Your message dated Thu, 27 Oct 2016 06:06:00 +0000
with message-id <93149ea2-28fd-8c76-b670-b41479715...@thykier.net>
and subject line Re: nmu: Please binNMU bmusb against newer libusb-1.0
has caused the Debian Bug report #842206,
regarding nmu: Please binNMU bmusb against newer libusb-1.0
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.)
--
842206: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842206
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
User: release.debian....@packages.debian.org
Usertags: binnmu
Severity: normal
Hi,
bmusb can benefit strongly from being linked to libusb-1.0 (>= 2:1.0.21-1).
Do you think it would be possible to schedule a binNMU for all architectures?
Once upon a time, the format was something like
nmu bmusb_0.5.2-2 . ANY . -m "Rebuild against libusb-1.0 version with support
for zerocopy USB."
Thanks!
/* Steinar */
--
Homepage: https://www.sesse.net/
--- End Message ---
--- Begin Message ---
On Wed, 26 Oct 2016 23:57:10 +0200 "Steinar H. Gunderson"
<se...@debian.org> wrote:
> Package: release.debian.org
> User: release.debian....@packages.debian.org
> Usertags: binnmu
> Severity: normal
>
> Hi,
>
> bmusb can benefit strongly from being linked to libusb-1.0 (>= 2:1.0.21-1).
> Do you think it would be possible to schedule a binNMU for all architectures?
> Once upon a time, the format was something like
>
> nmu bmusb_0.5.2-2 . ANY . -m "Rebuild against libusb-1.0 version with support
> for zerocopy USB."
>
> Thanks!
>
> /* Steinar */
> --
> Homepage: https://www.sesse.net/
>
>
Scheduled, thanks.
~Niels
--- End Message ---
