Hi Wanna-Build Team,
On 19/08/2024 18:57, Aurelien Jarno wrote:
On 2024-08-14 12:59, Santiago Ruano Rincón wrote:
El 13/12/23 a las 11:56, Salvatore Bonaccorso escribió:
On Wed, Dec 13, 2023 at 07:50:38AM +0100, Sylvain Beucler wrote:
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.
Thanks for making new logs public Aurélien. Though this thread is about
a different issue:
We'd like to make old bullseye logs publicly available, e.g.
https://buildd.debian.org/status/package.php?p=wpa&suite=bullseye-security
so the LTS Team can use them as reference when analyzing future FTBFS,
as discussed in point 2 above at the end of last year.
On #debian-lts jmm and carnil recently recap'd that the old logs are
stored on master.debian.org in
/home/debian/archive/debian-security-logs, in xz-compressed mboxes (one
per month).
We'd need the Wanna-Build Team to filter out only those for bullseye (or
if that's simpler, all dists up to July since all embargoed builds were
published since), and then injects them to buildd.debian.org.
Would that be possible? :)
Cheers!
Sylvain Beucler
Debian LTS Team
