The meta-release file should be moved to archive.ubuntu.com to let the mirrors carry it
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
update-manager (Ubuntu) |
Triaged
|
Low
|
Unassigned |
Bug Description
Binary package hint: update-manager
The upgrade manager needs to download http://
For firewalled machines with a local mirror and machines requiring NTLM-authenticated proxy access, there is never an "upgrade" button. Even if there is a complete local mirror.
Another problem with this as reported in some duplicates is that the release upgrade available notification appears when the meta-release file is updated on changelogs.
Observed on the Gutsy->Hardy upgrade. We run a local FTP mirror, and our users have not been getting the option to upgrade, because outside connections to port 80 are firewalled. (NTLM proxies preferred). We worked around this by setting up a special proxy for meta-release.
Preferably the meta-release file should be moved to archive.ubuntu.com where the mirrors can carry it, and update-manager can get it from a local mirror. If this isn't possible, a configurable location would at least help our users.
I've discussed this with mvo, he agrees that this should be solved.
Changed in update-manager: | |
status: | New → Confirmed |
tags: | added: intrepid2jaunty |
tags: | removed: gutsy2hardy |
Changed in update-manager (Ubuntu): | |
status: | Fix Released → Triaged |
Changed in update-manager (Ubuntu): | |
assignee: | Rolf Leggewie (r0lf) → nobody |
Changed in update-manager (Ubuntu): | |
importance: | Undecided → Low |
summary: |
- Update-manager requires connectivity to changelog.ubuntu.com - mirrors - alone aren't sufficient + The meta-release file should be moved to archive.ubuntu.com to let the + mirrors carry it. |
summary: |
The meta-release file should be moved to archive.ubuntu.com to let the - mirrors carry it. + mirrors carry it |
description: | updated |
Any chance this can be fixed before the Intrepid release? After Hardy's release I had to fix quite a few of our users' machines after botched upgrades due to them trying every trick they could find on the internet to force the upgrade.