On 2016-01-13 19:57, Rolf Leggewie wrote: > On 09.01.2016 02:38, Aurelien Jarno wrote: > > Package: scanbd > > Version: 1.4.1-7 > > Severity: wishlist > > > > Dear Maintainer, > > > > scanbd has a build-depends on libusb-dev. A few years ago upstream > > has released a new major version libusb 1.0 with a different API which > > aims to fix design deficiencies with USB 2.0 and 3.0 in mind. > > > > The old libusb 0.1 package is not supported upstream anymore and should > > be considered deprecated. > > > > If scanbd supports the new libusb 1.0 library, please consider > > switching the build-depends from libusb-dev to libusb-1.0-0-dev. > > Aurelien, thank you for the heads-up. > > I specifically set the build dependency to libusb-dev to avoid > dependency on a specific version. I believe you are the maintainer of > the libusb-dev package. Do you plan to point that libusb version 1.0 > eventually? That's the way I was hoping to do the migration.
This is not really something we can do given that the two libraries have an incompatible API. Doing so might work for some package, but will break all packages that are not supporting the new version. > I tested today and the package scanbd compiles fine. The binary package > seems to run fine as well. It turns out the bug you reported would be a > non-issue on upgrade to the new API of libusb-dev. What do you suggest > to do considering my preference to stay version-agnostic in the build > dependencies. Great that it works. Please change the build-depends, libusb 1.0 is even in squeeze, so that should not be a problem for backports. The name is also unlikely to change until there is another API incompatible change, which is not something planed. Regards, Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B [email protected] http://www.aurel32.net
