[SRU] prompt to change unmodified conf file /etc/cron.d/mailman during upgrade from oneiric to precise

Bug #911244 reported by Jean-Baptiste Lallement
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
mailman (Ubuntu)
Fix Released
Medium
Canonical Server
Precise
Fix Released
Medium
James Page

Bug Description

[IMPACT]
Users are prompted on upgrade from oneiric to precise to update a configuration file which has not been changed.

[TEST CASE]
Start with a fresh oneiric/11.10 install
sudo apt-get install mailman
sudo do-release-upgrade

results in:

Setting up mailman (1:2.1.14-3) ...

Configuration file `/etc/cron.d/mailman'
 ==> File on system created by you or by a script.
 ==> File also in package provided by package maintainer.
   What would you like to do about it ? Your options are:
    Y or I : install the package maintainer's version
    N or O : keep your currently-installed version
      D : show the differences between the versions
      Z : start a shell to examine the situation
 The default action is to keep your current version.
*** mailman (Y/I/N/O/D/Z) [default=N] ?

[REGRESSION POTENTIAL]
The fix is in the maintainer script and simple checks for the existence of the offending file and that its checksum matches a unmodified version - if this is the case it gets removed and replaced by a properly managed one. Minimal but upgrades from lucid should be checked as well.

>> Original bug report <<
Autoupgrade testing from oneiric to precise

The base image is a fresh and up to date oneiric installation. During upgrade the user is prompted to update the following unmodified configuration file:
/etc/cron.d/mailman

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: mailman 1:2.1.14-3
ProcVersionSignature: Ubuntu 3.2.0-7.13-generic 3.2.0-rc7
Uname: Linux 3.2.0-7-generic x86_64
ApportVersion: 1.90-0ubuntu1
Architecture: amd64
Date: Tue Jan 3 14:56:39 2012
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: mailman
UpgradeStatus: Upgraded to precise on 2012-01-03 (0 days ago)
mtime.conffile..etc.cron.d.mailman: 2012-01-03T14:14:43.969877

Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :
Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :
Changed in mailman (Ubuntu):
importance: Undecided → Medium
Changed in mailman (Ubuntu Precise):
assignee: nobody → Canonical Server Team (canonical-server)
tags: added: dist-upgrade oneiric2precise qa-daily-testing
tags: added: rls-mgr-p-tracking
Revision history for this message
Thijs Kinkhorst (kink) wrote :

Fixed in 1:2.1.14-4

Changed in mailman (Ubuntu):
status: New → Fix Released
Revision history for this message
James Page (james-page) wrote :
Changed in mailman (Ubuntu Precise):
assignee: Canonical Server Team (canonical-server) → James Page (james-page)
status: New → In Progress
milestone: none → ubuntu-12.04.1
James Page (james-page)
description: updated
summary: - prompt to change unmodified conf file /etc/cron.d/mailman during upgrade
- from oneiric to precise
+ [SRU] prompt to change unmodified conf file /etc/cron.d/mailman during
+ upgrade from oneiric to precise
description: updated
James Page (james-page)
description: updated
Revision history for this message
James Page (james-page) wrote :

Uploaded to -proposed for SRU team review.

Revision history for this message
Adam Conrad (adconrad) wrote : Please test proposed package

Hello Jean-Baptiste, or anyone else affected,

Accepted mailman into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/mailman/1:2.1.14-3ubuntu0.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please change the bug tag from verification-needed to verification-done. If it does not, change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in mailman (Ubuntu Precise):
status: In Progress → Fix Committed
tags: added: verification-needed
Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

SRU verification for Precise:
I have reproduced the problem with mailman 1:2.1.14-3 in precise and have verified that the version of mailman 1:2.1.14-3ubuntu0.1 in -proposed fixes the issue.

Marking as verification-done

tags: added: verification-done
removed: verification-needed
Revision history for this message
Scott Kitterman (kitterman) wrote : Update Released

The verification of this Stable Release Update has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package mailman - 1:2.1.14-3ubuntu0.1

---------------
mailman (1:2.1.14-3ubuntu0.1) precise-proposed; urgency=low

  * Ensure clean, unprompted upgrades of mailman from previous
    releases (LP: #911244):
    - d/preinst.in: Cherry picked update from most recent packaging to
      remove any unmanaged+unchanged versions of /etc/cron.d/mailman prior
      to installation of the new, managed version.
 -- James Page <email address hidden> Fri, 13 Jul 2012 08:42:33 +0100

Changed in mailman (Ubuntu Precise):
status: Fix Committed → Fix Released
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.