Hi Andres, On Mon, May 16, 2022 at 12:36:38PM -0400, Andres Salomon wrote: > On 5/16/22 11:35, Ben Steinberg wrote: > > Package: chromium > > Version: 101.0.4951.64-1~deb11u1 > > Severity: normal > > X-Debbugs-Cc: bsteinb...@law.harvard.edu > > > > 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! > > > Unfortunately, bullseye-security buildd logs don't appear to be public, so I > actually have no idea whether 101.0.4951.64-1~deb11u1 ran into problems > building on arm64. > > > 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
