-
-
Notifications
You must be signed in to change notification settings - Fork 14.4k
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
capnproto: 0.10.4 -> 1.0.1 #249260
capnproto: 0.10.4 -> 1.0.1 #249260
Conversation
This is not compatible with pycapnp due to capnproto/pycapnp#323. In the meantime, I've turned this PR into a draft. |
5a257f4
to
aa820d1
Compare
Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/capnproto/versions. meta.description for capnproto is: Cap'n Proto cerealization protocol meta.homepage for capnproto is: https://capnproto.org/ Updates performed
To inspect upstream changesImpactChecks done (click to expand)
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:
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 2 packages failed to build:
20 packages built:
Maintainer pings |
That pycapnp issue doesn't seem to be progressing, could we just mark pycapnp as broken and merge this? |
@tjni friendly ping. Do you think we could still merge this before pycapnp is fixed? 🙏 capnproto 1.0 is already 2 months old and I need it to update the veilid package. |
This pull request has been mentioned on NixOS Discourse. There might be relevant details there: |
Pinging maintainers of If you don't intend on maintaining the package anymore, let us know and we'll remove you from its maintainers. |
@bbigras if they don't respond in a week or so, feel free to merge this and mark |
Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/capnproto/versions.
meta.description for capnproto is: Cap'n Proto cerealization protocol
meta.homepage for capnproto is: https://capnproto.org/
Updates performed
To inspect upstream changes
Impact
Checks done (click to expand)
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-users
list or you can usesudo
since 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-review
run on x86_64-linux 12 packages failed to build:
19 packages built:
Maintainer pings
cc @cstrahan for testing.