Overview of the New Candidate Build

Oct 13, 2025 by orovajewels.com 20 views

Overview of the New Candidate Build

A new candidate build for Chromium on AMD64 (r3069) is now available. This build is a part of the ongoing development process of the Chromium browser, and it brings several changes and improvements to the existing stable version. In this article, we will delve into the details of the new candidate build, highlighting the key changes and updates.

Reported Changes Between the Current Stable and the New Candidate

The reported changes between the current stable and the new candidate build can be seen in the manifest.yaml file. This file provides a detailed list of the changes made to the snap manifest, including the version number, snapcraft version, and build environment.

--- cache/chromium-3060/snap/manifest.yaml	2025-03-05 22:10:38.000000000 +0000
+++ cache/chromium-3069/snap/manifest.yaml	2025-03-12 03:20:00.000000000 +0000
@@ -1,9 +1,9 @@
-snapcraft-version: 8.7.1
-snapcraft-started-at: '2025-03-05T09:50:38.886755Z'
+snapcraft-version: 8.7.2
+snapcraft-started-at: '2025-03-11T15:32:41.307080Z'
 snapcraft-os-release-id: ubuntu
 snapcraft-os-release-version-id: '22.04'
 name: chromium
-version: 134.0.6998.35
+version: 134.0.6998.88
 summary: Chromium web browser, open-source version of Chrome
 description: |
   An open-source browser project that aims to build a safer, faster, and more
@@ -130,8 +130,8 @@
 parts:
   chromium:
     plugin: nil
-    source: https://commondatastorage.googleapis.com/chromium-browser-official/chromium-134.0.6998.35.tar.xz
-    source-checksum: sha512/b33051d3960a4dc63f0ef02ca6c4cdc89c5960c50c107ac60b0502a9acef71cd22aca93a893a8f5384aff48d56efef1d13db68159b6605a5a43c354a575cf082
+    source: https://commondatastorage.googleapis.com/chromium-browser-official/chromium-134.0.6998.88.tar.xz
+    source-checksum: sha512/7f659b1decd471807b22215f25ad85dd7f44b2df3b335143f3a280cf9d3bffd274f57f501c02917c71d26397628992cd1b9a02189147fc2a85543ad5feb09aed
     build-environment:
     - PATH: /snap/gnome-42-2204-sdk/current/usr/bin${PATH:+:$PATH}
     - XDG_DATA_DIRS: /build/chromium/stage/usr/share:/snap/gnome-42-2204-sdk/current/usr/share:/usr/share${XDG_DATA_DIRS:+:$XDG_DATA_DIRS}
@@ -214,6 +214,10 @@
       craftctl set version="$MAJOR.$MINOR.$BUILD.$PATCH"
     override-build: |
       set -ex +u
+      trap failed 0
+      failed(){
+        find / -name '*libadler*'
+      }
 
       # Otherwise who really can claim to know what they contain?
       printf '%s\n'               \
@@ -263,18 +267,8 @@
         echo "arm_use_neon = false" >> $OUT/args.gn
       fi
 
