Your message dated Fri, 12 Jun 2020 22:55:53 +0200
with message-id <[email protected]>
and subject line Re: Bug#962722: nmu: md4c_0.4.4-1
has caused the Debian Bug report #962722,
regarding nmu: md4c_0.4.4-1
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.)
--
962722: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962722
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: [email protected]
Usertags: binnmu
Hi,
The last upload of md4c went through NEW and thus I'm requesting a binNMU to
have the amd64 packages rebuilt on buildd, such that the package can transition
to testing.
nmu md4c_0.4.4-1 . amd64 . unstable . -m "Rebuild amd64 package on the buildd
so it can transition."
--
Med vänliga hälsningar
Patrick Franz
--- End Message ---
--- Begin Message ---
On 2020-06-12 20:44:23 +0200, Patrick Franz wrote:
> Package: release.debian.org
> Severity: normal
> User: [email protected]
> Usertags: binnmu
>
> Hi,
>
> The last upload of md4c went through NEW and thus I'm requesting a binNMU to
> have the amd64 packages rebuilt on buildd, such that the package can
> transition to testing.
>
> nmu md4c_0.4.4-1 . amd64 . unstable . -m "Rebuild amd64 package on the buildd
> so it can transition."
Scheduled, but binNMUed everywhere since the package provides MA: same
binaries.
Cheers
--
Sebastian Ramacher
signature.asc
Description: PGP signature
--- End Message ---
