-
-
Notifications
You must be signed in to change notification settings - Fork 14.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
[staging] boost: bump default version to 1.7x #120259
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
diff LGTM but we need to check the outfall and try to minimize the breakage.
I assume this is going to have to wait until after ZHF/21.05 release now? |
pkgs/top-level/all-packages.nix
Outdated
@@ -13442,7 +13442,7 @@ in | |||
boost174 = callPackage ../development/libraries/boost/1.74.nix { }; | |||
boost175 = callPackage ../development/libraries/boost/1.75.nix { }; | |||
boost17x = boost175; | |||
boost = boost16x; | |||
boost = boost17x; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not sure about this change. It is probably going to break a lot and I can't really test it right now because my usual test packages are not building on staging.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've had a hard time testing this due to the sheer number of packages that need to be re-built. If someone with the storage space and will to do a comprehensive nixpkgs-review test on it (or some other mechanism of seeing what packages are broken), I can do a regex replace boost -> boost16x for anything that wont build with the newer version.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have a quite beefy remote build farm available but I can't build 5000+ packages. I don't know how we should continue with this PR.
@jonringer can you assist?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Targeting at a merge base of staging and master makes more sense, there binary cache should be available for testing.
Keep in mind that, after this PR is merged, or even with this PR, we should also remove all overrides of packages where: boost = boost17x; As of now I count 11 occurences in |
rdedup: 3.1.1 -> 3.2.1
sdparm: 1.11 -> 1.12
SPAdes: 3.15.2 -> 3.15.3
terraform: 1.0.6 -> 1.0.7
Motivation for this change
Most packages that depend on the boost libraries in nixpkgs are pointing at the unversioned "boost" package. Unversioned boost is currently 1.69.0, which was released in 2018. This should be updated to the newest boost library available in nixpkgs (1.75). I expect build-time breakages, but it should be fairly straightforward to pin broken packages to an older boost revision once they are identified.
Things done
sandbox
innix.conf
on non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
./result/bin/
)nix path-info -S
before and after)