Hi, On 2024-08-14 12:59, Santiago Ruano Rincón wrote: > Dear wanna-build team, > > El 13/12/23 a las 11:56, Salvatore Bonaccorso escribió: > > Hi Sylvain, > > > > On Wed, Dec 13, 2023 at 07:50:38AM +0100, Sylvain Beucler wrote: > > > Hi all, > > > > > > Actually we have a summary of the situation here: > > > https://salsa.debian.org/lts-team/lts-extra-tasks/-/issues/51 > > > > > > We have mostly 2 options: > > > > > > 1/ General fix, involving a dak hook and some corner cases, and more > > > importantly having access to the infrastructure, > > > > > > 2/ One-off mass injection of [oldstable]-security build logs when > > > starting a > > > new LTS dist. > > > > > > > > > Given that 1/ was attempted a couple times in the past and never reached > > > completion, and given that we might solve this if the debusine [1] project > > > is adopted, I think we can drop it for now. > > > > > > Doing 2/ next August for bullseye sounds doable, solves the most immediate > > > use case (i.e. LTS devs comparing previous logs on new FTBFS), so I think > > > we > > > can privilege this option. > > > > > > What do you think? > > > > Agreed, I think doing 2/ is more sensible at this point to cover the > > need of LTS devs needing to compare previous logs. > > > > In the middle or long(er) run having logs available in public after > > they do not need anymore to be restricted is surely welcome, but as > > outlined this won't be in near future be possible with the current > > setup and more work involved. > > As suggested last December, could you please make the bullseye-security > build logs publicly available?
I have updated the configuration so that NEW bullseye-security logs are published and publicly available. Regards Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://aurel32.net
signature.asc
Description: PGP signature
