You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems that stack2nix first tries to clone the master branch for the given repo. This interacts poorly with submodules as they are initialised to the remote on master rather than the given revision.
If the commit you want to use contains submodules which point to a different remote then running stack2nix fails as it can't find the reference.
The way I "fixed" this was to push my branch to the master branch as well but obviously this is not possible in general.
The text was updated successfully, but these errors were encountered:
@angerman That's great but hie-nix still uses stack2nix which is where I ran into this issue. If hie-nix started using haskell.nix then this issue doesn't bother me.
@domenkozar this is now squarely in your court ;-) I tried. Maybe this is a good opportunity for you to finally try haskell.nix and complain about all that’s wrong with it :-)
It seems that stack2nix first tries to clone the master branch for the given repo. This interacts poorly with submodules as they are initialised to the remote on
master
rather than the given revision.If the commit you want to use contains submodules which point to a different remote then running
stack2nix
fails as it can't find the reference.The way I "fixed" this was to push my branch to the master branch as well but obviously this is not possible in general.
The text was updated successfully, but these errors were encountered: