Package: libusbmuxd-dev
Version: 2.1.1-1+b1
Severity: important
Tags: patch
Dear Maintainer,
With libusbmuxd-dev installed and nothing else, pkg-config cannot use
its file, so nothing builds against the library:
$ pkg-config --cflags libusbmuxd-2.0
Package libimobiledevice-glue-1.0 was not found in the pkg-config search path.
Perhaps you should add the directory containing `libimobiledevice-glue-1.0.pc'
to the PKG_CONFIG_PATH environment variable
Package 'libimobiledevice-glue-1.0', required by 'libusbmuxd-2.0', not found
$ pkg-config --exists libusbmuxd-2.0; echo $?
1
The cause: /usr/lib/x86_64-linux-gnu/pkgconfig/libusbmuxd-2.0.pc has
Requires.private: libplist-2.0 >= 2.2.0 libimobiledevice-glue-1.0 >= 1.2.0
and the package depends on libplist-dev but not on
libimobiledevice-glue-dev:
Depends: libplist-dev (>= 2.3.0), libusbmuxd-2.0-7 (= 2.1.1-1+b1)
Policy 8.4 asks that installing the development package brings all the
development files needed to compile against the library.
Where it entered: 2.1.0-1, when upstream added the glue library to the
.pc file. 2.0.2-3 (bookworm) is right. 2.1.0-1 (trixie) has the same
control file and the same .pc file as 2.1.1-1; I read those, I did not
run trixie's package.
The two packages in the archive that build against libusbmuxd-dev,
libimobiledevice and idevicerestore, have libimobiledevice-glue-dev in
their own Build-Depends, so their builds do not meet this. I met it
building a program from outside the archive.
The fix is the one libimobiledevice-dev already has, the dependency.
Against 2.1.1-1:
--- a/debian/control
+++ b/debian/control
@@ -25,6 +25,7 @@
Multi-Arch: same
Depends: libplist-dev (>= 2.3.0),
libusbmuxd-2.0-7 (= ${binary:Version}),
+ libimobiledevice-glue-dev,
${misc:Depends}
Description: ${source:Synopsis} (devel)
${source:Extended-Description}
Tested in clean testing containers (amd64, pkgconf 2.5.1-4). With the
archive's libusbmuxd-dev 2.1.1-1+b1 alone, the two commands above fail
as shown. With the packages rebuilt from the patched source as the only
extra repository, in a fresh container:
$ apt-get install libusbmuxd-dev=2.1.1-1 libusbmuxd-2.0-7=2.1.1-1
[...]
Setting up libimobiledevice-glue-dev (1.3.3-2) ...
Setting up libusbmuxd-2.0-7:amd64 (2.1.1-1) ...
Setting up libusbmuxd-dev:amd64 (2.1.1-1) ...
$ pkg-config --exists libusbmuxd-2.0; echo $?
0
$ pkg-config --cflags --libs libusbmuxd-2.0
-lusbmuxd-2.0
libirecovery-1.0-dev has the same fault. I am reporting it separately,
with its own patch.
I found this with AI assistance and checked it myself.
Daniel Ramos
-- System Information:
Debian Release: forky/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 7.3.4-stereo3d18 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to C.UTF-8),
LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect
Versions of packages libusbmuxd-dev depends on:
ii libplist-dev 2.7.0+git20250820-1+b2
ii libusbmuxd-2.0-7 2.1.1-1+b1
libusbmuxd-dev recommends no packages.
libusbmuxd-dev suggests no packages.
-- no debconf information