package mailman 1:2.1.14-3ubuntu0.1 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1

Bug #1446941 reported by kalidoss
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
mailman (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

I am using Ubuntu 12.04. When I attempted to update mailman,
it returned error and exited.

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: mailman 1:2.1.14-3ubuntu0.1
ProcVersionSignature: Ubuntu 3.2.0-80.116-generic-pae 3.2.68
Uname: Linux 3.2.0-80-generic-pae i686
ApportVersion: 2.0.1-0ubuntu17.8
Architecture: i386
Date: Tue Apr 21 08:50:15 2015
DuplicateSignature: package:mailman:1:2.1.14-3ubuntu0.1:subprocess new pre-installation script returned error exit status 1
ErrorMessage: subprocess new pre-installation script returned error exit status 1
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3)
MarkForUpload: True
SourcePackage: mailman
Title: package mailman 1:2.1.14-3ubuntu0.1 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
kalidoss (kalidoss-murugesan) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in mailman (Ubuntu):
status: New → Confirmed
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

The data here clearly shows the issue for the reason.
From your log:
 The directory /var/lib/mailman/qfiles contains files. It needs to be
 empty for the upgrade to work properly. You can try to handle them by:
  - Stop new messages from coming in (at the MTA level).
  - Start a mailman queue runner: /etc/init.d/mailman start
  - Let it run until all messages are handled.
    If they don't all get handled in a timely manner, look at the logs
    to try to understand why and solve the cause.
  - Stop it: /etc/init.d/mailman stop
  - Retry the upgrade.
  - Let messages come in again.
 You can also decide to simply remove the files, which will make Mailman
 forget about (and lose) the corresponding emails.
...
Package configuration
 Configuring mailman
 Old queue files present
 abort installation

Mailman needs the "active incoming queue" to be empty on upgrade.
That is a local configuration issue and not a bug in the package.
Gladly the fail even shows how to resolve it.

Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Thank you for your report.

This looks like a local configuration problem, rather than a bug in Ubuntu.

You can find pointers to get help for this sort of problem here: http://www.ubuntu.com/support/community

Since we use this bug tracker to track bugs in Ubuntu, rather than configuration problems, I'm marking this bug as Invalid. This helps us to focus on fixing bugs in Ubuntu.

If you believe that this is really a bug, then you may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to New.

Changed in mailman (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for mailman (Ubuntu) because there has been no activity for 60 days.]

Changed in mailman (Ubuntu):
status: Incomplete → Expired
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.