debootstrap 0 -> 1 attrpath: debootstrap Checking auto update branch... [version] [version] skipping because derivation has updateScript [rustCrateVersion] [rustCrateVersion] No cargoSha256 or cargoHash found [golangModuleVersion] [golangModuleVersion] Not a buildGoModule package with vendorSha256 or vendorHash [npmDepsVersion] [npmDepsVersion] No npmDepsHash [updateScript] [updateScript] Success [updateScript] this derivation will be built: /nix/store/8fpc1pygqkmad97vypx496jsnfaiy6b0-packages.json.drv building '/nix/store/8fpc1pygqkmad97vypx496jsnfaiy6b0-packages.json.drv'... Going to be running update for following packages: - debootstrap-1.0.131 Press Enter key to continue... Running update for: - debootstrap-1.0.131: UPDATING ... - debootstrap-1.0.131: DONE. Packages updated! [quotedUrls] [quotedUrls] nothing found to replace Diff after rewrites: diff --git a/pkgs/tools/misc/debootstrap/default.nix b/pkgs/tools/misc/debootstrap/default.nix index 04c19d93af99..d80b25771b6b 100644 --- a/pkgs/tools/misc/debootstrap/default.nix +++ b/pkgs/tools/misc/debootstrap/default.nix @@ -40,14 +40,14 @@ let binPath = lib.makeBinPath [ ]; in stdenv.mkDerivation rec { pname = "debootstrap"; - version = "1.0.131"; + version = "debian/1.0.123+deb11u2"; src = fetchFromGitLab { domain = "salsa.debian.org"; owner = "installer-team"; repo = pname; rev = "refs/tags/${version}"; - hash = "sha256-rwNcrS2GzVs0JYxeHcpLMG9FDwSpthNmZIemn95hC6g="; + hash = "sha256-jME09mitlUqHZ13icg/WG5AAz+jyFJbDYU/8axSmBHo="; }; nativeBuildInputs = [ makeWrapper ]; No auto update branch exists Successfully finished processing cachix "/nix/store/dq28l3szsdyz9irxxvrsm2s4is1dyyqm-debootstrap-debian-1.0.123+deb11u2" [check][nixpkgs-review] Result of `nixpkgs-review` run on x86_64-linux [1](https://github.com/Mic92/nixpkgs-review)
2 packages built:
Automatic update generated by [nixpkgs-update](https://github.com/ryantm/nixpkgs-update) tools. This update was made based on information from passthru.updateScript. meta.description for debootstrap is: Tool to create a Debian system in a chroot meta.homepage for debootstrap is: https://wiki.debian.org/Debootstrap meta.changelog for debootstrap is: https://salsa.debian.org/installer-team/debootstrap/-/blob/debian/1.0.123+deb11u2/debian/changelog ###### Updates performed - Ran passthru.UpdateScript ###### To inspect upstream changes ###### Impact
Checks done (click to expand) --- - built on NixOS - The tests defined in `passthru.tests`, if any, passed - found debian/1.0.123+deb11u2 with grep in /nix/store/dq28l3szsdyz9irxxvrsm2s4is1dyyqm-debootstrap-debian-1.0.123+deb11u2 ---
Rebuild report (if merged into master) (click to expand) ``` 2 total rebuild path(s) 2 package rebuild(s) First fifty rebuilds by attrpath debootstrap distrobuilder ```
Instructions to test this update (click to expand) --- Either **download from Cachix**: ``` nix-store -r /nix/store/dq28l3szsdyz9irxxvrsm2s4is1dyyqm-debootstrap-debian-1.0.123+deb11u2 \ --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \ --option trusted-public-keys ' nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs= cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY= ' ``` (The Cachix cache is only trusted for this store-path realization.) For the Cachix download to work, your user must be in the `trusted-users` list or you can use `sudo` since root is effectively trusted. Or, **build yourself**: ``` nix-build -A debootstrap https://github.com/r-ryantm/nixpkgs/archive/46823c77b41a59ad5905a5c36c8666f1e1203ef8.tar.gz ``` Or: ``` nix build github:r-ryantm/nixpkgs/46823c77b41a59ad5905a5c36c8666f1e1203ef8#debootstrap ``` After you've downloaded or built it, look at the files and if there are any, run the binaries: ``` ls -la /nix/store/dq28l3szsdyz9irxxvrsm2s4is1dyyqm-debootstrap-debian-1.0.123+deb11u2 ls -la /nix/store/dq28l3szsdyz9irxxvrsm2s4is1dyyqm-debootstrap-debian-1.0.123+deb11u2/bin ``` ---

### Pre-merge build results We have automatically built all packages that will get rebuilt due to this change. This gives evidence on whether the upgrade will break dependent packages. Note sometimes packages show up as _failed to build_ independent of the change, simply because they are already broken on the target branch. Result of `nixpkgs-review` run on x86_64-linux [1](https://github.com/Mic92/nixpkgs-review)
2 packages built:
--- ###### Maintainer pings cc @MarcWeber for [testing](https://github.com/ryantm/nixpkgs-update/blob/master/doc/nixpkgs-maintainer-faq.md#r-ryantm-opened-a-pr-for-my-package-what-do-i-do). https://api.github.com/repos/NixOS/nixpkgs/pulls/259803