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

chromium: Update to 131.0.6778.85 #852

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

MaxIhlenfeldt
Copy link
Collaborator

Fixes #848.

Release notes:
https://chromereleases.googleblog.com/2024/11/stable-channel-update-for-desktop_12.html
https://chromereleases.googleblog.com/2024/11/stable-channel-update-for-desktop_19.html

Build and patch changes:

Rebase patches.

License changes:

Added licenses:

  • third_party/android_deps/libs/org_jspecify_jspecify/LICENSE
  • third_party/devtools-frontend/src/front_end/third_party/json5/LICENSE
  • third_party/ink/LICENSE
  • third_party/ink_stroke_modeler/LICENSE

Removed licenses:

  • third_party/catapult/third_party/httplib2/LICENSE

Updated licenses: None.

Test-built (big thanks to @SoumyaWind):

  • chromium-ozone-wayland:
  • master, clang, MACHINE=qemux86-64
  • styhead, clang, MACHINE=raspberrypi4-64
  • scarthgap, clang, MACHINE=qemux86-64
  • chromium-x11:
  • master, clang, MACHINE=qemuarm, qemuarm64, qemux86-64, raspberrypi4-64
  • scarthgap, clang, MACHINE=qemuarm, qemuarm64, qemux86-64, raspberrypi4-64

Fixes OSSystems#848.

Release notes:
    https://chromereleases.googleblog.com/2024/11/stable-channel-update-for-desktop_12.html
    https://chromereleases.googleblog.com/2024/11/stable-channel-update-for-desktop_19.html

Build and patch changes:
------------------------

Rebase patches.

License changes:
----------------

Added licenses:
  * third_party/android_deps/libs/org_jspecify_jspecify/LICENSE
  - https://chromium-review.googlesource.com/c/chromium/src/+/5898977

  * third_party/devtools-frontend/src/front_end/third_party/json5/LICENSE
  - https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/5920841

  * third_party/ink/LICENSE
  - https://chromium-review.googlesource.com/c/chromium/src/+/5530802

  * third_party/ink_stroke_modeler/LICENSE
  - https://chromium-review.googlesource.com/c/chromium/src/+/5530867

Removed licenses:
  * third_party/catapult/third_party/httplib2/LICENSE
  - https://chromium-review.googlesource.com/c/catapult/+/5858365

Updated licenses: None.

Test-built (big thanks to @SoumyaWind):
---------------------------------------

* chromium-ozone-wayland:
 - master, clang,    MACHINE=qemux86-64
 - styhead, clang,   MACHINE=raspberrypi4-64
 - scarthgap, clang, MACHINE=qemux86-64

* chromium-x11:
 - master, clang,    MACHINE=qemuarm, qemuarm64, qemux86-64, raspberrypi4-64
 - scarthgap, clang, MACHINE=qemuarm, qemuarm64, qemux86-64, raspberrypi4-64

Signed-off-by: Max Ihlenfeldt <[email protected]>
@MaxIhlenfeldt
Copy link
Collaborator Author

Uploading as a draft because the build will currently fail on Scarthgap, because upstream now requires Rust 1.78 and Scarthgap only has 1.75. However, I reached out to the maintainer of meta-lts-mixins' kirkstone/rust branch (which currently has Rust 1.78), and he told me:

It has been my plan to create a scarthgap/rust when required, and I
mentioned on the YP call this week that my goal is to produce the initial
version for next week. Someone else just posted their initial take on one
as well, though their usecase is different, and I suspect we'll end up with
myself as maintainer.

I don't think it makes sense to create a patch to temporarily get upstream's Rust requirement back down to 1.75 when we can just wait until next week and then require meta-lts-mixins' new scarthgap/rust branch.

wdyt?

@MaxIhlenfeldt
Copy link
Collaborator Author

@SoumyaWind as always, testing would be greatly appreciated! Note that the Scarthgap build currently doesn't work as mentioned in my previous comment. I also added a Styhead build to my own testing setup, not sure if you want to do the same.

@SoumyaWind
Copy link

@MaxIhlenfeldt ok, I will start testing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

chromium: Update to 131
2 participants