do-release-upgrade -d doesn't work immediately after running do-release-upgrade
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
update-manager (Ubuntu) |
Fix Released
|
High
|
Michael Vogt | ||
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/
-d/--devel-release to false-negative if you've run a normal
do-release-upgrade first?
Related branches
Changed in update-manager: | |
assignee: | nobody → mvo |
importance: | Undecided → High |
milestone: | none → ubuntu-8.04 |
status: | New → Confirmed |
This is fixed in hardy already, but needs a fix in dapper.