-
-
Notifications
You must be signed in to change notification settings - Fork 14.1k
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
fetchpatch2: init #182250
fetchpatch2: init #182250
Conversation
allows us to use the new features of patchutils without having to reset all fetchpatch hashes in nixpkgs NixOS#32084
In principle I like the approach. Before merging, we perhaps should think if there's some other potentially hash-changing... change that we might want to have as well. |
I'm not aware of those and they might also have been implemented or fixed already because our current fetchpatch patchutils is from 2013 |
@@ -31,6 +31,7 @@ with pkgs; | |||
|
|||
fetchurl = callPackages ../build-support/fetchurl/tests.nix { }; | |||
fetchpatch = callPackages ../build-support/fetchpatch/tests.nix { }; | |||
fetchpatch2 = callPackages ../build-support/fetchpatch/tests.nix { fetchpatch = fetchpatch2; }; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should move this right into the test then we could also reduce the changes in all-packages.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the current solution is decent. If we need something else, we can change it.
#48567 is the only issue I've found, but can be largely resolved by hashing parameters into a |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, but needs more eyes.
patchutils = buildPackages.patchutils_0_3_3; | ||
} // { | ||
tests = pkgs.tests.fetchpatch; | ||
version = 1; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since fetchurl now support pname+version we could set this via that but not super important.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That'd be on the result of fetchpatch, whereas the test needs it to have a version for the function itself.
I think having the version on the result (derivation) would be confusing. (Why does my patch have a version I didn't specify?)
Successfully created backport PR #203847 for |
Git push to origin failed for release-22.11 with exitcode 1 |
perhaps we should do the the downloading in a fod and then the patchutils stuff in a non fod to prevent hash incompabilities when we update patchutils |
The main point of |
allows us to use the new features of patchutils without having to reset
all fetchpatch hashes in nixpkgs
#32084
Description of changes
Things done
sandbox = true
set innix.conf
? (See Nix manual)nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"
. Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/
)nixos/doc/manual/md-to-db.sh
to update generated release notes