Bug#941793: nmu: libimobiledevice_1.2.1~git20181030.92c5462-1
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
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,
- --
Yves-Alexis
-----BEGIN PGP SIGNATURE-----
iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAl2Zn2cACgkQ3rYcyPpX
RFv1MQf9HCrq7PcTGARBTZmkisA5BJLBRGyN8xNWIWLEXXBJTIV7eHCaO6EvnagN
tys5gQXS8TrulnorZ0rE1bkFHQ/ZIirAEu84XI6HGmo6G4qXN7YQhmqzTRRLkUxk
lRnUI/aNeIPqk3WQb/zMVvbDOZDs3KjompBDVcECQhHa8+EDZNlhOmTg9dbOOK5K
DY3Aaf9ZSvN5QVYr+Oay7xeTmDpttceedLIbo5t9aPeZlJ/SCax0st4Kua6B3Ug9
RZVnhod6TZ26uDccyWpL1utuBpFIg7RXJ4M5V9haDb6B5+QyhDBnUpu/MgfCvw5n
8BnmwMjLPL9xuZAvYumR4747Tpi1NQ==
=EDhd
-----END PGP SIGNATURE-----
Reply to: