Ubuntu
update-manager package

do-release-upgrade -d doesn't work immediately after running do-release-upgrade

Bug #211978 reported by James Troup
28
This bug affects 4 people
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)
Fix Released
High
Michael Vogt
Ubuntu ubuntu-8.04
Dapper
Fix Released
Medium
Michael Vogt

Bug Description

Binary package hint: update-manager

Steps to reproduce:
1. install update-manager-core from dapper-updates
2. run do-release-upgrade, verify that "No new release found" is printed
3. run do-release-upgrade -d, verify that "No new release found" is printed - that is a lie
4. install update-managerc-ore from dapper-proposed
5. run do-release-upgrade -d, verify that it performs some actions and gives you the opportunity to ugprade

Original bug description:
| root@yellow:/etc # do-release-upgrade
| Checking for a new ubuntu release
| No new release found
| root@yellow:/etc # do-release-upgrade -d
| Checking for a new ubuntu release
| No new release found
| root@yellow:/etc #

Given the machine is running dapper, that's clearly a lie...

It seems MetaRelease.py is doing some rather dubious things with the
mtime of /var/lib/update-manager/meta-release that cause
-d/--devel-release to false-negative if you've run a normal
do-release-upgrade first?

See original description
Michael Vogt (mvo)
Changed in update-manager:
assignee: nobody → mvo
importance: Undecided → High
milestone: none → ubuntu-8.04
status: New → Confirmed
Revision history for this message
Michael Vogt (mvo) wrote :
Revision history for this message
Michael Vogt (mvo) wrote :

This is fixed in hardy already, but needs a fix in dapper.

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

I uploaded a fix into dapper-proposed, following the regular SRU steps now.

Changed in update-manager:
assignee: nobody → mvo
importance: Undecided → Medium
status: New → Fix Committed
description: updated
Revision history for this message
Michael Vogt (mvo) wrote :

I mark this "in progress" again because while it is fixed in hardy the upload to dapper-proposed is not reviewed/processed yet and we should do that before -final.

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

This bug can also lead to bug like that people see a possible upgrade to edgy instead of dapper.

Revision history for this message
Colin Watson (cjwatson) wrote :

The binaries were stuck in the dapper-proposed NEW queue - I've waved them through now.

Revision history for this message
Brian Murray (brian-murray) wrote :

I have recreated this bug using update-manager-core from dapper-updates with package version 0.56~dapper4. I then verified the fix using update-manager-core version 0.56~dapper5.

Incidentally, I was only able to recreate the original bug when executing 'do-release-upgrade' and 'do-release-upgrade -d' as root. When I executed them via 'sudo' the bug was not triggered.

Revision history for this message
Martin Pitt (pitti) wrote :

Copied to dapper-updates. Michael, is this still an issue with Hardy? If not, please close the Hardy task.

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

Closing the hardy task, this is fixed here too, I just kept it open to have it on the radar in the 8.04 buglist

Changed in update-manager:
status: In Progress → Fix Released
Revision history for this message
Stephen Birch (sgbirch) wrote :

I attempted to use do-release-upgrade to install the 9.04 beta onto a hardy machine and experienced the same problem, it did not find the new release:

root@tab:/etc/update-manager# do-release-upgrade
Checking for a new ubuntu release
No new release found

root@tab:/etc/apt# do-release-upgrade -d
Checking for a new ubuntu release
No new release found

I removed update-manager-core and reinstalled but that did not fix the problem.

Attempte to upgrade from hardy to 9.04 using "update-manager -d" also failed.

Revision history for this message
Aethralis (aethralis) wrote :

I'm also affected. I even installed update-manager-core from intrepid proposed, but even that did not do the trick.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.