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
Staging next #51444
Staging next #51444
Conversation
There is a breakage introduced by the pyqt update (5.10 -> 5.11), the sip package must be handeled differently to be able to import the module. I did some investigation here : #49400 (comment) |
boto3: 1.9.36 -> 1.9.62 awscli: 1.16.72 I update all three of these at a time because they rely on each other and get annoyed when such changes are non-atomic. Also added a note to the packages telling people that this is needed. I tested awscli and the libraries against a real account.
It currently breaks on Python 3.7 due to `async` becoming a reserved keyword
I'm noticing the staging jobset on hydra hasn't run since November 27 ,and it hasn't even finished. Is there a jobset I don't know about? I'm concerned maybe something has broken in the shuffle here. |
Answer, yes: https://hydra.nixos.org/jobset/nixpkgs/staging-next :) |
@FRidh is this merge likely to happen soon? I'm waiting for the awscli/boto3/botocore updates and might manually transplant them over to master if this branch is going to take a while. There's no fundamental reason I think to bundle those with the rest of these updates, right? |
Just merged master into staging-next again. |
Seems like there were more recent changes that had not been rebuild as we have a mass-rebuild on master now. |
Looks like it comes from here: #51960, probably targeted at master by a mistake. |
Motivation for this change
Things done
sandbox
innix.conf
on non-NixOS)nix-shell -p nox --run "nox-review wip"
./result/bin/
)nix path-info -S
before and after)