Your message dated Mon, 17 Sep 2012 12:18:22 +0200
with message-id <[email protected]>
and subject line Re: Bug#686461: libusb: Future plans for libusb-0.1
has caused the Debian Bug report #686461,
regarding libusb: Future plans for libusb-0.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.)


-- 
686461: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686461
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: libusb
Source-Version: 2:0.1.12-20
Severity: wishlist
Tags: upstream

Dear Maintainer,

the latest upstream version of libusb-0.1 is 0.1.12 (released in March 2006);

to make the legacy applications work with the current libusb-1.0,
a compatibilty layer package called libusb-compat-0.1 has been released on the 
libusb upstream site;

meanwhile, Debian has switched from libusb-1.0 (http://www.libusb.org/) to its 
fork called libusbx (http://libusbx.org/).

What are the future plans for the legacy libusb-0.1 library support in Debian?


-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

--- End Message ---
--- Begin Message ---
On Sun, Sep 02, 2012 at 12:25:42AM +0400, Bob Bib wrote:
> Source: libusb
> Source-Version: 2:0.1.12-20
> Severity: wishlist
> Tags: upstream
> 
> Dear Maintainer,
> 
> the latest upstream version of libusb-0.1 is 0.1.12 (released in March 2006);
> 
> to make the legacy applications work with the current libusb-1.0,
> a compatibilty layer package called libusb-compat-0.1 has been released on 
> the libusb upstream site;
> 
> meanwhile, Debian has switched from libusb-1.0 (http://www.libusb.org/) to 
> its fork called libusbx (http://libusbx.org/).
> 
> What are the future plans for the legacy libusb-0.1 library support in Debian?
> 

The plan is to continue to maintain the legacy libusb-0.1 library as
long as they are many package using it. When this number is getting
low (let's say below 50 packages), we'll force the remaining packages to
use the libusb/libusbx 1.0.

There is no plan to use the libusb-compat-0.1 library so far, as it
seems to not be fully compatible with the original library. For example
libftdi is not able to use the async mode with libusb-0.1. That's why we
prefer to fix bugs in libusb-0.1 instead of using libusb-compat-0.1 (and
Debian carries a few patches there).

As I guess the point of the bug was to ask the status, and it is given
in this mail, I am closing it.

-- 
Aurelien Jarno                          GPG: 1024D/F1BCDB73
[email protected]                 http://www.aurel32.net

--- End Message ---

Reply via email to