On Sun, Jun 22, 2025 at 10:01:52AM -0400, Noah Meyerhans wrote: > I also don't see it on upgrade from -3 in trixie, but I do see a couple > of unexpected things: > > Setting up sa-compile (4.0.1-4) ... > Running sa-compile (may take a long time) > Warning: The unit file, source configuration file or drop-ins of > spamd.service changed on disk. Run 'systemctl daemon-reload' > to reload units. > Setting up spamd (4.0.1-4) ... > Processing triggers for man-db (2.13.1-1) ...
Strangely, this does not seem to happen 100% of the time. Here is a transcript of an upgrade from -3 to -4 that did not encounter this issue. root@satest-trixie:~# apt install spamd spamassassin Upgrading: spamassassin spamc spamd Summary: Upgrading: 3, Installing: 0, Removing: 0, Not Upgrading: 20 Download size: 1383 kB Space needed: 9216 B / 18.9 GB available Continue? [Y/n] Get:1 file:/etc/apt/mirrors/debian.list Mirrorlist [43 B] Get:2 http://apt.internal.morgul.net:3142/debian sid/main amd64 spamd all 4.0.1-4 [77.3 kB] Get:3 http://apt.internal.morgul.net:3142/debian sid/main amd64 spamassassin all 4.0.1-4 [1239 kB] Get:4 http://apt.internal.morgul.net:3142/debian sid/main amd64 spamc amd64 4.0.1-4 [66.2 kB] Fetched 1383 kB in 0s (26.0 MB/s) Reading changelogs... Done (Reading database ... 31072 files and directories currently installed.) Preparing to unpack .../archives/spamd_4.0.1-4_all.deb ... Unpacking spamd (4.0.1-4) over (4.0.1-3) ... Preparing to unpack .../spamassassin_4.0.1-4_all.deb ... Unpacking spamassassin (4.0.1-4) over (4.0.1-3) ... Preparing to unpack .../spamc_4.0.1-4_amd64.deb ... Unpacking spamc (4.0.1-4) over (4.0.1-3) ... Setting up spamc (4.0.1-4) ... Setting up spamassassin (4.0.1-4) ... Installing new version of config file /etc/spamassassin/init.pre ... Installing new version of config file /etc/spamassassin/v310.pre ... Installing new version of config file /etc/spamassassin/v312.pre ... Installing new version of config file /etc/spamassassin/v320.pre ... Installing new version of config file /etc/spamassassin/v330.pre ... Installing new version of config file /etc/spamassassin/v340.pre ... Installing new version of config file /etc/spamassassin/v341.pre ... Installing new version of config file /etc/spamassassin/v342.pre ... Installing new version of config file /etc/spamassassin/v343.pre ... Installing new version of config file /etc/spamassassin/v400.pre ... Setting up spamd (4.0.1-4) ... Processing triggers for man-db (2.13.1-1) ... And there's no indication of the "spamd.service: State 'stop-sigterm' timed out. Killing." problem.
