Package: mosquitto
Version: 2.0.21-1
Severity: normal

Dear Maintainer,

after a package upgrade, the mosquitto systemd service is not restarted 
automatically.
Looking at the debian/rules this does not seem like specifically intented 
behavior.

I suspect this is because the service file is not in the debian directory and 
dh_installsystemd does not place default triggers.
After tinkering a bit by copying the service to debian/ and setting an override 
for dh_installsystemd, the systemd postinst triggers
get inserted as expected. So I'm guessing that's the reason.

Just fyi this report is sent from a container so the kernel version does not 
match Deb13.
I noticed this problem when I upgraded from mosquitto 2.0 to 2.1 while testing 
configs.

Thank you for your time and effort

-- System Information:
Debian Release: 13.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 7.0.10 (SMP w/24 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect

Versions of packages mosquitto depends on:
ii  adduser              3.152
ii  init-system-helpers  1.69~deb13u1
ii  libc6                2.41-12+deb13u3
ii  libcjson1            1.7.18-3.1+deb13u1
ii  libdlt2              2.18.10-10+b1
ii  libmosquitto1        2.0.21-1
ii  libssl3t64           3.5.6-1~deb13u1
ii  libsystemd0          257.13-1~deb13u1
ii  libwebsockets19t64   4.3.5-1+deb13u1
ii  libwrap0             7.6.q-36
ii  sysvinit-utils       3.14-4

mosquitto recommends no packages.

Versions of packages mosquitto suggests:
pn  apparmor  <none>

-- no debconf information

Reply via email to