renode-unstable 0 -> 1 attrpath: renode-unstable Checking auto update branch... [version] [version] generic version rewriter does not support multiple hashes [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] these 2 derivations will be built: /nix/store/8r3jdlpxsvlg4mbpmk8cvb3wmkcbgmq3-renode-unstable-updater.drv /nix/store/2ry5d582a6h48xcvm0q770xb8abr5fwm-packages.json.drv building '/nix/store/8r3jdlpxsvlg4mbpmk8cvb3wmkcbgmq3-renode-unstable-updater.drv'... building '/nix/store/2ry5d582a6h48xcvm0q770xb8abr5fwm-packages.json.drv'... Going to be running update for following packages: - renode-unstable-1.15.1+20240808git7a138330e Press Enter key to continue... Running update for: - renode-unstable-1.15.1+20240808git7a138330e: UPDATING ... - renode-unstable-1.15.1+20240808git7a138330e: DONE. Packages updated! Diff after rewrites: diff --git a/pkgs/by-name/re/renode-unstable/package.nix b/pkgs/by-name/re/renode-unstable/package.nix index 746a18168685..ccac7bdabd02 100644 --- a/pkgs/by-name/re/renode-unstable/package.nix +++ b/pkgs/by-name/re/renode-unstable/package.nix @@ -5,11 +5,11 @@ renode.overrideAttrs (finalAttrs: _: { pname = "renode-unstable"; - version = "1.15.1+20240808git7a138330e"; + version = "1.15.1+20240816gitb8fc56b69"; src = fetchurl { url = "https://builds.renode.io/renode-${finalAttrs.version}.linux-dotnet.tar.gz"; - hash = "sha256-hxGh+Pzpvw7dfRLdaqSEUCM8zLN9z2HQD8owOCu/uY4="; + hash = "sha256-3J70pjIrGGQLDlVkKuPYjL7HcjrN9H/xF7248BaMwAs="; }; passthru.updateScript = No auto update branch exists Successfully finished processing cachix "/nix/store/c9gdmz67784i27gpbd31hnria3w2b8nj-renode-unstable-1.15.1+20240816gitb8fc56b69" [check][nixpkgs-review] Result of `nixpkgs-review` 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 passthru.updateScript. meta.description for renode-unstable is: Virtual development framework for complex embedded systems meta.homepage for renode-unstable is: https://renode.io ###### Updates performed - Ran passthru.UpdateScript ###### To inspect upstream changes ###### Impact Checks done --- - built on NixOS - The tests defined in `passthru.tests`, if any, passed - found 1.15.1+20240816gitb8fc56b69 in filename of file in /nix/store/c9gdmz67784i27gpbd31hnria3w2b8nj-renode-unstable-1.15.1+20240816gitb8fc56b69 ---
Rebuild report (if merged into master) (click to expand) ``` 2 total rebuild path(s) 2 package rebuild(s) First fifty rebuilds by attrpath renode-unstable ```
Instructions to test this update (click to expand) --- Either **download from Cachix**: ``` nix-store -r /nix/store/c9gdmz67784i27gpbd31hnria3w2b8nj-renode-unstable-1.15.1+20240816gitb8fc56b69 \ --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 renode-unstable https://github.com/r-ryantm/nixpkgs/archive/411a92de1cba0c38aed2e7a2dc8447e652c4e2bf.tar.gz ``` Or: ``` nix build github:r-ryantm/nixpkgs/411a92de1cba0c38aed2e7a2dc8447e652c4e2bf#renode-unstable ``` After you've downloaded or built it, look at the files and if there are any, run the binaries: ``` ls -la /nix/store/c9gdmz67784i27gpbd31hnria3w2b8nj-renode-unstable-1.15.1+20240816gitb8fc56b69 ls -la /nix/store/c9gdmz67784i27gpbd31hnria3w2b8nj-renode-unstable-1.15.1+20240816gitb8fc56b69/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)
1 package built:
--- ###### Maintainer pings cc @otavio 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). --- Add a :+1: [reaction] to [pull requests you find important]. [reaction]: https://github.blog/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/ [pull requests you find important]: https://github.com/NixOS/nixpkgs/pulls?q=is%3Aopen+sort%3Areactions-%2B1-desc https://api.github.com/repos/NixOS/nixpkgs/pulls/335350