Your message dated Thu, 7 Dec 2017 03:36:50 +0100
with message-id <[email protected]>
and subject line Re: nmu: xerces-c_3.2.0+debian-2
has caused the Debian Bug report #882576,
regarding nmu: xerces-c_3.2.0+debian-2
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.)
--
882576: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882576
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: [email protected]
Usertags: binnmu
Hi,
xerces-c is in transition (#881127) and has built successfully on all
archs except hurd. However, based on my research into the failure, I
believe this failure may be transient, and would like to request a
binNMU for hurd arch only.
Thanks,
Bill
nmu xerces-c_3.2.0+debian-2 . hurd . unstable . -m "Rebuild due to suspected
transient failure"
-- System Information:
Debian Release: 9.0
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64
(x86_64)
Foreign Architectures: i386
Kernel: Linux 4.9.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
On Fri, 24 Nov 2017 00:32:33 -0500 William Blough <[email protected]> wrote:
> nmu xerces-c_3.2.0+debian-2 . hurd . unstable . -m "Rebuild due to suspected
> transient failure"
Solved by a give-back.
Andreas
--- End Message ---
