Hi Yves, > On Sat, 2019-10-05 at 15:45 +0200, Yves-Alexis Perez wrote: >> Package: release.debian.org >> Severity: normal >> User: release.debian.org@packages.debian.org >> Usertags: binnmu > >> nmu libimobiledevice_1.2.1~git20181030.92c5462-1 . ANY . unstable . -m >> "rebuild against newer libusbmuxd" > >> Hi, > >> I recently updated the idevices stack in Debian (libplist, libusbmuxd, >> libimobiledevice etc.). Upstream doesn't release packages anymore, so I >> do snapshots myselfs, and missed an interface break in libusbmuxd: > >> https://github.com/libimobiledevice/libusbmuxd/commit/f5a7387a54ae08c9cd1d83a415393e0e909dc6e6#diff-038b1c435b1baca0fc7faaf5e375f401L37 > >> This bug is causing crashes in applications linked against >> libimobiledevice (like #941703). > >> I've uploaded an updated libimobiledevice built against the updated >> libusbmuxd, but it's currently sitting in NEW. While a proper solution >> should be found long term (and I'll ask upstream about that), for now >> would it be possible to rebuild libimobiledevice against the newer >> libusbmuxd? > > I've opened an issue upstream ( > https://github.com/libimobiledevice/libusbmuxd/issues/81), which will bump the > soname, but that'll still sit in NEW which doesn't seem really fast these > days. > > Regards, Sorry for taking so long, but I have the feeling that the binNMU isn't appropriate. I take the silence from the other team members to mean something similar. I suggest you revert the latest changes in libusbmuxd (e.g. with a +really version), let it migrate to testing and then do the soname bump dance. Paul
Attachment:
signature.asc
Description: OpenPGP digital signature