Running nixpkgs-update (https://nix-community.org/update-bot/) with UPDATE_INFO: bup 0.33.9 -> 0.33.10 https://repology.org/project/bup/versions attrpath: bup Checking auto update branch... No auto update branch exists [version] [version] updated version and sha256 [rustCrateVersion] [rustCrateVersion] No cargoHash found [golangModuleVersion] [golangModuleVersion] Not a buildGoModule package with vendorHash [npmDepsVersion] [npmDepsVersion] No npmDepsHash [updateScript] [updateScript] skipping because derivation has no updateScript Diff after rewrites: diff --git a/pkgs/by-name/bu/bup/package.nix b/pkgs/by-name/bu/bup/package.nix index 8373c3b527d1..379531d3ccd0 100644 --- a/pkgs/by-name/bu/bup/package.nix +++ b/pkgs/by-name/bu/bup/package.nix @@ -15,7 +15,7 @@ assert par2Support -> par2cmdline != null; let - version = "0.33.9"; + version = "0.33.10"; pythonDeps = with python3.pkgs; @@ -38,7 +38,7 @@ stdenv.mkDerivation { repo = "bup"; owner = "bup"; tag = version; - hash = "sha256-MW4kScu81XW89W7WpvOj40+S8bG5QozN30Hfj4TsnX4="; + hash = "sha256-uqXlfTFRgCN9c00iQik+IMN6k81fpeY6gNscP54Xzgs="; }; buildInputs = [ Successfully finished processing [check][nixpkgs-review] ## `nixpkgs-review` result Generated using [`nixpkgs-review`](https://github.com/Mic92/nixpkgs-review). Command: `nixpkgs-review --extra-nixpkgs-config '{ allowBroken = false; }'` Commit: `079d6b841e6a3f2c05848ff15a6e2025b857261d` --- ### `x86_64-linux`
:white_check_mark: 25 packages built:
Automatic update generated by [nixpkgs-update](https://github.com/nix-community/nixpkgs-update) tools. This update was made based on information from https://repology.org/project/bup/versions. meta.description for bup is: Efficient file backup system based on the git packfile format meta.homepage for bup is: https://github.com/bup/bup ###### Updates performed - Version update ###### To inspect upstream changes ###### Impact Checks done --- - built on NixOS - The tests defined in `passthru.tests`, if any, passed - found 0.33.10 with grep in /nix/store/cp6pzn7x9bwvm80519xng95y6ndrw86c-bup-0.33.10 - found 0.33.10 in filename of file in /nix/store/cp6pzn7x9bwvm80519xng95y6ndrw86c-bup-0.33.10 ---
Rebuild report (if merged into master) (click to expand) ``` 17 total rebuild path(s) 17 package rebuild(s) First fifty rebuilds by attrpath bup datalad datalad-gooey git-annex git-annex-metadata-gui haskellPackages.git-annex python313Packages.datalad python313Packages.datalad-gooey python313Packages.datalad-next python313Packages.git-annex-adapter python313Packages.heudiconv python314Packages.datalad python314Packages.datalad-gooey python314Packages.datalad-next python314Packages.git-annex-adapter python314Packages.heudiconv ```
Instructions to test this update (click to expand) --- Either **download from the cache**: ``` nix-store -r /nix/store/cp6pzn7x9bwvm80519xng95y6ndrw86c-bup-0.33.10 \ --option binary-caches 'https://cache.nixos.org/ https://nixpkgs-update-cache.nix-community.org/' \ --option trusted-public-keys ' nixpkgs-update-cache.nix-community.org-1:U8d6wiQecHUPJFSqHN9GSSmNkmdiFW7GW7WNAnHW0SM= cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY= ' ``` (The nixpkgs-update cache is only trusted for this store-path realization.) For the cached 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 bup https://github.com/r-ryantm/nixpkgs/archive/079d6b841e6a3f2c05848ff15a6e2025b857261d.tar.gz ``` Or: ``` nix build github:r-ryantm/nixpkgs/079d6b841e6a3f2c05848ff15a6e2025b857261d#bup ``` After you've downloaded or built it, look at the files and if there are any, run the binaries: ``` ls -la /nix/store/cp6pzn7x9bwvm80519xng95y6ndrw86c-bup-0.33.10 ls -la /nix/store/cp6pzn7x9bwvm80519xng95y6ndrw86c-bup-0.33.10/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. ## `nixpkgs-review` result Generated using [`nixpkgs-review`](https://github.com/Mic92/nixpkgs-review). Command: `nixpkgs-review --extra-nixpkgs-config '{ allowBroken = false; }'` Commit: `079d6b841e6a3f2c05848ff15a6e2025b857261d` --- ### `x86_64-linux`
:white_check_mark: 25 packages built:
--- ###### Maintainer pings cc @rnhmjoj for [testing](https://github.com/nix-community/nixpkgs-update/blob/main/doc/nixpkgs-maintainer-faq.md#r-ryantm-opened-a-pr-for-my-package-what-do-i-do). > [!TIP] > As a maintainer, if your package is located under `pkgs/by-name/*`, you can comment **`@NixOS/nixpkgs-merge-bot merge`** to automatically merge this update using the [`nixpkgs-merge-bot`](https://github.com/NixOS/nixpkgs/blob/master/ci/README.md#nixpkgs-merge-bot). https://api.github.com/repos/NixOS/nixpkgs/pulls/484923