Your message dated Sun, 08 Sep 2013 15:24:07 +0100
with message-id <1378650247.4594.18.ca...@jacala.jungle.funky-badger.org>
and subject line Re: Bug#722150: nmu: libsigrokdecode_0.2.0-2
has caused the Debian Bug report #722150,
regarding nmu: libsigrokdecode_0.2.0-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 ow...@bugs.debian.org
immediately.)
--
722150: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=722150
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian....@packages.debian.org
Usertags: binnmu
Please schedule a binNMU for libsigrokdecode. The maintainer upload was
pending in NEW for a while and still depends on python3.2.
nmu libsigrokdecode_0.2.0-2 . amd64 . -m "Rebuild against python3.3."
Ansgar
--- End Message ---
--- Begin Message ---
On Sun, 2013-09-08 at 15:36 +0200, Ansgar Burchardt wrote:
> Please schedule a binNMU for libsigrokdecode. The maintainer upload was
> pending in NEW for a while and still depends on python3.2.
>
> nmu libsigrokdecode_0.2.0-2 . amd64 . -m "Rebuild against python3.3."
Scheduled.
Regards,
Adam
--- End Message ---
