-
Notifications
You must be signed in to change notification settings - Fork 194
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
chromium: update to 115.0.5790.170 #741
Conversation
I'll add the detailed description later, maybe you can please start testing already? @nrpt-m |
Sure, I am starting the testing. |
b90eb06
to
fcbb743
Compare
Updated the commit message and PR description. |
@MaxIhlenfeldt
Next, starting with kirkstone, dunfell & mickledore branches. |
fcbb743
to
f549ba4
Compare
Patch 0035-... has been merged upstream as https://crrev.com/c/4767547, so I updated the patch file (+ commit message and PR description) accordingly. |
How to get meta-clang/dunfell-clang14 ? |
The |
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.
The changes look fine to me. The MTE patch is a bit scary, but I guess it's the best we can do at the moment.
I just have no idea what to do with the dunfell-clang14 branch :/
Not sure what you mean by scary, but luckily we can drop it once we use clang >= 15 everywhere.
Me neither, but we definitely need it for this update. @kraj how do you suggest we proceed with kraj/meta-clang#835? |
@MaxIhlenfeldt Have completed the builds & testing in kirkstone branch for all these below systems and chromium worked well in all these systems.
Next, starting with dunfell & mickledore branches. |
@MaxIhlenfeldt , Could you please check these errors. |
@nrpt-m Is |
Sorry, I missed it "PREFERRED_VERSION_nodejs-native = "14.%". |
FYI, I'll be ooo tomorrow and the rest of the week. I suppose it's a bit optimistic, but should there be progress regarding the |
@MaxIhlenfeldt @rakuco ,
**RPi4/dunfell the "network service crashed" problem is still there. |
@MaxIhlenfeldt & @rakuco
If you are agree with all these above test results then, we are good to go for merge. |
Thank you for testing! Everything looks fine from my side too, but we need to figure out the dunfell-clang14 situation first. |
f549ba4
to
ca9f34e
Compare
Release notes: https://chromereleases.googleblog.com/2023/07/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2023/07/stable-channel-update-for-desktop_20.html https://chromereleases.googleblog.com/2023/07/stable-channel-update-for-desktop_25.html https://chromereleases.googleblog.com/2023/08/stable-channel-update-for-desktop.html Build and patch changes: ------------------------ Drop 0019-Backport-constexpr-std-string-fixes.patch, 0022-Backport-Avoid-capturing-structured-bindings.patch, 0026-Backport-std-string-ends_with-is-C-20.-Use-base-Ends.patch, and 0030-Backport-Avoid-operator-which-is-C-20-specific.patch as they are included upstream now. Add one more fix to 0018-Only-default-operator-on-declaration.patch, which previously was part of 0030-Backport-Avoid-operator-which-is-C-20-specific.patch to prevent a conflict. Also drop some fixes that are now included upstream. Drop some fixes from 0021-Add-missing-typename-s.patch that are now included upstream, and add two new ones. Add one more fix to 0028-Avoid-capturing-structured-bindings.patch. Add 0033-Revert-Reland-Reland-mte-refactor-the-tagging-functi.patch to work around a bug in clang 14 that leads to a build error. Add 0034-Avoid-parenthesized-initialization-of-aggregates.patch to fix build errors with clang < 16. Add 0035-Backport-IWYU-for-chromedriver-chrome-client_hints.h.patch to fix a build error. Rebase remaining patches. License changes: ---------------- Added licenses: * third_party/beto-core/LICENSE - https://chromium-review.googlesource.com/c/chromium/src/+/4444306 * third_party/devtools-frontend/src/front_end/third_party/puppeteer-replay/package/LICENSE - https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/4480871 Removed licenses: none. Updated licenses: none. Test-built: ----------- * chromium-ozone-wayland: - mickledore, clang, MACHINE=qemuarm64 - kirkstone, clang, MACHINE=raspberrypi4-64 * chromium-x11 - dunfell, clang**, MACHINE=raspberrypi4-64 ** Please note that Chromium requires below set-up when on dunfell branch. - The clang version to be >= 14 and for that, use the latest meta-clang/dunfell-clang14 branch. - Require the latest meta-oe with Nodejs 14.x support. - Add the PREFERRED_VERSION_nodejs-native = "14.%" in conf/local.conf file. Signed-off-by: Max Ihlenfeldt <[email protected]>
ca9f34e
to
6615360
Compare
@rakuco , |
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.
The dunfell-clang14 branch was finally created in meta-clang last Friday, so I'll go ahead and merge this PR while Max is OoO.
Release notes:
https://chromereleases.googleblog.com/2023/07/stable-channel-update-for-desktop.html
https://chromereleases.googleblog.com/2023/07/stable-channel-update-for-desktop_20.html
https://chromereleases.googleblog.com/2023/07/stable-channel-update-for-desktop_25.html
https://chromereleases.googleblog.com/2023/08/stable-channel-update-for-desktop.html
Build and patch changes:
Drop 0019-Backport-constexpr-std-string-fixes.patch,
0022-Backport-Avoid-capturing-structured-bindings.patch,
0026-Backport-std-string-ends_with-is-C-20.-Use-base-Ends.patch, and
0030-Backport-Avoid-operator-which-is-C-20-specific.patch as they are
included upstream now.
Add one more fix to 0018-Only-default-operator-on-declaration.patch,
which previously was part of
0030-Backport-Avoid-operator-which-is-C-20-specific.patch to prevent a
conflict. Also drop some fixes that are now included upstream.
Drop some fixes from 0021-Add-missing-typename-s.patch that are now
included upstream, and add two new ones.
Add one more fix to 0028-Avoid-capturing-structured-bindings.patch.
Add 0033-Revert-Reland-Reland-mte-refactor-the-tagging-functi.patch to
work around a bug in clang 14 that leads to a build error.
Add 0034-Avoid-parenthesized-initialization-of-aggregates.patch to fix
build errors with clang < 16.
Add 0035-Backport-IWYU-for-chromedriver-chrome-client_hints.h.patch to
fix a build error.
Rebase remaining patches.
License changes:
Added licenses:
Removed licenses: none.
Updated licenses: none.
Test-built:
** Please note that Chromium requires below set-up when on dunfell
branch.
meta-clang/dunfell-clang14 branch.
file.
Signed-off-by: Max Ihlenfeldt [email protected]