[Piuparts-devel] Bug#992226: piuparts: bullseye is now stable
Nicolas Dandrimont
nicolas at dandrimont.eu
Mon Aug 16 23:18:26 BST 2021
Control: tags -1 + pending
Hi Sebastian,
On Mon, Aug 16, 2021, at 08:37, Sebastian Ramacher wrote:
> Since bullseye was release on Saturday, please change all jobs that
> start from stable (e.g., stable2sid) to use bullseye instead of buster.
I've just deployed piuparts 1.1.4 on piuparts.d.o, which updates the (old)*stable and testing aliases for the bullseye release. This should make the stable2* and testing2sid environments DTRT.
I've also deployed a followup change to make sure the test environments for bullseye-pu, bullseye-security and bullseye2next, used by SRMs, are being created and handled.
(currently deployed branch: https://salsa.debian.org/debian/piuparts/-/tree/tmp-1.1.4, until Andreas pushes his actual 1.1.4 branch on which I'll rebase the pejacevic changes).
I'll leave this bug open until we've confirmed that all results are as expected (which should show up in the next piuparts-report run).
Thanks for your work on bullseye!
Cheers,
--
Nicolas Dandrimont
More information about the Piuparts-devel
mailing list