release no longer supported message missing

Bug #364583 reported by Michael Vogt
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)
Fix Released
Medium
Michael Vogt
Hardy
Fix Released
Medium
Unassigned
Jaunty
Fix Released
Medium
Michael Vogt

Bug Description

Binary package hint: update-manager

The release no longer supported message is missing when a release is set to "Supported: 0"

TEST CASE (hardy):
1. use update-manager from hardy
2. edit /etc/lsb-release and change DISTRIB_CODENAME from hardy to dapper (as this is no longer supported)
3. run update-manager verify that no "no longer supported message" is displayed
4. install update-manager from hardy-proposed, repeat 3 and verify that it works now

TEST CASE (jaunty):
1. use update-manager from stock jaunty
2. edit /etc/lsb-release and change DISTRIB_CODENAME from jaunty to gutsy
-DISTRIB_CODENAME=jaunty
+DISTRIB_CODENAME=gutsy
3. run update-manager and verify that there is no dialog about the no longer supported distro

4. install update-manager from jaunty-proposed
5. run "update-manager" and verify there is a warning dialog about the distro no longer supported

TEST CASE (intrepid, hardy).
1. same as above for jaunty, put DISTRIB_CODENAME to gutsy and verify the missing warning and the fix

Michael Vogt (mvo)
Changed in update-manager (Ubuntu):
assignee: nobody → Michael Vogt (mvo)
importance: Undecided → Medium
status: New → In Progress
Michael Vogt (mvo)
description: updated
Revision history for this message
Martin Pitt (pitti) wrote :

Accepted update-manager into jaunty-proposed-proposed; please test and give feedback here. Please see https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

tags: added: verification-needed
Revision history for this message
Steve Beattie (sbeattie) wrote :

I can confirm that the version of update-manager in jaunty, 1:0.111.7, does not warn about releases that are no longer supported, and have verified that the version in jaunty-proposed, 1:0.111.8, gives a warning about unsupported versions. It does continue to offer release upgrades and install available updates.

I do note that update-manager-text gives no warning (nor does it offer a release upgrade, I'm assuming that capability is not yet in place). Also, does adept_updater need a similar fix? I tried adept-updater from 8.04 updates, 2.1.3ubuntu25.1, and it gave no warning about an unsupported release; adept from jaunty didn't appear to either, but I wasn't running a full kubuntu desktop there.

Martin Pitt (pitti)
tags: added: verification-done
removed: verification-needed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package update-manager - 1:0.111.8

---------------
update-manager (1:0.111.8) jaunty-proposed; urgency=low

  * DistUpgrade/DistUpgrade.cfg:
    - add "grub" to the list of packages to keep installed
      (LP: #363465)
    - ensure brasero is upgraded (thanks to Chris Jones for
      the report) (LP: #364136)
    - ensure guidance-power-manager is removed on upgrade
      (LP: #364620)
  * DistUpgrade/DistUpgradeCache.py:
    - support DistUpgradeCache.markUpgrade()
  * DistUpgrade/mirrors.cfg:
    - add "mirror.files.bigpond.com" (thanks to wgrant)
  * debian/control:
    - build-depend on latest nvidia-common (LP: #363500) to ensure
      the nvidia-common if is included in the internal copy of
      u-m
  * DistUpgrade/DistUpgradeQuirks.py:
    - when the upgrade starts, remove old hal.postinst to prevent
      the trigger from running that causes network-manager to shutdown
      all connections (LP: #327053)
  * UpdateManager/Core/MetaRelease.py, UpdateManager/MetaReleaseGObject.py:
    - fix "no longer supported" message (LP: #364583)

 -- Michael Vogt <email address hidden> Mon, 20 Apr 2009 13:53:01 +0200

Changed in update-manager (Ubuntu Jaunty):
status: In Progress → Fix Released
Revision history for this message
Michael Vogt (mvo) wrote :

This is part of u-m trunk so this task can be closed.

Martin Pitt (pitti)
Changed in update-manager (Ubuntu):
status: In Progress → Fix Released
Michael Vogt (mvo)
Changed in update-manager (Ubuntu Hardy):
status: New → In Progress
description: updated
Revision history for this message
Martin Pitt (pitti) wrote : Please test proposed package

Hello Michael, or anyone else affected,

Accepted update-manager into hardy-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

Changed in update-manager (Ubuntu Hardy):
status: In Progress → Fix Committed
tags: removed: verification-done
tags: added: verification-needed
Changed in update-manager (Ubuntu Hardy):
importance: Undecided → Medium
Revision history for this message
Marc Deslauriers (mdeslaur) wrote :

I can confirm the package in -proposed works.

Before updating, Hardy's update-manager wanted me to upgrade to Intrepid. After the update, it's telling me to upgrade to Lucid.

tags: added: verification-done
removed: verification-needed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package update-manager - 1:0.87.33

---------------
update-manager (1:0.87.33) hardy-security; urgency=low

  * REGRESSION FIX:
    - DistUpgrade/DistUpgradeViewKDE.py: fix regression caused by improper
      return value handling. (LP: #933225)
 -- Marc Deslauriers <email address hidden> Thu, 16 Feb 2012 08:30:21 -0500

Changed in update-manager (Ubuntu Hardy):
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.