<html><head></head><body>Hello,<br><br>I'm not sure I understand the problem.<br><br>Libyder relies on libsystemd to write logs in journald, but it's one of the log output available, like syslog, a file, a callback or the console. But you can use libyder without systemd if you don't use it as log output.<br><br>Also, in Debian packages, libsystemd0 doesn't have systemd as a dependency. This may be for a reason.<br><br>I will try and see what happens if you use libyder with libsystemd and without systemd. But besides the probable fact that a journald log will be unavailable if set, I don't think there will be bad consequences.<br><br><div class="gmail_quote">Le 3 avril 2019 06 h 02 min 22 s HAE, Harald Welte <laforge@gnumonks.org> a écrit :<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail">Package: libyder-dev<br>Version: 1.4.4-4<br>Severity: normal<br><br>I'm experiencing problems building yder-based applications:,<br>libyder.pc (after applying debian/cmake.patch) has a Requires.private to<br>the pacakge 'systemd'. However, 'systemd' is not listed in the<br>'Depends' line of debian/control.<br><br>This leads to the absurd situation that I can build + install<br>libyder-dev, but other yder-using applications will not get past their<br>cmaake/autoconf step as 'systemd' is not neccessarily installed.<br><br>So at the very least, 'systemd' should be listed in 'Depends'.<br><br>I'm somewhat doubtful about this entire method of using pkg-config<br>'Requires.private'. It may make sense in the absence of a package<br>manager. But as we're talking about a Debian package here: Dependencies<br>should be tracked at package installation time using dpkg/apt, and not<br>some pkg-config private mechanism, IMHO.<br><br>Also, I'm not entirely sure why there's a dependency on 'systemd', and<br>not 'libsystemd' as in the upstream source. The Debian changelog<br>unfortunately doesn't explain why that cmake.patch is used.<br><br>Thanks in advance.<br><br>-- System Information:<br>Debian Release: buster/sid<br> APT prefers unstable<br> APT policy: (500, 'unstable')<br>Architecture: amd64 (x86_64)<br>Foreign Architectures: i386<br><br>Kernel: Linux 4.19.0-4-amd64 (SMP w/4 CPU cores)<br>Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE<br>Locale: LANG=en_US.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8)<br>Shell: /bin/sh linked to /bin/bash<br>Init: systemd (via /run/systemd/system)<br>LSM: AppArmor: enabled<br><br>Versions of packages libyder-dev depends on:<br>ii libjansson-dev 2.12-1<br>ii liborcania-dev 1.2.9-5<br>ii libsystemd-dev 241-2<br>ii libyder2.0 1.4.4-4<br><br>libyder-dev recommends no packages.<br><br>libyder-dev suggests no packages.<br><br>-- no debconf information<hr>Debian-iot-maintainers mailing list<br>Debian-iot-maintainers@alioth-lists.debian.net<br><a href="https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-iot-maintainers">https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-iot-maintainers</a><br></pre></blockquote></div></body></html>