[debhelper-devel] Bug#848192: /usr/bin/dh_systemd_start: dh_systemd_start needs to start .socket before .service

Matthias Urlichs matthias at urlichs.de
Thu Dec 15 00:38:18 UTC 2016


Package: debhelper
Version: 10.2.2
Severity: normal
File: /usr/bin/dh_systemd_start

When I have both a service and a socket unit file, dh_systemd_start runs
the service first.

This is bad because the socket will refuse to run when the service has been
started, while the service's configuration probably depends on the socket.

        deb-systemd-invoke $_dh_action knxd.service knxd.socket >/dev/null || true

Please re-order to act on the socket first.

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (700, 'testing'), (650, 'unstable'), (600, 'stable'), (550, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

Kernel: Linux 4.9.0-rc5-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages debhelper depends on:
ii  autotools-dev            20161112.1
ii  binutils                 2.27.51.20161127-1
ii  dh-autoreconf            12
ii  dh-strip-nondeterminism  0.028-1
ii  dpkg                     1.18.15
ii  dpkg-dev                 1.18.15
ii  file                     1:5.29-1
ii  libdpkg-perl             1.18.15
ii  man-db                   2.7.5-2
ii  perl                     5.24.1~rc3-3
ii  po-debconf               1.0.20

debhelper recommends no packages.

Versions of packages debhelper suggests:
ii  dh-make  2.201608

-- no debconf information




More information about the debhelper-devel mailing list