I uploaded a fix into dapper-proposed, following the regular SRU steps
now.
** Changed in: update-manager (Ubuntu Dapper)
Importance: Undecided => Medium
Assignee: (unassigned) => Michael Vogt (mvo)
Status: New => Fix Committed
** Description changed:
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:
| [EMAIL PROTECTED]:/etc # do-release-upgrade
| Checking for a new ubuntu release
| No new release found
| [EMAIL PROTECTED]:/etc # do-release-upgrade -d
| Checking for a new ubuntu release
| No new release found
| [EMAIL PROTECTED]:/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?
--
do-release-upgrade -d doesn't work immediately after running do-release-upgrade
https://bugs.launchpad.net/bugs/211978
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
