Running nixpkgs-update (https://nix-community.org/update-bot/) with UPDATE_INFO: faketty 1.0.19 -> 1.0.20 https://github.com/dtolnay/faketty/releases attrpath: faketty Checking auto update branch... No auto update branch exists [version] [version] generic version rewriter does not support multiple hashes [rustCrateVersion] [rustCrateVersion] Replacing cargoHash with sha256-2MVWtCezrCd+uDAkYLzwDNobrc7TQEu1H2eUHlOcpVE= [rustCrateVersion] Finished updating Crate version and replacing hashes [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/fa/faketty/package.nix b/pkgs/by-name/fa/faketty/package.nix index 90bc0e38d8c3..946cb75ea9a6 100644 --- a/pkgs/by-name/fa/faketty/package.nix +++ b/pkgs/by-name/fa/faketty/package.nix @@ -6,14 +6,14 @@ rustPlatform.buildRustPackage rec { pname = "faketty"; - version = "1.0.19"; + version = "1.0.20"; src = fetchCrate { inherit pname version; - hash = "sha256-ntfbwaVZM4wtoDaaFo+Y7RHSft3KZ29DMsNiTvhiaXs="; + hash = "sha256-1AX2DBFOSUcORSQCo/5Vd8puE4hJU9VDfVqxcZDKrrY="; }; - cargoHash = "sha256-0pDm/e1xisPLqdTe10kleoejQfuOZoZW6l/83Splz/Y="; + cargoHash = "sha256-2MVWtCezrCd+uDAkYLzwDNobrc7TQEu1H2eUHlOcpVE="; postPatch = '' patchShebangs tests/test.sh 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: `7e49124d2edc3dd9185a0689a8e32d6fd6b70be1` --- ### `x86_64-linux`
:x: 2 packages failed to build:
:white_check_mark: 4 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://github.com/dtolnay/faketty/releases. meta.description for faketty is: Wrapper to execute a command in a pty, even if redirecting the output meta.homepage for faketty is: https://github.com/dtolnay/faketty meta.changelog for faketty is: https://github.com/dtolnay/faketty/releases/tag/1.0.20 ###### Updates performed - Rust version update ###### To inspect upstream changes ###### Impact Checks done --- - built on NixOS - The tests defined in `passthru.tests`, if any, passed - found 1.0.20 with grep in /nix/store/dg86fixsvvv2bbfzcmy01amr3vmlqf41-faketty-1.0.20 - found 1.0.20 in filename of file in /nix/store/dg86fixsvvv2bbfzcmy01amr3vmlqf41-faketty-1.0.20 ---
Rebuild report (if merged into master) (click to expand) ``` 7 total rebuild path(s) 7 package rebuild(s) First fifty rebuilds by attrpath cdktf-cli faketty ghostfolio grafana parca shopify-cli ```
Instructions to test this update (click to expand) --- Either **download from the cache**: ``` nix-store -r /nix/store/dg86fixsvvv2bbfzcmy01amr3vmlqf41-faketty-1.0.20 \ --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 faketty https://github.com/r-ryantm/nixpkgs/archive/7e49124d2edc3dd9185a0689a8e32d6fd6b70be1.tar.gz ``` Or: ``` nix build github:r-ryantm/nixpkgs/7e49124d2edc3dd9185a0689a8e32d6fd6b70be1#faketty ``` After you've downloaded or built it, look at the files and if there are any, run the binaries: ``` ls -la /nix/store/dg86fixsvvv2bbfzcmy01amr3vmlqf41-faketty-1.0.20 ls -la /nix/store/dg86fixsvvv2bbfzcmy01amr3vmlqf41-faketty-1.0.20/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: `7e49124d2edc3dd9185a0689a8e32d6fd6b70be1` --- ### `x86_64-linux`
:x: 2 packages failed to build:
:white_check_mark: 4 packages built:
--- ###### Maintainer pings > [!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/482954