-
-
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
staging-next 2024-05-31 #316075
Merged
Merged
staging-next 2024-05-31 #316075
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Reapply "systemd: enable debug info"
ghostscript: 10.02.1 -> 10.03.1
See https://gitlab.gnome.org/GNOME/glib/-/merge_requests/4073 and related upstream issues for details.
boehmgc: disable tests on aarch64-linux
e2fsprogs: 1.47.0 -> 1.47.1
pipewire: 1.0.6 -> 1.0.7
kexec-tools: pull upstream fix for binutils-2.42
#246164 but for hardlinks. Mesa, among other packages, has binaries that are linked together and can end up corrupted when the same binary is stripped through two different names. To resolve this, print out the device and inode number before each file name, sort/uniq based on that, then cut it back out before stripping. The symlink resolution logic is removed as the same file accessed through two different links in `$paths` will necessarily have the same numbers. File/directory within the paths listed in `$paths` are correctly not (and were never) processed due to the `-type f` predicate and (implied) `-P` option to `find`.
plasma-wayland-protocols: 1.12.0 -> 1.13.0
...into staging-next
[staging-next] paperless-ngx: skip newly failing test
mesa: hack around aarch64-darwin build failure
…or Requests 2.32 ...into staging-next
Well, "fix", because this just allows us to use deprecated C++ features for now, and the actual consumer of said features is boost 1.65.1, vendored inside mapbox-gl, vendored inside qtlocation, with all the upstreams in this chain being mostly dead. Anyway, this should buy us time until the next libcxx bump comes around, and then we'll have to send qt5location to a farm upstate unless someone wants to go through the entire boost codebase and precision-upgrade it.
...into staging-next
The broken chromium is quite a problem, I think. /cc maintainers: @networkException, @emilylange. |
It's included in there already, but we can't drop the patch yet, as e.g. thunderbird still needs it, as of 115.11.1.
...into staging-next
Solves the following build error: ~~~ FAILED: obj/chrome/browser/devtools/devtools/devtools_window.o In file included from ../../chrome/browser/devtools/devtools_window.cc:32: ../../chrome/browser/file_select_helper.h:16:10: fatal error: 'components/enterprise/buildflags/buildflags.h' file not found 16 | #include "components/enterprise/buildflags/buildflags.h" | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~ Can be removed once chromium and ungoogled-chromium are both on M126, since the patch is from M126. https://issues.chromium.org/issues/336911498 https://chromium-review.googlesource.com/c/chromium/src/+/5487538
13 tasks
…m-M125 [staging-next] chromium: fix building M125 with ninja 1.12
This was referenced Jun 18, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
1.severity: security
Issues which raise a security issue, or PRs that fix one
6.topic: emacs
Text editor
6.topic: kernel
The Linux kernel
6.topic: lua
6.topic: printing
6.topic: python
6.topic: qt/kde
6.topic: ruby
6.topic: rust
6.topic: systemd
6.topic: TeX
Issues regarding texlive and TeX in general
6.topic: vim
8.has: clean-up
8.has: documentation
This PR adds or changes documentation
8.has: package (new)
This PR adds a new package
10.rebuild-darwin: 501+
10.rebuild-darwin: 5001+
10.rebuild-darwin-stdenv
This PR causes stdenv to rebuild
10.rebuild-linux: 501+
10.rebuild-linux: 5001+
10.rebuild-linux-stdenv
This PR causes stdenv to rebuild
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is the first staging-next iteration that will not reach 24.05. (But there are
staging*-24.05
, as usual.)Helpful links
https://hydra.nixos.org/job/nixpkgs/staging-next/unstable#tabs-constituents
https://hydra.nixos.org/job/nixos/staging-next-small/tested
https://hydra.nixos.org/jobset/nixpkgs/staging-next
https://hydra.nixos.org/jobset/nixos/staging-next-small
Mass breakages