Your message dated Thu, 12 Jun 2014 16:30:58 +0200
with message-id <[email protected]>
and subject line Re: Bug#746335: nmu: libvtk-dicom0.4_0.4.5-1
has caused the Debian Bug report #746335,
regarding nmu: libvtk-dicom0.4_0.4.5-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.)


-- 
746335: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746335
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: [email protected]
Usertags: binnmu

If I read and understand the following correctly:
https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=25;bug=746216

Please schedule a binNMU:

nmu libvtk-dicom0.4_0.4.5-1 . i386 kfreebsd-amd64 kfreebsd-amd64i386
mips mipsel powerpc . -m "rebuild against newer libgmp10 lib"

Thanks

--- End Message ---
--- Begin Message ---
On 29/04/14 08:35, Mathieu Malaterre wrote:
> Package: release.debian.org
> Severity: normal
> User: [email protected]
> Usertags: binnmu
> 
> If I read and understand the following correctly:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=25;bug=746216
> 
> Please schedule a binNMU:
> 
> nmu libvtk-dicom0.4_0.4.5-1 . i386 kfreebsd-amd64 kfreebsd-amd64i386
> mips mipsel powerpc . -m "rebuild against newer libgmp10 lib"

This needed a give-back (which are sent to debian-wb-team), not a binnmu. I've
given it back on i386 and kfreebsd-* (the others had already been given back).

Thanks for noticing.

Regards,
Emilio

--- End Message ---

Reply via email to