Hi,
As discussed during the last meeting, I made a few changes to the
tooling to handle 2 concurrent LTS releases for a short while (normally
June 12th until September 1st).
This is a new situation, due to slight changes in the release cycles
(AFAIU: LTS now starts exactly 3 years after the initial release; ELTS
starts year+5 July 1st),
(This may happen again for forky; for trixie we may have the opposite
situation with no active LTS during 2028-07; but let's not try and
predict the future too much.)
lts-cve-triage.py:
- Allow setting the target dists (--releases prev_lts lts next_lts).
During the short bullseye&bookworm-lts period, FD can run it twice:
prev_lts lts next_lts
$ bin/lts-cve-triage.py --releases buster bullseye trixie
$ bin/lts-cve-triage.py --releases buster bookworm trixie
- Allow filtering dla-needed.txt by dist.
Now all dla-needed.txt entries are in the form: package/bullseye.
'package' means both dists, 'package/dist' means only 1.
This is like ela-needed.txt and similar to dsa-needed.txt.
lts-cve-triage.py filters this appropriately and can distinguish
bullseye and bookworm package triage (as in ELTS).
bin/package-operation (private repo):
- This tool can already handle multiple ELTS dists. The code was tweaked
a bit to handle LTS similarly. Tested with --find-work and --add.
These changes were deployed immediately and are meant to work with
either 1 or 2 LTS releases. This should help find any issue before the
actual bookworm-lts switch.
Some coordinator scripts (such as the weekly report) may need attention
to handle entries in dla-needed.txt.
check-advisories doesn't care about dists, only about package versions
and tags, AFAICS it doesn't need an update.
Cheers!
Sylvain
