Failed to install due to permission error creating secring.gpg

[mkgg]

Error appears after login

ProblemType: Package
DistroRelease: Ubuntu 13.10
Package: spamassassin 3.3.2-6ubuntu2
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
Uname: Linux 3.11.0-12-generic x86_64
ApportVersion: 2.12.5-0ubuntu2
AptOrdering: spamassassin: Configure
Architecture: amd64
Date: Fri Oct 18 15:15:59 2013
DuplicateSignature: package:spamassassin:3.3.2-6ubuntu2:Unterprozess installiertes post-installation-Skript gab den Fehlerwert 2 zurück
ErrorMessage: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 2 zurück
InstallationDate: Installed on 2013-08-27 (52 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MarkForUpload: True
PackageArchitecture: all
SourcePackage: spamassassin
Title: package spamassassin 3.3.2-6ubuntu2 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 2 zurück
UpgradeStatus: Upgraded to saucy on 2013-10-18 (0 days ago)

spamassassin (3.3.2-6ubuntu2) is being set up ...
gpg: WARNING: Uncertain ownership of the home directory `/ var / lib / spamassassin / sa-update-keys'
gpg: failed to create temporary file `/var/lib/spamassassin/sa-update-keys/.#lk0xb238d0.artemis.22824 ': No authorization
gpg: Error creating "/var/lib/spamassassin/sa-update-keys/secring.gpg": General error
gpg: failed to create temporary file `/var/lib/spamassassin/sa-update-keys/.#lk0xb238d0.artemis.22824 ': No authorization
gpg: Error creating "/var/lib/spamassassin/sa-update-keys/pubring.gpg": General error
gpg: no writable keychain found: eof
gpg: Error reading `/usr/share/spamassassin/GPG.KEY ': General error
gpg: import from `/usr/share/spamassassin/GPG.KEY 'failed: General error
dpkg: Error editing spamassassin (--configure):
 Sub-process installed post-installation script returned error 2

[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. If this particular issue still persists, I'd request opening a fresh new bug for us to evaluate.