unicorn: 2.1.0 -> 2.1.1 #343642
unicorn: 2.1.0 -> 2.1.1 #343642
Conversation
|
Result of 12 packages failed to build:
20 packages built:
|
r-ryantm
force-pushed
the
auto-update/unicorn
branch
from
a9e132a
to
8d631a0
Compare
|
Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/unicorn-engine/unicorn/releases. meta.description for unicorn is: Lightweight multi-platform CPU emulator library meta.homepage for unicorn is: https://www.unicorn-engine.org Updates performed
To inspect upstream changesImpactChecks done
Rebuild report (if merged into master) (click to expand)Instructions to test this update (click to expand)Either download from Cachix: (The Cachix cache is only trusted for this store-path realization.) Or, build yourself: Or: After you've downloaded or built it, look at the files and if there are any, run the binaries: Pre-merge build resultsWe have automatically built all packages that will get rebuilt due to This gives evidence on whether the upgrade will break dependent packages. Result of 12 packages marked as broken and skipped:
20 packages built:
Maintainer pingscc @thoughtpolice @luc65r for testing. Tip As a maintainer, if your package is located under Add a 👍 reaction to pull requests you find important. |
Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/unicorn-engine/unicorn/releases.
meta.description for unicorn is: Lightweight multi-platform CPU emulator library
meta.homepage for unicorn is: https://www.unicorn-engine.org
Updates performed
To inspect upstream changes
Release on GitHub
Compare changes on GitHub
Impact
Checks done
passthru.tests, if any, passedRebuild report (if merged into master) (click to expand)
Instructions to test this update (click to expand)
Either download from Cachix:
(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the
trusted-userslist or you can usesudosince root is effectively trusted.Or, build yourself:
Or:
After you've downloaded or built it, look at the files and if there are any, run the binaries:
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-reviewrun on x86_64-linux 131 packages failed to build:
1 package built:
Maintainer pings
cc @thoughtpolice @luc65r for testing.
Tip
As a maintainer, if your package is located under
pkgs/by-name/*, you can comment@NixOS/nixpkgs-merge-bot mergeto automatically merge this update using thenixpkgs-merge-bot.Add a 👍 reaction to pull requests you find important.