Skip to content
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 430 commits into from
Jun 12, 2024
Merged

staging-next 2024-05-31 #316075

merged 430 commits into from
Jun 12, 2024

Conversation

vcunat
Copy link
Member

@vcunat vcunat commented May 31, 2024

flokli and others added 30 commits May 23, 2024 18:48
Reapply "systemd: enable debug info"
ghostscript: 10.02.1 -> 10.03.1
boehmgc: disable tests on aarch64-linux
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
@vcunat vcunat requested a review from emilylange as a code owner June 11, 2024 10:43
github-actions bot and others added 13 commits June 11, 2024 12:01
[staging-next] paperless-ngx: skip newly failing test
mesa: hack around aarch64-darwin build failure
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.
@vcunat
Copy link
Member Author

vcunat commented Jun 12, 2024

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.
@vcunat
Copy link
Member Author

vcunat commented Jun 12, 2024

vcunat and others added 3 commits June 12, 2024 12:50
...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
…m-M125

[staging-next] chromium: fix building M125 with ninja 1.12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.