This information should certainly go in the official upgrade
instructions here: https://help.ubuntu.com/10.04/serverguide/C
/installing-upgrading.html. It'd be nice to have some mechanism to be
notified of when the .1 release is out.
--
'do-release-upgrade' requires the '-d' flag to upgrade from
The doc is updated by .1 release to reflect that (if you look at
https://help.ubuntu.com/community/HardyUpgrades, you can see that it
doesn't mention --proposed anymore). In the mean time, it's true it
/could/ mention that --proposed is only temporary, until .1 is out.
--
'do-release-upgrade'
This is not a bug. LTS - LTS upgrades are enabled for the general
public after the LTS.1 version is released, in order to flesh out the
remaining upgrade issues. Until .1 you need either -d or --proposed
to upgrade.
10.04.1 is expected on July 29th.
** Changed in: update-manager-core (Ubuntu)
Besides this bug report, where is this listed?
--
'do-release-upgrade' requires the '-d' flag to upgrade from dapper to hardy,
and from hardy to lucid
https://bugs.launchpad.net/bugs/223741
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
http://www.ubuntu.com/desktop/get-ubuntu/upgrade
https://help.ubuntu.com/community/LucidUpgrades
...
--
'do-release-upgrade' requires the '-d' flag to upgrade from dapper to hardy,
and from hardy to lucid
https://bugs.launchpad.net/bugs/223741
You received this bug notification because you are
Neither of those links appear to provide any reference to LTS upgrades
not needing either the -d or the --proposed after the LTS.1 release. I
could be overlooking it, but I can't seem to find any reference to this
functionality outside of this bug report.
--
'do-release-upgrade' requires the
** Also affects: server-papercuts
Importance: Undecided
Status: New
--
'do-release-upgrade' requires the '-d' flag to upgrade from dapper to hardy,
and from hardy to lucid
https://bugs.launchpad.net/bugs/223741
You received this bug notification because you are a member of Ubuntu
Confirmed for me, too. In order to upgrade my system from Hardy to
Lucid, I need to use the -d option with update-manager.
--
'do-release-upgrade' requires the '-d' flag to upgrade from dapper to hardy,
and from hardy to lucid
https://bugs.launchpad.net/bugs/223741
You received this bug
This same bug now applies to upgrading from Hardy (8.04) to Lucid
(10.04). Issuing sudo do-release-upgrade does not find the new LTS
release. Heck, even the release notes seem to indicate that passing a
-d is the proper way. This seems very broken and less than
desirable to me.
--
** Summary changed:
- 'do-release-upgrade' requires the '-d' flag to upgrade from dapper to hardy
+ 'do-release-upgrade' requires the '-d' flag to upgrade from dapper to hardy,
and from hardy to lucid
--
'do-release-upgrade' requires the '-d' flag to upgrade from dapper to hardy,
and from
Using the '-d' flag now causes Packages.bz2 and Sources.bz2 Hash Sum
mismatch's. sudo do-release-upgrade by itself now works. Please modify
the upgrade instructions on http://www.ubuntu.com/getubuntu/upgrading as
this is causing considerable problems with folks trying to upgrade. I've
just tested
I can confirm this, I have a dapper system that reports No new release
found to the command sudo do-release-upgrade and does update the
system if the -d flag is used.
** Changed in: update-manager-core (Ubuntu)
Status: New = Confirmed
--
'do-release-upgrade' requires the '-d' flag to
12 matches
Mail list logo
