Ubuntu
amavisd-new package

package amavisd-new-postfix 1:2.6.5-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Bug #808053 reported by Carlo on 2011-07-09

This bug report is a duplicate of: Bug #1587695: package amavisd-new 1:2.10.1-2ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	amavisd-new (Ubuntu)	New	Undecided	Unassigned

Bug Description

Was performing a routine update when I got the error message.

ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: amavisd-new-postfix 1:2.6.5-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.38-10.44-generic 2.6.38.7
Uname: Linux 2.6.38-10-generic i686
Architecture: i386
Date: Sat Jul 9 11:59:55 2011
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
PackageArchitecture: all
SourcePackage: amavisd-new
Title: package amavisd-new-postfix 1:2.6.5-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

Tags:

Revision history for this message

Carlo (carlo-1973) wrote on 2011-07-09:

AptOrdering.txt Edit (2.8 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (3.4 KiB, text/plain; charset="utf-8")
Df.txt Edit (381 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (52.4 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.gz Edit (2.1 KiB, application/x-gzip)

Revision history for this message

Andreas Moog (ampelbein) wrote on 2011-07-09:

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 801338, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.