-
-
Notifications
You must be signed in to change notification settings - Fork 14.2k
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
fetchFromGitHub: re-fetch upon version changes #294068
base: staging
Are you sure you want to change the base?
Conversation
c2f6d70
to
65a152b
Compare
65a152b
to
c0ae33f
Compare
version
and re-fetch upon version/rev changesversion
and re-fetch upon version changes
c0ae33f
to
70bc532
Compare
@ofborg build archivebox python311Packages.jwt python312Packages.jwt |
70bc532
to
56cc63c
Compare
@ofborg build cowsay |
@ofborg build nixdoc |
08f6449
to
3b8b903
Compare
version
and re-fetch upon version changes
Let's limit the scope of this PR and avoid changing the interface too much. |
408e863
to
f893a82
Compare
f893a82
to
f1db6e9
Compare
I couldn't find a way to reproduce the build failure as well. Even |
ofborg-eval-lib-tests failure
i've seen this failure before and filed a bug: #294433 re-runing the eval usually clears it: |
I'm running |
Update: Manual run on my Command: |
@ofborg eval |
Take optional argument `passthru` for custom passthru attribute set. Update the `meta` attribute via `<pkg>.overrideAttrs` instead of attribute set update (`//`). Attach attributes `owner`, `repo` and `rev` via `passthru` instead of attribute set update.
Prefix the default value of `name` with `rev` to force re-fetch everytime `rev` changes.
f1db6e9
to
b6f434c
Compare
Bump as #294334 is merged and has headed |
@ofborg eval |
Similar changes were rejected previously: #59858 (review) |
@lheckemann Thanks a lot for this information! Things have changed a lot this five years. We don't even have |
Actually the concern we have now was the same concern from 7 years ago 🙃
And now every nix user gets to trip on FOD moments, so badly that we have to warn them in the manual about it. Anyway maybe the new RFC will help sort it. |
This pull request has been mentioned on NixOS Discourse. There might be relevant details there: https://discourse.nixos.org/t/puzzling-behavior-of-fetchfromgithub-with-submodules/48911/3 |
Description of changes
This PR mitigates the development issue of irrelevent FOD hashes after version bump/version overriding, by making
rev
part of the store path through the default value of thename
attribute.Depends on #294329 and #294334. Once they're merged, there will be only one commit and two changed files (including the release note) in this PR.
Things done
nix.conf
? (See Nix manual)sandbox = relaxed
sandbox = true
nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"
. Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/
)Add a 👍 reaction to pull requests you find important.