On Fri, 2022-10-07 at 00:10 +0200, Gordon Ball wrote: > * Upload to unstable and see what breaks? The experimental pseudo-excuses already say several packages break: https://qa.debian.org/excuses.php?experimental=1&package=pyyaml autopkgtest for ganeti/3.0.2-1: amd64: Regression, arm64: Regression autopkgtest for llvm-toolchain-13/1:13.0.1-7: amd64: Pass, arm64: Regression autopkgtest for satpy/0.37.1-1: amd64: Regression, arm64: Regression autopkgtest for spades/3.15.5+dfsg-1: amd64: Regression So at least these issues need to be investigated and maybe bugs filed. > * Request an archive rebuild with this version and see what breaks? Definitely. > * File bugs against all likely affected packages with a fixed date for > an upload? Definitely. I don't know if any packages in Debian have versioned dependencies on pyyaml, but if they do then it might be worth filing a transition bug. Probably also a good idea to do that anyway too. https://wiki.debian.org/Teams/ReleaseTeam/Transitions There might also be Debian services broken by pyyaml 6, but they can be dealt with during the upgrade of the debian.org machines to bookworm. -- bye, pabs https://wiki.debian.org/PaulWise
Attachment:
signature.asc
Description: This is a digitally signed message part