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 "MOVE STUFF AROUND:" section [2] that manipulates symlinks but doesn't actually update suite_name in the database (contrary to most suites [3] which are handled by a "rename-suite" function [4]). The "rename-suite" won't work with broken suites - as its database updates are based on the previous "suite_name" value (which is the part that is broken right now afaict). I hope this is going to work out somehow - and it is nice to see some progress was made :) cheers, Stefan [1]: https://salsa.debian.org/ftp-team/dak/-/commit/bc0f26a328ff6f3a26ff0f04a6e51a8ac6cd5e7f [2]: https://salsa.debian.org/ftp-team/dak/-/blob/8f090ecf549fcc8713af3e2a993fc52bcd66bc91/docs/release.txt#L117-136 [3]: https://salsa.debian.org/ftp-team/dak/-/blob/8f090ecf549fcc8713af3e2a993fc52bcd66bc91/docs/release.txt#L69-84 [4]: https://salsa.debian.org/ftp-team/dak/-/blob/8f090ecf549fcc8713af3e2a993fc52bcd66bc91/docs/release.txt#L15-42 On 20.06.19 14:06, Stefan Bühler wrote: > 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 | head -n4 > Origin: Debian > Label: Debian > Suite: testing > Codename: buster > > The Suite for buster-backports should be "testing-backports" right now > and become "stable-backports" when buster gets released. > > cheers, > Stefan > > On 18.06.17 09:46, Stefan Bühler wrote: >> 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 <[email protected]> >>> 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 last 2 lines, both Suite and Codename are set >>>>> to "wheezy-backports" whereas, to be consistent with the rest, the >>>>> suite should be something like "stable-backports". >>>> >>>> JFTR, it looks like this bug has been propagated to the just released >>>> suite Jessie. Currently, >>>> http://ftp.debian.org/debian/dists/jessie-backports/Release reads: >>>> >>>> Suite: jessie-backports >>>> Codename: jessie-backports >>>> >>>> To cope with this, I've just hard-coded yet another release name in >>>> sources.d.n configuration, to make sure that the new backports suite is >>>> included. >>>> >>>> It would be nice to fix this now for jessie+1. >>> >>> Didn't work out so far, stretch is affected by this as well: >>> >>> $ curl -s http://ftp.debian.org/debian/dists/stretch-backports/Release >>> Origin: Debian Backports >>> Label: Debian Backports >>> Suite: stretch-backports >>> Codename: stretch-backports >>> [...] >>> >>> Maybe this could still be fixed in time? I guess right now "Suite" >>> should read "testing-backports", hoping it becomes "stable-backports" on >>> release. >> >> Still broken after the stretch release. Maybe this time just fix it >> although it is already released (right now there is nothing in it yet >> anyway)? >> >> As a workaround if someone wants to pin: >> >> Pin: release o=Debian Backports,a=stable-backports >> >> They should pin instead or additionally: >> >> Pin: release o=Debian Backports,n=stretch-backports >> >> Or (if you don't mix oldstable / stable backports sources): >> >> Pin: release o=Debian Backports >> >> Pinning a=stretch-backports ("a=" instead of "n="!) might work now, but >> breaks if this bug gets fixed. >> >> cheers, >> Stefan >>
