-
-
Notifications
You must be signed in to change notification settings - Fork 15.2k
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
swig4: 4.0.2 -> 4.2.1 #277049
swig4: 4.0.2 -> 4.2.1 #277049
Conversation
This pull request has been mentioned on NixOS Discourse. There might be relevant details there: https://discourse.nixos.org/t/prs-ready-for-review/3032/3220 |
Result of 30 packages failed to build:
91 packages built:
non-empty logs https://gist.github.com/pbsds/b5a614c1cd6f8431899b837a2b94d704 |
79e5051
to
9728175
Compare
Thanks @wegank, for the updates on this PR. What's a good strategy to move forward with this? 30 failed packages are a bit much for me to try and fix, especially as I can only build on my local workstation. Should I look out for updates on the failed packages? Contact those maintainers? Any ideas and suggestions are most welcome. |
I think it's necessary to open separate PRs to fix the packages before merging this (I've made 14 for the bump to exiv2 0.28, for example). But it would indeed be a good idea to ping the maintainers first to see if they can fix them. |
@pbsds would you be willing to do another |
Thanks for the recommendation @wegank, I'll work through the build failures and will open Issues or PRs and ask the package maintainers for help. |
Result of 13 packages marked as broken and skipped:
25 packages failed to build:
75 packages built:
Hydra EDIT: i built the
|
With the availability of the 24.05 release and this PRs branch having rebased on the current |
Result of 38 packages marked as broken and skipped:
22 packages failed to build:
24 packages built:
|
Find below a few findings, thoughts, questions related to the build failures posted above:
|
I wouldn't worry about packages that are already broken on hydra, like kicad, txtai and pytorch-metric-learning. You can check so by inserting the attribute path into urls like https://hydra.nixos.org/job/nixos/trunk-combined/nixpkgs.kicad-unstable.x86_64-linux For new breakages you need to determine whether the failure is due to flakyness/impurity or due to the change in swig4 I'm running nixpkgs-review on x86_64-linux now |
I'm sure it is non-optional now. In particular,
Yes, but I think my #272425 is no longer working from a certain date this year, I'll try to bump the package again in that PR this weekend. |
I wasn't aware about the or-tools update in #272425, happy to help test on |
Result of 38 packages marked as broken and skipped:
22 packages failed to build:
24 packages built:
|
Result of 9 packages failed to build:
55 packages built:
|
Result of 8 packages marked as broken and skipped:
12 packages built:
|
Mind having another look at this, @siraben, @quantenzitrone, @wegank, @SomeoneSerge? Checking the failed linux builds the following packages also fail on a recent commit (d3cb976) on master and are likely unrelated to the changes proposed in this PR:
The build failure of faiss is known (see facebookresearch/faiss#3239), related to the changes in this PR, and addressed by 3cdf3ed491bfbc66891d0451dcbceb9b06206774 also included in this PR. The other failures are very likely failures related to the faiss build-failure as they seem to have faiss as a dependency. |
Result of 2 packages failed to build:
62 packages built:
|
Co-authored-by: quantenzitrone <74491719+quantenzitrone@users.noreply.github.com>
Result of 2 packages marked as broken and skipped:
18 packages failed to build:
110 packages built:
|
only new failure is described in #287880, LGTM |
Thank you for your contribution @afh, this one took a while to get merged |
Thanks @pbsds and everyone involved for your feedback and helping getting this merged, very much appreciated!! 🙏 |
Description of changes
👉 NOTA BENE: This PR depends on the relaxed gpytorch version requirement for botorch changes from #328732 in order to successfully run ``nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"
on
aarch64-darwin`.Things done
nix.conf
? (See Nix manual)sandbox = relaxed
sandbox = true
nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"
. Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/
)Add a 👍 reaction to pull requests you find important.