Your message dated Sun, 28 Sep 2014 19:21:03 +0100
with message-id <[email protected]>
and subject line Re: Bug#763182: nmu: libdevel-cover-perl_1.17-1
has caused the Debian Bug report #763182,
regarding nmu: libdevel-cover-perl_1.17-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.)
--
763182: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763182
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: [email protected]
Usertags: binnmu
A newer upstream version of libdevel-cover-perl was recently uploaded
(after perl 5.20.1-1 had migrated to testing), but unfortunately quite
a few buildds hadn't been updated from 5.20.0 yet so those binaries are
now uninstallable.
nmu libdevel-cover-perl_1.17-1 . i386 armel armhf kfreebsd-amd64 kfreebsd-i386
powerpc s390x . --extra-depends 'perl-base (>= 5.20.1)' -m "rebuild for Perl
5.20.1"
amd64, mips, mipsel, ppc64el, and arm64 seem to be OK.
To prevent this occurring again on the next upload, should I mail the
relevant [email protected] addresses to get the chroots updated
or do you have a process for that?
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
On 2014-09-28 14:31, Niko Tyni wrote:
A newer upstream version of libdevel-cover-perl was recently uploaded
(after perl 5.20.1-1 had migrated to testing), but unfortunately quite
a few buildds hadn't been updated from 5.20.0 yet so those binaries are
now uninstallable.
nmu libdevel-cover-perl_1.17-1 . i386 armel armhf kfreebsd-amd64
kfreebsd-i386 powerpc s390x . --extra-depends 'perl-base (>= 5.20.1)'
-m "rebuild for Perl 5.20.1"
amd64, mips, mipsel, ppc64el, and arm64 seem to be OK.
Scheduled.
To prevent this occurring again on the next upload, should I mail the
relevant [email protected] addresses to get the chroots updated
or do you have a process for that?
I don't believe we do, so please mail the arch address. That's unless
someone has a s3kr1t process I'm not aware of :)
Thanks,
--
Jonathan Wiltshire [email protected]
Debian Developer http://people.debian.org/~jmw
4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51
<directhex> i have six years of solaris sysadmin experience, from
8->10. i am well qualified to say it is made from bonghits
layered on top of bonghits
--- End Message ---
