dyncall: 1.1 -> 1.2 #111169
dyncall: 1.1 -> 1.2 #111169
Conversation
ofborg
bot
added
10.rebuild-darwin: 1-10
10.rebuild-darwin: 1
10.rebuild-linux: 1-10
labels
| sha256 = "cf97fa3f142db832ff34235caa4d69a7d5f16716573d446b2d95069126e88795"; | ||
| url = "https://www.dyncall.org/r1.2/dyncall-1.2.tar.gz"; | ||
| # https://www.dyncall.org/r1.2/SHA256 | ||
| sha256 = "sha256-6IFUwCQ0IVYHBPXHKUr73snpka+gYB1a3/UELqgYCNc="; |
There was a problem hiding this comment.
The upstream sha256 (see the URL in the comment) is "e88154c0243421560704f5c7294afbdec9e991afa0601d5adff5042ea81808d7" which I prefer since it's easier to check (or populate if taking from upstream) but shrug don't feel strongly about it.
(update: nix-hash --to-base16 --type sha256 "sha256-6IFUwCQ0IVYHBPXHKUr73snpka+gYB1a3/UELqgYCNc=" confirms the hashes match, which isn't surprising, but FYI :))
Surprised this needs to go to staging, wonder what causes the mass rebuild?! haha
There was a problem hiding this comment.
I don't really care about the sha format but way more about that the version number is not substituted.
Surprised this needs to go to staging, wonder what causes the mass rebuild?! haha
Some hickup, changed target branch.
|
Result of 3 packages built:
|
Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/dyncall/versions.
meta.description for dyncall is: "Highly dynamic multi-platform foreign function call interface library"
meta.homepage for dyncall is: "https://www.dyncall.org"
meta.changelog for dyncall is: ""
Updates performed
To inspect upstream changes
Impact
Checks done (click to expand)
built on NixOS
The tests defined in
passthru.tests, if any, passed0 of 0 passed binary check by having a zero exit code.
0 of 0 passed binary check by having the new version present in output.
directory tree listing: https://gist.github.com/f7f176ecef12308592bf80c8d98dbc6b
du listing: https://gist.github.com/e08801c96c596cda9afae2a1f0df1ff0
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.)
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:
After you've downloaded or built it, look at the files and if there are any, run the binaries:
Pre-merge build results
NixPkgs review skipped
Maintainer pings
cc @dtzWill for testing.