pdfcpu 0.7.0 -> 0.8.0 https://github.com/pdfcpu/pdfcpu/releases attrpath: pdfcpu Checking auto update branch... No auto update branch exists [version] [version] generic version rewriter does not support multiple hashes [rustCrateVersion] [rustCrateVersion] No cargoSha256 or cargoHash found [golangModuleVersion] [golangModuleVersion] Found old vendorHash = "sha256-jVX/CFf9dd9qD3gyGVDjbfINtPLCsgdjWFix4BCpDZ0=" [golangModuleVersion] Replaced vendorHash with sha256-4k4aZnQ9SjcGr/ziCacfcVfVk7w4Qhli2rOeYE76Qs0= [golangModuleVersion] Finished updating vendorHash [npmDepsVersion] [npmDepsVersion] No npmDepsHash [updateScript] [updateScript] skipping because derivation has no updateScript Diff after rewrites: diff --git a/pkgs/applications/graphics/pdfcpu/default.nix b/pkgs/applications/graphics/pdfcpu/default.nix index 2613304b17c2..77458c3cc5af 100644 --- a/pkgs/applications/graphics/pdfcpu/default.nix +++ b/pkgs/applications/graphics/pdfcpu/default.nix @@ -2,13 +2,13 @@ buildGoModule rec { pname = "pdfcpu"; - version = "0.7.0"; + version = "0.8.0"; src = fetchFromGitHub { owner = "pdfcpu"; repo = pname; rev = "v${version}"; - hash = "sha256-FzlukSQSKeQY6H53UfWXwL8bXkOXRhaA92/Kgxh4oms="; + hash = "sha256-E1D2DvwwrtlY06kvCZkoAO5VcdtkBJYLcxuqGsulFUA="; # Apparently upstream requires that the compiled executable will know the # commit hash and the date of the commit. This information is also presented # in the output of `pdfcpu version` which we use as a sanity check in the @@ -31,7 +31,7 @@ buildGoModule rec { ''; }; - vendorHash = "sha256-jVX/CFf9dd9qD3gyGVDjbfINtPLCsgdjWFix4BCpDZ0="; + vendorHash = "sha256-4k4aZnQ9SjcGr/ziCacfcVfVk7w4Qhli2rOeYE76Qs0="; ldflags = [ "-s" Successfully finished processing cachix "/nix/store/5cwfr61dyvxfnbkjz67qj8srjasnld7x-pdfcpu-0.8.0" [check][nixpkgs-review] Result of `nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }'` run on x86_64-linux [1](https://github.com/Mic92/nixpkgs-review)
1 package built:
Automatic update generated by [nixpkgs-update](https://github.com/ryantm/nixpkgs-update) tools. This update was made based on information from https://github.com/pdfcpu/pdfcpu/releases. meta.description for pdfcpu is: A PDF processor written in Go meta.homepage for pdfcpu is: https://pdfcpu.io ###### Updates performed - Golang update ###### To inspect upstream changes ###### Impact Checks done --- - built on NixOS - The tests defined in `passthru.tests`, if any, passed - found 0.8.0 with grep in /nix/store/5cwfr61dyvxfnbkjz67qj8srjasnld7x-pdfcpu-0.8.0 - found 0.8.0 in filename of file in /nix/store/5cwfr61dyvxfnbkjz67qj8srjasnld7x-pdfcpu-0.8.0 ---
Rebuild report (if merged into master) (click to expand) ``` 2 total rebuild path(s) 2 package rebuild(s) First fifty rebuilds by attrpath pdfcpu ```
Instructions to test this update (click to expand) --- Either **download from Cachix**: ``` nix-store -r /nix/store/5cwfr61dyvxfnbkjz67qj8srjasnld7x-pdfcpu-0.8.0 \ --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 pdfcpu https://github.com/r-ryantm/nixpkgs/archive/f72200173490f328d596232c510a98134dd134ef.tar.gz ``` Or: ``` nix build github:r-ryantm/nixpkgs/f72200173490f328d596232c510a98134dd134ef#pdfcpu ``` After you've downloaded or built it, look at the files and if there are any, run the binaries: ``` ls -la /nix/store/5cwfr61dyvxfnbkjz67qj8srjasnld7x-pdfcpu-0.8.0 ls -la /nix/store/5cwfr61dyvxfnbkjz67qj8srjasnld7x-pdfcpu-0.8.0/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 --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }'` run on x86_64-linux [1](https://github.com/Mic92/nixpkgs-review)
1 package built:
--- ###### Maintainer pings cc @doronbehar for [testing](https://github.com/ryantm/nixpkgs-update/blob/main/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/306683