Bug#1107236: tracker.debian.org: stop showing unmaintained bullseye-backports

Raphael Hertzog <[email protected]>
Newsgroups gmane.linux.debian.devel.quality-assurance
Message-ID <aD7zBWzr9uOak2xw__26887.357740064$1748956047$gmane$org@t14-buxy.home.ouaza.com>
Hi,

On Tue, 03 Jun 2025, Simon McVittie wrote:
> As announced in 
> https://lists.debian.org/debian-backports-announce/2024/07/msg00000.html, 
> bullseye-backports no longer accepts uploads and should not be expected to
> be up-to-date with bookworm{,-security}. I think it would make sense to
> drop it from the "versions" and "versioned links" panels on the package
> tracker at this point.

Why?

I mean it doesn't disappear from the rmadison output either, and I see
that table as a web version of "rmadison".

I typically remove tracking of such distributions when they are no
longer available on the local mirror and when jobs are failing due to
that. :-)

So arguably the question could become "why do we keep repositories that
we can't update on ftp-master.debian.org"?

> (For future branches, this happens at the same time that the base suite is 
> handed over from the security team to the LTS team, approximately 1 year 
> after the next stable release.

FWIW, the LTS team agreed with security team and release team to say that
the handover happens 3 years after the release, and no longer 1 year after
the next stable release. I guess the backports team could follow the same
logic... though to be fair, I'd prefer if DD were allowed to maintain
backports 5 years if that's their wish.

Cheers,
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.