Your message dated Fri, 15 Aug 2025 13:30:06 -0400
with message-id <[email protected]>
and subject line Re: Bug#1111208: Trixie Chromium Arm64 build failure
has caused the Debian Bug report #1111208,
regarding Trixie Chromium Arm64 build failure
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1111208: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1111208
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: chromium
Version: 139.0.7258.127-1~deb13u1
It looks like the build for arm64 recently failed or got lost for Chromium:
https://packages.debian.org/trixie/chromium
Normally this is not an issue the user just gets an old package but in
this case it prevents chromium-l10n from being installed and does not
allow installation if that package is installed.
20.14 The following packages have unmet dependencies:
20.14 chromium-l10n : Depends: chromium (>= 139.0.7258.127-1~deb13u1)
but 138.0.7204.183-1 is to be installed
20.14 E: Unable to correct problems, you have held broken packages.
20.14 E: The following information from --solver 3.0 may provide
additional context:
20.14 Unable to satisfy dependencies. Reached two conflicting decisions:
20.14 1. chromium-l10n:arm64=139.0.7258.127-1~deb13u1 is selected for install
20.14 2. chromium-l10n:arm64=139.0.7258.127-1~deb13u1 Depends
chromium (>= 139.0.7258.127-1~deb13u1)
20.14 but none of the choices are installable:
20.14 [no choices]
If you need any more information please let me know.
Ryan Kuba
--- End Message ---
--- Begin Message ---
Hi,
Thanks for the bug report, but it's not lost - it's just building very
slowly. This unfortunately is common for armhf and arm64, about half of
the buildds for those architectures are fast, and the other half are
very slow (taking almost 3 days to build chromium).
* chromium/arm64
| chromium:
| Package : chromium
| Version : 139.0.7258.127-1~deb13u1
| Builder : buildd_arm64-arm-ubc-01
| State : Building
| Section : misc
| Priority : optional
| Previous-State : Needs-Build
| State-Change : 2025-08-13 21:07:14.301937
| CalculatedPri : 420
| component : main
| Distribution : trixie-security
| Notes : uncompiled
| State-Days : 1
| State-Time : 158899
The worst part is that I don't always notice right away when the build
fails for an architecture, so it's actually useful to have users file
bugs (or at least email me) when they notice something is missing! But
users also can't see the buildd status, so they won't know whether the
build for their architecture failed, or if the buildd is just being
slow. 🤷
Thanks,
Andres
On 8/15/25 10:31, Ryan Kuba wrote:
Package: chromium
Version: 139.0.7258.127-1~deb13u1
It looks like the build for arm64 recently failed or got lost for Chromium:
https://packages.debian.org/trixie/chromium
<https://packages.debian.org/trixie/chromium>
Normally this is not an issue the user just gets an old package but in
this case it prevents chromium-l10n from being installed and does not
allow installation if that package is installed.
20.14 The following packages have unmet dependencies:
20.14 chromium-l10n : Depends: chromium (>= 139.0.7258.127-1~deb13u1)
but 138.0.7204.183-1 is to be installed
20.14 E: Unable to correct problems, you have held broken packages.
20.14 E: The following information from --solver 3.0 may provide
additional context:
20.14 Unable to satisfy dependencies. Reached two conflicting decisions:
20.14 1. chromium-l10n:arm64=139.0.7258.127-1~deb13u1 is selected for
install
20.14 2. chromium-l10n:arm64=139.0.7258.127-1~deb13u1 Depends
chromium (>= 139.0.7258.127-1~deb13u1)
20.14 but none of the choices are installable:
20.14 [no choices]
If you need any more information please let me know.
Ryan Kuba
--- End Message ---
