Package: libirecovery-1.0-dev
Version: 1.3.1-1+b2
Severity: important
Tags: patch
Dear Maintainer,
With libirecovery-1.0-dev installed and nothing else, pkg-config cannot
use its file, so nothing builds against the library:
$ pkg-config --cflags libirecovery-1.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 'libirecovery-1.0', not found
$ pkg-config --exists libirecovery-1.0; echo $?
1
The cause: /usr/lib/x86_64-linux-gnu/pkgconfig/libirecovery-1.0.pc has
Requires.private: libimobiledevice-glue-1.0 >= 1.2.0 libusb-1.0 >= 1.0.3
and the package depends on libusb-1.0-0-dev but not on
libimobiledevice-glue-dev:
Depends: libirecovery-1.0-5 (= 1.3.1-1+b2), libusb-1.0-0-dev
Policy 8.4 asks that installing the development package brings all the
development files needed to compile against the library.
Where it entered: after 1.0.0-5 (bookworm), whose .pc file requires only
libusb. 1.2.1-1 (trixie) has the glue library in its .pc file and the
same Depends as 1.3.1-1; I read those, I did not run trixie's package.
The fix is the one libimobiledevice-dev already has, the dependency.
Against 1.3.1-1:
--- a/debian/control
+++ b/debian/control
@@ -54,6 +54,7 @@
Depends:
libirecovery-1.0-5 (= ${binary:Version}),
libusb-1.0-0-dev,
+ libimobiledevice-glue-dev,
${misc:Depends},
Multi-Arch: same
Description: Development files for libirecovery
Tested in clean testing containers (amd64, pkgconf 2.5.1-4). With the
archive's libirecovery-1.0-dev 1.3.1-1+b2 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 libirecovery-1.0-dev=1.3.1-1 libirecovery-1.0-5=1.3.1-1
[...]
Setting up libirecovery-1.0-5:amd64 (1.3.1-1) ...
Setting up libimobiledevice-glue-dev (1.3.3-2) ...
Setting up libirecovery-1.0-dev:amd64 (1.3.1-1) ...
$ pkg-config --exists libirecovery-1.0; echo $?
0
$ pkg-config --cflags --libs libirecovery-1.0
-I/usr/include/libusb-1.0 -lirecovery-1.0
libusbmuxd-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 libirecovery-1.0-dev depends on:
ii libirecovery-1.0-5 1.3.1-1+b2
ii libusb-1.0-0-dev 2:1.0.30-1
libirecovery-1.0-dev recommends no packages.
libirecovery-1.0-dev suggests no packages.
-- no debconf information