Hi,Disclaimer: I only now saw your e-mail. By default the Debian bug tracking system doesn't CC replies to the submitter of bugs.
On Sat, 9 Mar 2024 13:07:04 -0800 David Caldwell <da...@porkrind.org> wrote:
> 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.I think this failed. I got this email shortly afterward: > Subject: commit-patch_2.6.2-1_amd64.changes REJECTED > > Version check failed: > Your upload included the source package commit-patch, version 2.6.2-1, > however unstable already has version 2.6.2-1. > Uploads to unstable must have a higher version than present in unstable.
That wasn't my upload, as I uploaded version 2.6.2-1.1 (which by now has been excepted in the archive.
Is this expected or did something go wrong?
Well, the upload was rejected so didn't accomplish anything. I would be surprised if that was expected by the uploader.
Today I got this: > commit-patch 2.6-2.1 is marked for autoremoval from testing on 2024-03-29> > It is affected by these RC bugs:> 1065038: commit-patch: fails to migrate to testing for too long: uploader built arch:all binary > https://bugs.debian.org/1065038 So I think things are not in a good state. What is the solution to this?
My upload (in DELAYED at that time) fixed it. You could have prevented that message by doing a new upload yourself after I filed this bug (I prefer it when maintainers fix the issue themselves instead of me becoming responsible for a trivial upload).
Paul
OpenPGP_signature.asc
Description: OpenPGP digital signature
