Hi Paul! Paul Gevers <elb...@debian.org> writes:
> Source: python-volatile > Version: 2.1.0-2 > Severity: serious > Control: close -1 2.1.0-3 > X-Debbugs-CC: jel...@debian.org > Tags: sid bookworm pending > User: release.debian....@packages.debian.org > Usertags: out-of-sync > [snip] > I have immediately closed this bug with the version in unstable, so if > that version or a later version migrates, this bug will no longer affect > testing. I have also tagged this bug to only affect sid and bookworm, so > it doesn't affect (old-)stable. > > Your package is only blocked because the arch:all binary package(s) > aren't built on a buildd. Unfortunately the Debian infrastructure > doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will > shortly do a no-changes source-only upload to DELAYED/15, closing this > bug. Please let me know if I should delay or cancel that upload. > Solving this bug justifies an upload, and I'd also like to update my email address in src:python-volatile. Normally I don't think changing an email address would justify an upload, so this is a great opportunity ;-) I will of course credit you for identifying this issue and taking the initiative to fix it, and will upload without delay once I receive your ACK (please CC me). For future reference, if there was an NMUdiff, I would incorporate it into the -4 release along with my change, but then, what is the best practise? Ask for the NMU submitter to cancel the delayed upload, upload -4 which will presumably cause -3.1 to be rejected when the delayed timer fires, or cancel the delayed upload myself? Thanks! Nicholas
signature.asc
Description: PGP signature
