Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#42682 - [libimobiledevice] 1.1.6-1 should depend on usbmuxd
Attached to Project:
Arch Linux
Opened by Jacobo Pantoja (jacobopantoja) - Tuesday, 04 November 2014, 21:51 GMT
Last edited by Jan de Groot (JGC) - Tuesday, 24 January 2017, 14:06 GMT
Opened by Jacobo Pantoja (jacobopantoja) - Tuesday, 04 November 2014, 21:51 GMT
Last edited by Jan de Groot (JGC) - Tuesday, 24 January 2017, 14:06 GMT
|
DetailsDescription:
Release 1.1.6-1 has dependency of libusbmuxd; the problem is that e.g. ifuse requires the actual usbmuxd binary to be installed. For systems in which the package was already installed, the result is that libusbmuxd is fetched, but usbmuxd is kept (although orphaned). For new installs, ifuse (and every idevice___ binary that I have tested) is not capable of communicating with the device. In summary, usbmuxd package should be a dependency of libimobiledevice Additional info: * package version(s) * config and/or log files etc. Steps to reproduce: Remove usbmuxd, libusbmuxd and libimobiledevice packages. Install libimobiledevice. Plug the device. Run ideviceinfo (or any other libimobiledevice binary). It will fail |
This task depends upon
Technically we should just create the loop and make it depend on usbmuxd, as long as we don't use versioned depends it's won't be a pain to update this in the future.