-
-
Notifications
You must be signed in to change notification settings - Fork 453
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fetchGit: work-around bug in Nix 2.4 #424
Conversation
I was mistaken, the issue persists on 2.5 as well, so the condition check need to be adjusted accordingly |
f3ea507
to
5525d1f
Compare
Tested on |
Another approach to make `poetry2nix` work with dependencies specified by arbitrary `rev=<hash>` values on newer Nix revisions. Relates-to: nix-community#358 Relates-to: NixOS/nix#5128
If `branch` or `tag` is given in sourceSpec, then `fetchGit` would work as before, the only problematic setup is `rev` when used with Nix 2.4+
This bug should be fixed in Nix, not worked around in |
I'd like you to reconsider this decision because unless I am mistaken there is no alternative right now to use commit hashes with flakes. |
I agree with @vlaci. But for me it's not a workaround, it's plain following to upstream API changes |
I couldn't force-push to this branch so I made a new PR in #512. |
The point is that we shouldn't have these types of regressions in Nix and force downstream projects to deal with them. |
@adisbladis i agree, Nix team should communicate clearly and announce breaking changes in advance. Downstream projects should have time to react and adapt. In a week of learning Nix this is already second case when upstream make dependent projects broken. It's not ok (( |
Another approach to make
poetry2nix
work with dependencies specifiedby arbitrary
rev=<hash>
values on newer Nix revisions.Relates-to: #358
Relates-to: NixOS/nix#5128
--
Interestingly I only see this error on 'nix-2.4pre20211001_4f49615' (nixpkgs-unstable channel) but not on 'nix-2.5pre20211007_844dd90' (nixos-unstable channel)Update: there was a cached copy of that dependency in my /nix/store 🙃