Ubuntu
bugzilla package

package bugzilla3 3.2.4.0-3ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 14

Bug #491617 reported by Nathan Geffen on 2009-12-02

This bug report is a duplicate of: Bug #419826: The following variables are new to /etc/bugzilla3/localconfig since you last ran checksetup.pl. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	bugzilla (Ubuntu)	Confirmed	Undecided	Unassigned

Bug Description

Binary package hint: bugzilla

This error occurred when I tried to install bugzilla using Synaptic Package Manager on Ubuntu 9.10. I'm using the latest repositories from the main server. Besides this comment, everything else in this bug report has been autogenerated.

ProblemType: Package
Architecture: i386
Date: Wed Dec 2 16:14:54 2009
DistroRelease: Ubuntu 9.10
ErrorMessage: subprocess installed post-installation script returned error exit status 14
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
Package: bugzilla3 3.2.4.0-3ubuntu1
PackageArchitecture: all
ProcVersionSignature: Ubuntu 2.6.31-15.50-generic
SourcePackage: bugzilla
Title: package bugzilla3 3.2.4.0-3ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 14
Uname: Linux 2.6.31-15-generic i686

Tags:

Revision history for this message

Nathan Geffen (nathangeffen) wrote on 2009-12-02:

AptOrdering.txt Edit (2.7 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (2.7 KiB, text/plain; charset="utf-8")
Dmesg.txt Edit (70.8 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (43.7 KiB, text/plain; charset="utf-8")

Revision history for this message

Jean-Baptiste Lallement (jibel) wrote on 2009-12-02:

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 419826, 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.