dcrwallet: 1.5.1 -> 1.6.0 #110462
dcrwallet: 1.5.1 -> 1.6.0 #110462
Conversation
|
EDIT: Seems to be caused by the fact that the commit (somehow) has 1000 statuses (https://docs.github.com/en/rest/reference/repos#statuses). However, looking at the This can probably be worked around by force-pushing the commit. I'll probably ask someone somewhere how to determine if a commit has reached that 1000 status limit so we can add some logic to ofborg... Will look into this more tomorrow. EDIT2: Submitted a ticket. We'll see what happens. Unless this update is urgently necessary, it would be nice to not use my previously-suggested force-push workaround, to keep the PR state as it was when the issue occurred. Might help GitHub Support debug. Though, they might have a "time machine" that makes this carefulness unnecessary, but 🤷 EDIT3: They got back to me (relatively quickly... pleasantly surprised) and apparently the API only shows 30 statuses per page. Using |
|
@GrahamcOfBorg eval |
cole-h
force-pushed
the
auto-update/dcrwallet
branch
from
6185721
to
a93ca0f
Compare
Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/decred/dcrwallet/releases.
meta.description for dcrwallet is: "A secure Decred wallet daemon written in Go (golang)"
meta.homepage for dcrwallet is: "https://decred.org"
meta.changelog for dcrwallet 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.
found 1.6.0 with grep in /nix/store/0i8j9ja9v8kk57b7x4jyg5r54xvbdrln-dcrwallet-1.6.0
directory tree listing: https://gist.github.com/fc7f8dbc69bcd7c9a3f54cf736c2180d
du listing: https://gist.github.com/b79d8d4e270d5f53cbdb40749513f261
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
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 11 package built:
Maintainer pings
cc @juaningan @kalbasit for testing.