Source: moosefs Version: 3.0.115-1 Severity: normal Hi,
I noticed that moosefs hasn't built successfully on Ubuntu [1], and I traced this down to the fact that we're pulling in systemd transitively as a build dependency, which causes moosefs to build the systemd module and then create .service files that don't end up being installed: dh_missing dh_missing: warning: lib/systemd/system/moosefs-cgiserv.service exists in debian/tmp but is not installed to anywhere dh_missing: warning: lib/systemd/system/moosefs-chunkserver.service exists in debian/tmp but is not installed to anywhere dh_missing: warning: lib/systemd/system/moosefs-chunkserver@.service exists in debian/tmp but is not installed to anywhere dh_missing: warning: lib/systemd/system/moosefs-master.service exists in debian/tmp but is not installed to anywhere dh_missing: warning: lib/systemd/system/moosefs-master@.service exists in debian/tmp but is not installed to anywhere dh_missing: warning: lib/systemd/system/moosefs-metalogger.service exists in debian/tmp but is not installed to anywhere dh_missing: warning: lib/systemd/system/moosefs-metalogger@.service exists in debian/tmp but is not installed to anywhere dh_missing: error: missing files, aborting Specifically, the configure script runs pkg-config to check for the existence of systemd, and this only returns true in Ubuntu because we're pulling in the systemd package transitively (and Debian is not). We can patch out that line of the configure script in Ubuntu, but my gut is that this should somehow be addressed in Debian. Should Debian explicitly build-depend on systemd and then leverage that module in the source package instead of custom-creating the .service files in the debian/ directory? Or maybe that part of the script should be patched out in Debian so that we don't need to carry a delta? Please let me know your thoughts. Thanks, Logan [1] https://launchpad.net/ubuntu/+source/moosefs/3.0.115-1
