Hi Sylvain, On Sun, Jul 5, 2026 at 5:11 PM Sylvain Beucler <[email protected]> wrote: > > I want to flag the growing size of our security-tracker git > > repositories and see how y'all feel about tackling it. I brought this > > up at the last LTS meeting and was glad to hear I'm not alone. :) > > Please, let's not all spend time investigating this issue independently :)
Yes - I didn't plan to, except I was immediately affected by it whilst setting up the new machine and then subsequent pulls. I had to do it for myself at least. :) And since I have 96 gigs of RAM, I decided to give it a go and run some quick benchmarks and experiments. But that's all, I've got the history in place now. So I'll let y'all push for this. > As discussed during said meeting, Helmut, Santiago and I have already > put some hours into this, including exchanging with the security team. > Much is detailed in the meeting notes: > https://lists.debian.org/debian-lts/2026/06/msg00045.html > in the debian-security / debian-security-tracker mailing lists: > https://lists.debian.org/debian-security/2026/06/msg00001.html > https://lists.debian.org/debian-security-tracker/2026/06/msg00009.html > https://lists.debian.org/debian-security-tracker/2026/07/msg00006.html > and in my monthly report: > https://lists.debian.org/debian-lts/2026/07/msg00004.html > > Current work-arounds are also documented: > https://lts-team.pages.debian.net/cve-triage.html#debian-security-tracker Fab! - u
