From email at patrickbraun.org  Mon Jun  8 13:38:36 2026
From: email at patrickbraun.org (Patrick Braun)
Date: Mon, 08 Jun 2026 14:38:36 +0200
Subject: [Debian-iot-maintainers] Bug#1138686: Bug#1138686: mosquitto:
 systemd service does not restart on upgrade / systemd triggers missing in
 postinst
In-Reply-To: <65ea7e1b995348718b311c1a21e4a68da5dda2d8.camel@heute-morgen.de>
References: <178039552312.3928.3789407458345852797.reportbug@f1494bfa4145>
 <65ea7e1b995348718b311c1a21e4a68da5dda2d8.camel@heute-morgen.de>
 <178039552312.3928.3789407458345852797.reportbug@f1494bfa4145>
Message-ID: <f7948bd0-ccbb-b101-5b51-13a14ce2bf3b@patrickbraun.org>


Hello Joachim,
you're right. After testing again the package normally contains all the triggers.?
I started from scratch and noticed that I can only reproduce that behavior when attempting to build the curently latest mosquitto 2.1.2-3 on Debian 12.
Maybe the debhelper Version? Debian 13 onwards builds correctly. I had to install zlib1g-dev in addition to apt build-dep'ing the directory though (Debian 12 and 13).
picohttpparser needed to be built too, as that one is not in deb12/13. Otherwise, everything seemed to work fine.
Both packages were built using 'gbp buildpackage -us -uc'.
Which override for dh_installsystemd did you set?
I copied the systemduser line and removed --no-enableoverride_dh_installsystemd:
	dh_installsystemd -pmosquitto mosquitto.service


I guess this is kind of a me-problem, since building mosquitto 2.1 on Debian 12 is not really intended and the original Debian 12 package v?2.0.11-1.2+deb12u2? and testing/unstable are correct.
So my apologies for the somewhat pointless report.
?
Sincerely,
Patrick
?
?
On ?Thursday, June 04, 2026 15:33 CEST, Joachim Zobel <jz-2017 at heute-morgen.de> wrote:

?
Am Dienstag, dem 02.06.2026 um 10:18 +0000 schrieb Patrick Braun:
> I suspect this is because the service file is not in the debian directory and dh_installsystemd does not place default triggers.

There are default triggers in the package:

$ grep dh_installsystemd /tmp/postinst-3?
# Automatically added by dh_installsystemduser/13.31
# Automatically added by dh_installsystemd/13.31
# Automatically added by dh_installsystemd/13.31

> 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.

Which override for dh_installsystemd did you set?

How do your postinst triggers differ from the existing ones?

Sincerely,
Joachim
?



?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/debian-iot-maintainers/attachments/20260608/170aa051/attachment.htm>