I uploaded chromium-102 to bullseye-security, and I don't see armhf
binary packages. Salvatore, can you please tell me if that build failed?
I'm aware that it failed on i386, but that's for a different, new
reason (and also failed in sid). I need to deal with that separately.
On Tue, May 17, 2022 at 17:27, Salvatore Bonaccorso <car...@debian.org>
wrote:
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 <car...@debian.org <mailto:car...@debian.org>>
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
