Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

renode-unstable: 1.15.3+20241217git398e80b6e -> 1.15.3+20250109git606a24e00 #372360

Merged

Conversation

r-ryantm
Copy link
Contributor

@r-ryantm r-ryantm commented Jan 9, 2025

Automatic update generated by 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.3+20250109git606a24e00 in filename of file in /nix/store/0n70wh00n3wqvkfvzxc8g5gdrq5y8m6a-renode-unstable-1.15.3+20250109git606a24e00

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 the cache:

nix-store -r /nix/store/0n70wh00n3wqvkfvzxc8g5gdrq5y8m6a-renode-unstable-1.15.3+20250109git606a24e00 \
  --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 renode-unstable https://github.com/r-ryantm/nixpkgs/archive/e77b50689e4d0aab4989064615d2803aebdab72b.tar.gz

Or:

nix build github:r-ryantm/nixpkgs/e77b50689e4d0aab4989064615d2803aebdab72b#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/0n70wh00n3wqvkfvzxc8g5gdrq5y8m6a-renode-unstable-1.15.3+20250109git606a24e00
ls -la /nix/store/0n70wh00n3wqvkfvzxc8g5gdrq5y8m6a-renode-unstable-1.15.3+20250109git606a24e00/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.

Command: nixpkgs-review


x86_64-linux

✅ 1 package built:
  • renode-unstable

Maintainer pings

cc @otavio for testing.

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.


Add a 👍 reaction to pull requests you find important.

@github-actions github-actions bot added 10.rebuild-darwin: 0 This PR does not cause any packages to rebuild on Darwin 10.rebuild-linux: 1-10 labels Jan 9, 2025
@nix-owners nix-owners bot requested a review from otavio January 9, 2025 12:55
@otavio
Copy link
Contributor

otavio commented Jan 9, 2025

@NixOS/nixpkgs-merge-bot merge

@nixpkgs-merge-bot nixpkgs-merge-bot bot merged commit b71883b into NixOS:master Jan 9, 2025
23 of 27 checks passed
@nixpkgs-merge-bot
Copy link
Contributor

Merge completed (#306934)

@r-ryantm r-ryantm deleted the auto-update/renode-unstable branch January 10, 2025 00:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
10.rebuild-darwin: 0 This PR does not cause any packages to rebuild on Darwin 10.rebuild-linux: 1-10
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants