Bug#714726: wrong (as in: release-specific) "Suite:" entry in backports Release file

2025-03-30 Thread Stefan Bühler
Hi Martin-Éric, On 29.03.25 12:30, Martin-Éric Racine wrote: la 29.3.2025 klo 13.16 Martin-Éric Racine (martin-eric.rac...@iki.fi) kirjoitti: Meanwhile Origin is still borked for Trixie. Basically, Origin=vendor i.e. it should say Debian, not Debian Backports. Also, the Label syntax remains i

Bug#714726: wrong (as in: release-specific) "Suite:" entry in backports Release file

2025-03-29 Thread Stefan Bühler
Hi, On 24.03.25 11:55, Martin-Éric Racine wrote: On Tue, 17 Aug 2021 14:30:58 +0200 Mattia Rizzolo wrote: [...] Could this at least get fixed on time for Trixie? current state: * buster-backports doesn't exist anymore * bullseye-backports broken * bookworm-backports fixed * trixie-backports

Bug#714726: wrong (as in: release-specific) "Suite:" entry in backports Release file

2025-03-29 Thread Martin-Éric Racine
la 29.3.2025 klo 13.16 Martin-Éric Racine (martin-eric.rac...@iki.fi) kirjoitti: > > la 29.3.2025 klo 13.03 Stefan Bühler (sou...@stbuehler.de) kirjoitti: > > On 24.03.25 11:55, Martin-Éric Racine wrote: > > > On Tue, 17 Aug 2021 14:30:58 +0200 Mattia Rizzolo > > > wrote: > > > [...] > > > Could

Bug#714726: wrong (as in: release-specific) "Suite:" entry in backports Release file

2025-03-29 Thread Martin-Éric Racine
la 29.3.2025 klo 13.03 Stefan Bühler (sou...@stbuehler.de) kirjoitti: > On 24.03.25 11:55, Martin-Éric Racine wrote: > > On Tue, 17 Aug 2021 14:30:58 +0200 Mattia Rizzolo wrote: > > [...] > > Could this at least get fixed on time for Trixie? > > current state: > > * buster-backports doesn't exist

Bug#714726: wrong (as in: release-specific) "Suite:" entry in backports Release file

2025-03-24 Thread Martin-Éric Racine
On Tue, 17 Aug 2021 14:30:58 +0200 Mattia Rizzolo wrote: > On Sun, Aug 15, 2021 at 02:22:28PM +0200, Stefan Bühler wrote: > > Hi again, > > > > small status update: it seems bookworm (now testing) backports was > > created correctly (yay \o/), but bullseye (now stable) wasn't fixed. > > AFAIK this

Bug#714726: wrong (as in: release-specific) "Suite:" entry in backports Release file

2021-08-17 Thread Mattia Rizzolo
On Sun, Aug 15, 2021 at 02:22:28PM +0200, Stefan Bühler wrote: > Hi again, > > small status update: it seems bookworm (now testing) backports was > created correctly (yay \o/), but bullseye (now stable) wasn't fixed. AFAIK this is wanted as ftp-master refused to update suites already created. S

Bug#714726: wrong (as in: release-specific) "Suite:" entry in backports Release file

2021-08-15 Thread Stefan Bühler
Hi again, small status update: it seems bookworm (now testing) backports was created correctly (yay \o/), but bullseye (now stable) wasn't fixed. I still doubt release.txt contains the correct instructions to update bookworm-backports to suite stable-backports on bookworm release. --- $ curl -

Bug#714726: wrong (as in: release-specific) "Suite:" entry in backports Release file

2021-02-20 Thread Stefan Bühler
Hi, it seems dak got improved [1] (or at least the release instructions), although no changes were made to the current releases afaict (not even testing/bullseye). The instructions also don't include yet the part to update the suite_name on release - backports and (proposed-)updates are in a "

Bug#714726: wrong (as in: release-specific) "Suite:" entry in backports Release file

2019-06-20 Thread Stefan Bühler
Hi, here we are again for the buster release cycle. $ curl -s http://ftp.debian.org/debian/dists/buster-backports/Release | head -n4 Origin: Debian Backports Label: Debian Backports Suite: buster-backports Codename: buster-backports $ curl -s http://ftp.debian.org/debian/dists/buster/Release | h

Bug#714726: wrong (as in: release-specific) "Suite:" entry in backports Release file

2017-06-18 Thread Stefan Bühler
Hi, On Tue, 6 Jun 2017 13:33:03 +0200 Stefan Bühler wrote: > Hi, > > On Sun, 26 Apr 2015 22:01:03 +0200 Stefano Zacchiroli > wrote: > > Heya, > > > > On Tue, Jul 02, 2013 at 10:30:40AM +0200, Stefano Zacchiroli wrote: > > > ./wheezy-backports/Release:Suite: wheezy-backports > > > ./wheezy-b

Bug#714726: wrong (as in: release-specific) "Suite:" entry in backports Release file

2017-06-06 Thread Stefan Bühler
Hi, On Sun, 26 Apr 2015 22:01:03 +0200 Stefano Zacchiroli wrote: > Heya, > > On Tue, Jul 02, 2013 at 10:30:40AM +0200, Stefano Zacchiroli wrote: > > ./wheezy-backports/Release:Suite: wheezy-backports > > ./wheezy-backports/Release:Codename: wheezy-backports > > > > as you can see from the l

Bug#714726: wrong (as in: release-specific) "Suite:" entry in backports Release file

2015-04-26 Thread Stefano Zacchiroli
Heya, On Tue, Jul 02, 2013 at 10:30:40AM +0200, Stefano Zacchiroli wrote: > ./wheezy-backports/Release:Suite: wheezy-backports > ./wheezy-backports/Release:Codename: wheezy-backports > > as you can see from the last 2 lines, both Suite and Codename are set > to "wheezy-backports" whereas, to

Bug#714726:

2013-07-26 Thread Kernc
severity 714726 important merge 714726 509574 tags 714726 patch thank you This bug is almost 5 years old and has been duplicated several times: http://bugs.debian.org/509574 I'm fairly naive, but it looks to me that wheezy-backports doesn't report the suite correctly as stable-backports, and also

Bug#714726: wrong (as in: release-specific) "Suite:" entry in backports Release file

2013-07-02 Thread Stefano Zacchiroli
Package: ftp.debian.org Severity: normal [ moving here a discussion started on #debian-dak ] It seems that the Release file for the backports suite is the only one not having a "Suite:" entry which is independent from the actual release name: $ find . -name *Release | xargs egrep '^(Codename|S