Re: oldstable-backports suite causes debmirror to choke

Vivian Pots <[email protected]> Mon, 10 Mar 2025 09:59:33 -0400
Newsgroups gmane.linux.debian.backports.general
Message-ID <[email protected]>
Whoops; It's due to it expecting the suite to be set to 
oldstable-backports, rather than bullseye-backports, which it is 
currently set to. In the rest of the Debian repos, once stable moves to 
oldstable, their suite name changes too. debmirror relies upon this 
behavior, and thus backports not doing the same causes it to error out 
when fetching with the suite name.

On 10/03/2025 09:57, Vivian Pots wrote:
> It's due to it expecting the suite being set to bullseye-backports 
> rather than oldstable-backports. The signature is not expired on the 
> release.
> 
> Errors:
>   Broken Release file: neither Codename nor Suite matches oldstable- 
> backports
> 
> https://ftp.osuosl.org/debian/dists/bullseye-backports/Release
> 
> On 10/03/2025 09:51, Alexander Wirt wrote:
>> On Thu, Mar 06, 2025 at 10:24:41AM -0500, Vivian Pots wrote:
>>> oldstable-backports suite is set to bullseye-backports, which causes
>>> debmirror to fail with "neither Codename nor Suite matches
>>> oldstable-backports" when trying to mirror using the name
>>> oldstable-backports, considering the oldstable-backports Release as 
>>> invalid.
>>
>> As the error message says the release file is invalid.
>> oldstable-backports is not supported anymore, therefore the signature on
>> the release file is probably expired.
>>
>> Alex
>>
>