Your message dated Sat, 12 Mar 2022 12:10:53 +0000
with message-id
<70e27e00f15582e6863125c3f1dfb412b61a4ccf.ca...@adam-barratt.org.uk>
and subject line Re: Bug#1007154: ftp.debian.org: libwebp_1.2.2-1_amd64 stuck
in "Uploaded" state
has caused the Debian Bug report #1007154,
regarding ftp.debian.org: libwebp_1.2.2-1_amd64 stuck in "Uploaded" state
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1007154: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007154
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: [email protected]
Control: affects -1 src:libwebp
libwebp_1.2.2-1 has been built successfully on all architectures' buildds,
but the amd64 build never progressed past Uploaded state. Perhaps the
upload had unlucky timing relative to recent maintenance?
Is there something that can be done to retrieve this package from wherever
it has got lost, or should I be asking for a binNMU as a workaround?
If this has got stuck because of an infrastructure issue, other packages
might be affected (libwebp just happens to be one that I've noticed
because I have both :amd64 and :i386 installed).
Thanks,
smcv
--- End Message ---
--- Begin Message ---
On Sat, 2022-03-12 at 10:59 +0000, Simon McVittie wrote:
> libwebp_1.2.2-1 has been built successfully on all architectures'
> buildds,
> but the amd64 build never progressed past Uploaded state. Perhaps the
> upload had unlucky timing relative to recent maintenance?
>
> Is there something that can be done to retrieve this package from
> wherever
> it has got lost, or should I be asking for a binNMU as a workaround?
>
Apparently it was a case of #906146, possibly combined with a failed
maintainer upload from earlier in the week also still sitting in the
upload queue.
The package has been given back and has now successfully been accepted,
so I'm closing this bug.
Regards,
Adam
--- End Message ---
