** Description changed:

+ [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
+ 
+ [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.  So 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
+  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

** Summary changed:

- 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 changed:

  [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.  So 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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/911244

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mailman/+bug/911244/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to