spamassassin 3.3.2-6ubuntu1 failed to install due to incorrect group «debian-spamd:debian-spamd»

[francoisb]

Fresh install on a new computer. Spams are not sorted out.

ProblemType: Package
DistroRelease: Ubuntu 13.04
Package: spamassassin 3.3.2-6ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-23.34-generic 3.8.11
Uname: Linux 3.8.0-23-generic i686
NonfreeKernelModules: fglrx
ApportVersion: 2.9.2-0ubuntu8.1
Architecture: i386
Date: Sat Aug 3 19:42:31 2013
DuplicateSignature: package:spamassassin:3.3.2-6ubuntu1:subprocess installed post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2013-05-25 (71 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
MarkForUpload: True
PackageArchitecture: all
SourcePackage: spamassassin
Title: package spamassassin 3.3.2-6ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Noel Maersk (veox)]

The `postinst` script contains a directive to start the `systemd` service (via `invoke-rc.d`); that tries to run `sa-compile`.

On one (low-powered) system where I'm experiencing this, running `sa-compile` takes about 3 minutes.

This hits the (default) timeout of 1min 30s; the service fails; `postinst` fails.

Increasing the timeout in any manner (e.g. in `/etc/systemd/system.conf`) helps work around the problem.

[Karl Stenerud (kstenerud)]

Thanks, Noel,

Since this is outside of the scope of the original bug, could you please open a new bug for this issue so that it doesn't get lost?

[Noel Maersk (veox)]

Ah, perhaps it is indeed out of scope: I see now `DpkgTerminalLog.txt` of the original reporter contains

    Setting up spamassassin (3.3.2-6ubuntu1) ...
    chown: groupe incorrect: «debian-spamd:debian-spamd»

I don't have time to file a proper report now.

[Bryce Harrington (bryce)]

From the description it's not clear what the problem was originally, but spamassassin in general has been installing fine in the intervening years, so presumably this issue is no longer relevant.