Repository navigation
stack2nix doesn't work well with submodules #163
Description
Activity
We've since switched almost exclusively to
haskell.nixat iohk. See https://input-output-hk.github.io/haskell.nix/@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 :-)
I think we've fixed this bug at some point but could be it's still broken.
Given @mpickering has a workaround I'd rather delay any stack2nix improvements until I find time for haskell.nix and switch my projects to 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
masterrather than the given revision.If the commit you want to use contains submodules which point to a different remote then running
stack2nixfails 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.