Your message dated Tue, 17 May 2022 17:27:43 +0200
with message-id <[email protected]>
and subject line Re: Bug#1011078: chromium: arm64 package not available in
bullseye-security
has caused the Debian Bug report #1011078,
regarding chromium: arm64 package not available in bullseye-security
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.)
--
1011078: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011078
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: chromium
Version: 101.0.4951.64-1~deb11u1
Severity: normal
X-Debbugs-Cc: [email protected]
Dear Maintainer,
Chromium 101.0.4951.64-1~deb11u1 has been accepted for bullseye-security, and
the package
is present for the amd64 architecture. I think it has been built for arm64, but
it has not
yet appeared at
http://security.debian.org/debian-security/pool/main/c/chromium/ -- I know
there's a lag between amd64 and arm64 builds, but I think this is longer than
usual.
Please let me know if there's a better place to report this kind of issue.
Thanks!
-- System Information:
Debian Release: 11.3
APT prefers stable-security
APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: arm64 (aarch64)
Kernel: Linux 5.10.104-linuxkit (SMP w/6 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_RANDSTRUCT
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to
C.UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: unable to detect
Versions of packages chromium depends on:
ii chromium-common 101.0.4951.41-1~deb11u1
ii libasound2 1.2.4-1.1
ii libatk-bridge2.0-0 2.38.0-1
ii libatk1.0-0 2.36.0-2
ii libatomic1 10.2.1-6
ii libatspi2.0-0 2.38.0-4
ii libc6 2.31-13+deb11u3
ii libcairo2 1.16.0-5
ii libcups2 2.3.3op2-3+deb11u1
ii libdbus-1-3 1.12.20-2
ii libdrm2 2.4.104-1
ii libevent-2.1-7 2.1.12-stable-1
ii libexpat1 2.2.10-2+deb11u3
ii libflac8 1.3.3-2+deb11u1
ii libfontconfig1 2.13.1-4.2
ii libfreetype6 2.10.4+dfsg-1
ii libgbm1 20.3.5-1
ii libgcc-s1 10.2.1-6
ii libglib2.0-0 2.66.8-1
ii libgtk-3-0 3.24.24-4+deb11u2
ii libjpeg62-turbo 1:2.0.6-4
ii libjsoncpp24 1.9.4-4
ii liblcms2-2 2.12~rc1-2
ii libminizip1 1.1-8+b1
ii libnspr4 2:4.29-1
ii libnss3 2:3.61-1+deb11u2
ii libopenjp2-7 2.4.0-3
ii libopus0 1.3.1-0.1
ii libpango-1.0-0 1.46.2-3
ii libpng16-16 1.6.37-3
ii libpulse0 14.2-2
ii libre2-9 20210201+dfsg-1
ii libsnappy1v5 1.1.8-1
ii libstdc++6 10.2.1-6
ii libwebp6 0.6.1-2.1
ii libwebpdemux2 0.6.1-2.1
ii libwebpmux3 0.6.1-2.1
ii libx11-6 2:1.7.2-1
ii libxcb1 1.14-3
ii libxcomposite1 1:0.4.5-1
ii libxdamage1 1:1.1.5-2
ii libxext6 2:1.3.3-1.1
ii libxfixes3 1:5.0.3-2
ii libxkbcommon0 1.0.3-2
ii libxml2 2.9.10+dfsg-6.7+deb11u1
ii libxrandr2 2:1.5.1-1
ii libxslt1.1 1.1.34-4
ii zlib1g 1:1.2.11.dfsg-2
Versions of packages chromium recommends:
ii chromium-sandbox 101.0.4951.41-1~deb11u1
Versions of packages chromium suggests:
ii chromium-driver 101.0.4951.41-1~deb11u1
ii chromium-l10n 101.0.4951.41-1~deb11u1
pn chromium-shell <none>
Versions of packages chromium-common depends on:
ii libc6 2.31-13+deb11u3
ii libstdc++6 10.2.1-6
ii libx11-6 2:1.7.2-1
ii libxext6 2:1.3.3-1.1
ii x11-utils 7.7+5
ii xdg-utils 1.1.3-4.1
ii zlib1g 1:1.2.11.dfsg-2
Versions of packages chromium-common recommends:
ii chromium-sandbox 101.0.4951.41-1~deb11u1
ii fonts-liberation 1:1.07.4-11
ii libgl1-mesa-dri 20.3.5-1
ii libu2f-udev 1.1.10-3
ii notification-daemon 3.20.0-4
ii system-config-printer 1.5.14-1
ii upower 0.99.11-2
Versions of packages chromium-driver depends on:
ii libatomic1 10.2.1-6
ii libc6 2.31-13+deb11u3
ii libevent-2.1-7 2.1.12-stable-1
ii libgcc-s1 10.2.1-6
ii libglib2.0-0 2.66.8-1
ii libminizip1 1.1-8+b1
ii libnspr4 2:4.29-1
ii libnss3 2:3.61-1+deb11u2
ii libre2-9 20210201+dfsg-1
ii libstdc++6 10.2.1-6
ii libxcb1 1.14-3
ii zlib1g 1:1.2.11.dfsg-2
Versions of packages chromium-sandbox depends on:
ii libc6 2.31-13+deb11u3
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi,
On Mon, May 16, 2022 at 03:53:25PM -0400, Andres Salomon wrote:
> clone 1011078 -1
> retitle -1 chromium: i386 and armhf packages FTBFS in bullseye
> tags -1 bullseye ftbfs
> severity -1 serious
> thanks
>
> On Mon, 16 May 2022 20:33:46 +0200
> Salvatore Bonaccorso <[email protected]> wrote:
> [...]
> > Hi Andres,
> >
> > On Mon, May 16, 2022 at 12:36:38PM -0400, Andres Salomon wrote:
> > > On 5/16/22 11:35, Ben Steinberg wrote:
> > >
> > > Security Team, is there a way for me to get access to the logs for
> > > chromium's security builds by ssh'ing into a machine? Or some other
> > > way for me to view them?
> >
> > The build logs are not public but we can retrieve them. But in this
> > case from #debian-buildd:
> >
> > [17:58] < carnil> Hi, can someone double check if chromium/arm64
> > build for bullseye-security is still really in building state?
> > [18:07] < jcristau> carnil: it is not [18:07] < jcristau> guessing
> > the host crashed a few days ago and it got a power cycle
> >
> > Which I did and the package is not back in building state for arm64.
> >
> > Regards,
> > Salvatore
> >
>
> Okay, so arm64 should be building now (thanks Salvatore!). Assuming no
> build failures, they should show up in the archive in a day or two.
> Chromium is a slow build. :)
They where built now!
Regards,
Salvatore
--- End Message ---
