Package: libyder-dev Version: 1.4.4-4 Severity: normal I'm experiencing problems building yder-based applications:, libyder.pc (after applying debian/cmake.patch) has a Requires.private to the pacakge 'systemd'. However, 'systemd' is not listed in the 'Depends' line of debian/control.
This leads to the absurd situation that I can build + install libyder-dev, but other yder-using applications will not get past their cmaake/autoconf step as 'systemd' is not neccessarily installed. So at the very least, 'systemd' should be listed in 'Depends'. I'm somewhat doubtful about this entire method of using pkg-config 'Requires.private'. It may make sense in the absence of a package manager. But as we're talking about a Debian package here: Dependencies should be tracked at package installation time using dpkg/apt, and not some pkg-config private mechanism, IMHO. Also, I'm not entirely sure why there's a dependency on 'systemd', and not 'libsystemd' as in the upstream source. The Debian changelog unfortunately doesn't explain why that cmake.patch is used. Thanks in advance. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-4-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libyder-dev depends on: ii libjansson-dev 2.12-1 ii liborcania-dev 1.2.9-5 ii libsystemd-dev 241-2 ii libyder2.0 1.4.4-4 libyder-dev recommends no packages. libyder-dev suggests no packages. -- no debconf information
