[ Adding debian-b...@lists.debian.org back. ] Ritesh Raj Sarraf <r...@debian.org> (2015-09-28): > Adding systemd maintainers > > > Hello Cyril, > > THank you for the bug report. > > > On Fri, 2015-09-25 at 11:59 +0200, Cyril Brulebois wrote: > > Package: multipath-udeb > > Version: 0.5.0+git0.770e6d0d-3 > > Severity: grave > > Justification: renders package unusable > > > > > > [ Please keep debian-b...@lists.debian.org in the loop. ] > > > > Hi, > > > > Your package in unstable gained a dependency which cannot be > > satisfied: > > libsystemd0 has no udeb. It's therefore no longer installable, along > > with partman-multipath which depends on it. > > This was intentionally done because upstream added systemd dependency > some time ago. For Jessie, I had disabled systemd support, but now, it > makes sense to have it, and align with upstream and other > distributions. > > So, I think the real question is about why libsystemd0 does not have a > udeb ? > > systemd maintainers should provide that input.
Some input from someone who doesn't know a thing about systemd or multipath: libmultipath.so.0 has a NEEDED entry on libsystemd.so.0, which seems to only define symbols named sd_* (which seems fair). The only use I see in libmultipath.so.0 is sd_listen_fds. Its manpage says: sd_listen_fds() shall be called by a daemon to check for file descriptors passed by the init system as part of the socket-based activation logic. There's no systemd in d-i, so there's no socket-based activation logic, and you can't rely on that in your multipath udeb. Mraw, KiBi.
signature.asc
Description: Digital signature