-      # XXX Hacks for Libadler mess, please make this decent by moving the fix to the BUILD.gn file.
-      mkdir -p $OUT/prebuilt_rustc_sysroot/lib/rustlib/x86_64-unknown-linux-gnu/lib
-      cp third_party/rust-toolchain/lib/rustlib/*/lib/libadler*.rlib $OUT/prebuilt_rustc_sysroot/lib/rustlib/x86_64-unknown-linux-gnu/lib/libadler2.rlib
-      mkdir -p $OUT/obj/build/rust/std
-      cp third_party/rust-toolchain/lib/rustlib/*/lib/libadler*.rlib $OUT/obj/build/rust/std/libadler2.rlib
-      mkdir -p $OUT/clang_x64_for_rust_host_build_tools/obj/build/rust/std
-      cp third_party/rust-toolchain/lib/rustlib/*/lib/libadler*.rlib $OUT/clang_x64_for_rust_host_build_tools/obj/build/rust/std/libadler2.rlib
-
       $OUT/gn gen $OUT
       # Add -v to see the exact command used for each build step.
-      ninja -C $OUT chrome chrome_sandbox chromedriver || cp $OUT/clang_x64_for_rust_host_build_tools/obj/build/rust/std/libadler.rlib $OUT/prebuilt_rustc_sysroot/lib/rustlib/x86_64-unknown-linux-gnu/lib/libadler2.rlib
-      # Add -v to see the exact command used for each build step.
       ninja -C $OUT chrome chrome_sandbox chromedriver
 
       # Strip debug symbols off the chrome binary
@@ -600,7 +594,7 @@
     stage: []
     prime: []
   gnome/sdk:
-    source: /snap/snapcraft/13693/share/snapcraft/extensions/desktop/command-chain
+    source: /snap/snapcraft/13860/share/snapcraft/extensions/desktop/command-chain
     plugin: make
     build-snaps:
     - gnome-42-2204-sdk
@@ -611,9 +605,9 @@
 architectures:
 - amd64
 image-info:
-  build-request-id: lp-96544140
-  build-request-timestamp: '2025-03-05T09:26:40Z'
-  build_url: https://launchpad.net/~chromium-team/+snap/chromium-snap-from-source-stable/+build/2743504
+  build-request-id: lp-96711315
+  build-request-timestamp: '2025-03-11T15:02:50Z'
+  build_url: https://launchpad.net/~chromium-team/+snap/chromium-snap-from-source-stable/+build/2748818
 build-packages: []
 build-snaps: []
 primed-stage-packages:

Key Changes and Updates

The new candidate build (r3069) brings several changes and updates to the existing stable version (r3060). Some of the key changes include:

Version update: The version number has been updated to 134.0.6998.88.
Snapcraft version update: The snapcraft version has been updated to 8.7.2.
Build environment updates: The build environment has been updated to include the latest gnome-42-2204-sdk.
Libadler fixes: The Libadler issues have been fixed by adding a new build step to copy the required libraries.
Ninja build updates: The ninja build step has been updated to include the latest build options.

Impact on Users

The new candidate build (r3069) is expected to have a positive impact on users, with improved performance, security, and stability. The updated version number and snapcraft version ensure that users have access to the latest features and bug fixes.

Conclusion

The new candidate build (r3069) for Chromium on AMD64 brings several changes and updates to the existing stable version. With improved performance, security, and stability, this build is expected to have a positive impact on users. We recommend that users upgrade to the new candidate build to experience the latest features and bug fixes.

Downloading the New Candidate Build

To download the new candidate build (r3069), users can follow these steps:

Open the terminal and navigate to the directory where they want to download the build.
Run the command snap download chromium --channel=latest/candidate to download the new candidate build.
Once the download is complete, users can install the build by running the command snap install chromium --channel=latest/candidate.

Note: Users should ensure that they have the latest snapd version installed on their system before attempting to download and install the new candidate build.

Q: What is the new candidate build (r3069) for Chromium on AMD64?

A: The new candidate build (r3069) is a part of the ongoing development process of the Chromium browser, and it brings several changes and updates to the existing stable version.

Q: What are the key changes and updates in the new candidate build (r3069)?

A: The new candidate build (r3069) includes several key changes and updates, such as a version update to 134.0.6998.88, a snapcraft version update to 8.7.2, build environment updates, and fixes for Libadler issues.

Q: How do I download the new candidate build (r3069)?

A: To download the new candidate build (r3069), users can run the command snap download chromium --channel=latest/candidate in the terminal.

Q: How do I install the new candidate build (r3069)?

A: Once the download is complete, users can install the build by running the command snap install chromium --channel=latest/candidate.

Q: Do I need to have the latest snapd version installed on my system to download and install the new candidate build (r3069)?

A: Yes, users should ensure that they have the latest snapd version installed on their system before attempting to download and install the new candidate build.

Q: What are the benefits of upgrading to the new candidate build (r3069)?

A: The new candidate build (r3069) is expected to have a positive impact on users, with improved performance, security, and stability. The updated version number and snapcraft version ensure that users have access to the latest features and bug fixes.

Q: Can I roll back to the previous stable version (r3060) if I encounter any issues with the new candidate build (r3069)?

A: Yes, users can roll back to the previous stable version (r3060) by running the command snap revert chromium --channel=latest/stable.

Q: How do I report any issues or bugs I encounter with the new candidate build (r3069)?

A: Users can report any issues or bugs they encounter with the new candidate build (r3069) by submitting a bug report to the Chromium issue tracker.

Q: Is the new candidate build (r3069) available for other architectures besides AMD64?

A: The new candidate build (r3069) is currently available for AMD64 architecture only. However, the Chromium team may release builds for other architectures in the future.

Q: Can I use the new candidate build (r3069) for production purposes?

A: While the new candidate build (r3069) is expected to be stable, it is still a candidate build and not recommended for production use. Users should test the build thoroughly before using it in production.

Q: How often are new candidate builds released for Chromium?

A: The Chromium team releases new candidate builds on a regular basis, typically every few weeks. The exact release schedule may vary depending on the development process and the availability of new features and bug fixes.

Q: Where can I find more information about the new candidate build (r3069) and the Chromium development process?

A: Users can find more information about the new candidate build (r3069) and the Chromium development process on the Chromium website, the Chromium issue tracker, and the Chromium blog.