Hi On 2016-01-08, Aurelien Jarno wrote: > Package: lirc > Version: 0.9.0~pre1-1.2 > Severity: wishlist > > Dear Maintainer, > > lirc has a build-depends on libftdi-dev. Upstream has released a new > major version with a slightly different API and based on libusb 1.0. The > old libusb and libftdi versions should be considered deprecated as they > are not maintained upstream anymore. [...]
[ this will be basically the same answer as for libusb, so feel free
to skip reading one ]
What is the rough time frame you have in mind for removing libftdi1
from unstable?
I'm asking because there are two options:
- pushing the current upstream version, with a transition, involving
around 30 rdepends, needing sourceful uploads for most of them, and
a rather complex device specific config migration, plus some pending
packaging work
or
- backporting (looks to be pretty reasonable) the necessary changes for
libftdi1-dev to lirc 0.9.0 (or 0.9.1, which 'only' needs the config
migration, but not the library transition and the corresponding
transition slot).
Depending on your schedule, I can look into the targeted backports,
but naturally I'd prefer to avoid that (as long as lirc won't be
one of the final blockers).
Regards
Stefan Lippers-Hollmann
pgpQ9qg5OCG3s.pgp
Description: Digitale Signatur von OpenPGP
