<html><p>Hello Joachim,</p><p>you're right. After testing again the package normally contains all the triggers. </p><p>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.</p><p>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).</p><p>picohttpparser needed to be built too, as that one is not in deb12/13. Otherwise, everything seemed to work fine.</p><p>Both packages were built using 'gbp buildpackage -us -uc'.</p><blockquote><p>Which override for dh_installsystemd did you set?</p></blockquote><p>I copied the systemduser line and removed --no-enable</p><pre class="code highlight" lang="plaintext"><span class="">override_dh_installsystemd:</span>
<span class=""> dh_installsystemd -pmosquitto mosquitto.service</span>
</pre><p>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.</p><p>So my apologies for the somewhat pointless report.</p><p> </p><p>Sincerely,<br>Patrick</p><p> </p><p> </p><blockquote><p>On Thursday, June 04, 2026 15:33 CEST, Joachim Zobel <jz-2017@heute-morgen.de> wrote:<br><br> </p></blockquote><blockquote type="cite" cite="65ea7e1b995348718b311c1a21e4a68da5dda2d8.camel@heute-morgen.de"><p>Am Dienstag, dem 02.06.2026 um 10:18 +0000 schrieb Patrick Braun:<br>> I suspect this is because the service file is not in the debian directory and dh_installsystemd does not place default triggers.<br><br>There are default triggers in the package:<br><br>$ grep dh_installsystemd /tmp/postinst-3 <br># Automatically added by dh_installsystemduser/13.31<br># Automatically added by dh_installsystemd/13.31<br># Automatically added by dh_installsystemd/13.31<br><br>> After tinkering a bit by copying the service to debian/ and setting an override for dh_installsystemd, the systemd postinst triggers<br>> get inserted as expected. So I'm guessing that's the reason.<br><br>Which override for dh_installsystemd did you set?<br><br>How do your postinst triggers differ from the existing ones?<br><br>Sincerely,<br>Joachim<br> </p></blockquote><p><br><br><br> </p></html>