dpkg setup failed during installation/upgrade due to missing gpg for verification

Bug #1426562 reported by emare
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
spamassassin (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

help :-(

ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: spamassassin 3.4.0-3ubuntu2.1
ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3
Uname: Linux 3.16.0-30-generic x86_64
ApportVersion: 2.14.7-0ubuntu8.1
Architecture: amd64
Date: Fri Feb 27 22:45:26 2015
DuplicateSignature: package:spamassassin:3.4.0-3ubuntu2.1:subprocess installed post-installation script returned error exit status 2
ErrorMessage: subprocess installed post-installation script returned error exit status 2
InstallationDate: Installed on 2014-01-11 (412 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
PackageArchitecture: all
SourcePackage: spamassassin
Title: package spamassassin 3.4.0-3ubuntu2.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
UpgradeStatus: No upgrade log present (probably fresh install)

Setting up spamassassin (3.4.0-3ubuntu2.1) ...
error: gpg required but not found! It is not recommended, but you can use "sa-update" with the --no-gpg to skip the verification.
dpkg: error processing package spamassassin (--configure):
 subprocess installed post-installation script returned error exit status 2
dpkg: dependency problems prevent configuration of sa-compile:
 sa-compile depends on spamassassin (>= 3.3.2-8); however:
  Package spamassassin is not configured yet.

Revision history for this message
emare (ema0001) wrote :
tags: removed: need-duplicate-check
Bryce Harrington (bryce)
description: updated
summary: - package spamassassin 3.4.0-3ubuntu2.1 failed to install/upgrade:
- subprocess installed post-installation script returned error exit status
- 2
+ dpkg setup failed during installation/upgrade due to missing gpg for
+ verification
Revision history for this message
Bryce Harrington (bryce) wrote :

From the description it's not clear why gpg was not available, 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.

Changed in spamassassin (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.