Bug#926317: libyder.pc Requires.private systemd, but systemd not in debian/control

2019-04-03 Thread Harald Welte
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

Bug#926317: [Debian-iot-maintainers] Bug#926317: libyder.pc Requires.private systemd, but systemd not in debian/control

2019-04-04 Thread Nicolas Mora
Hello, I'm not sure I understand the problem. 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. Also, in Debian packages, l

Bug#926317: [Debian-iot-maintainers] Bug#926317: libyder.pc Requires.private systemd, but systemd not in debian/control

2019-04-04 Thread Harald Welte
Hi Nicolas, thanks for your response. On Thu, Apr 04, 2019 at 09:10:10AM -0400, Nicolas Mora wrote: > 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

Bug#926317: [Debian-iot-maintainers] Bug#926317: Bug#926317: libyder.pc Requires.private systemd, but systemd not in debian/control

2019-04-04 Thread Nicolas Mora
Hello Harald, IIRC, I put this patch in the first place because of compilation errors at the time, the errors were fixed only after patching the cmake script like this. But your bug made me check again and it seems that it's no longer necessary. So I'll remove the patch and push a new package soo