-
Notifications
You must be signed in to change notification settings - Fork 19
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
adding lix fails with "default" behaviour #96
Comments
|
can you define "too old"? |
today i cannot reproduce the problem. |
Because i didn't came across the problem again i close this issue. |
this recently begun happening to me with both {
"pins": {
...
"lix": {
"type": "GitRelease",
"repository": {
"type": "Git",
"url": "https://git.lix.systems/lix-project/lix"
},
"pre_releases": false,
"version_upper_bound": null,
"release_prefix": null,
"version": "2.91.1",
"revision": "ad9d06f7838a25beec425ff406fe68721fef73be",
"url": null,
"hash": "0ibpbvc6871bqyab0msml2g2y3c6jvg6yb169lykg4257izss8c6"
},
"lix-nixos-module": {
"type": "GitRelease",
"repository": {
"type": "Git",
"url": "https://git.lix.systems/lix-project/nixos-module"
},
"pre_releases": false,
"version_upper_bound": null,
"release_prefix": null,
"version": "2.91.1",
"revision": "6478f624b2a00367e0e3d750a2c7a9f3afb72712",
"url": null,
"hash": "1mq5741iwa10r93shg1y8q6cxa2zjppc2w10hsrv1gfac76p8nmj"
},
...
},
"version": 3
} which then gives the following error when i rebuild:
if i only
|
im really confused about this. why does branch matter at all when it knows exactly what revision it's after? why has the revision reference been updated to something it'll refuse to check out? |
the problem seems to be this: "Seems like npins indeed breaks for tags that are not on the default branch." |
...
so
so how about using allRefs = true in |
Note: this situation is a bit spicy as it involves: With Nix starting somewhen after 2.18, passing ... but still there is that problematic issue where Nix 2.18 and Lix ( ... which is made even more annoying when you see that if you get a Nix 2.24 to |
Perhaps there is apetite in the Lix community to fix this issue once and for all? Perhaps using |
adds
but
produces the following error:
the problem is that nix expect main as branch but the release is on release-2.90 branch.
i wonder if this is a inherent problem of buildins.fetchGit or if it can be somehow mitigated. with information we have in npins (but do not store yet).
The text was updated successfully, but these errors were encountered: