Suggestions for upgrade
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubuntu-release-upgrader (Ubuntu) |
Triaged
|
Wishlist
|
Unassigned | ||
update-manager (Ubuntu) |
Invalid
|
Wishlist
|
Unassigned |
Bug Description
I have 2 suggestions for the upgrade to avoid the server-crash ubuntu suffered in the release of feisty and would be helpful for users too.
1) I think it would be useful to have an option in the update manager to choose if you want to upgrade in the first moment you see the advise or to postpone for some other time.
An example:
Update-Manager have found a new version of Ubuntu: Feisty 7.04.
Do you want to upgrade now?
Yes - No
If you choose No then you see something like:
See a reminder about the upgrade in: ____ days
2) Update-Manager should check the availability of the servers so if they are down should warn you instead of start the process and stop in the middle.
Something like:
Sorry the upgrade process will not start because Ubuntu servers are busy, try later.
Thanks
Changed in update-manager: | |
importance: | Undecided → Wishlist |
status: | Unconfirmed → Confirmed |
Changed in update-manager: | |
status: | Confirmed → Invalid |
affects: | update-manager (Ubuntu) → ubuntu-release-upgrader (Ubuntu) |
affects: | update-manager → update-manager (Ubuntu) |
I think that my comment is related to this item.
Every time (so far) I try to use update manager to load 8.04 LTS I get to the "Distribution Upgrade" screen with a bunch of messages like this:
Failed to fetch http:// ca.archive. ubuntu. com/ubuntu/ dists/hardy/ Release. gpg Could not connect to ca.archive. ubuntu. com:80 (129.97.134.71), connection timed out ca.archive. ubuntu. com/ubuntu/ dists/hardy/ main/i18n/ Translation- en_CA.bz2 Connection failed ca.archive. ubuntu. com/ubuntu/ dists/hardy/ restricted/ i18n/Translatio n-en_CA. bz2 Connection failed ca.archive. ubuntu. com/ubuntu/ dists/hardy/ universe/ i18n/Translatio n-en_CA. bz2 Could not connect to ca.archive. ubuntu. com:80 (129.97.134.71), connection timed out
Failed to fetch http://
Failed to fetch http://
Failed to fetch http://
etc ...
I really don't understand why this is happening, but it seems like maybe something to do with the servers not being available. It would be useful if there was a button to "try again later" or something. As it is I have to go all the way back to the beginning of the process. Going back to the beginning is not a big deal, but maybe there is a better way?