Ubuntu
update-manager package

Ubuntu 'do_release_upgrade" doesn't work behind proxy

Bug #115388 reported by zapodot
8
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)
Fix Released
Low
Michael Vogt

Bug Description

Binary package hint: update-manager-core

I am trying to upgrade Ubuntu on a "firewalled" server running Ubuntu Edgy Server to Feisty with the "do_release_upgrade" command, but it reports that no new version was found..

My guess is that it can have something to do with the firewall which the server has to get through. To get apt-get working I'm need to use a http proxy server, maybe do_release_upgrade need that to?
I have not found any way of specifying proxy settings for "do_release_upgrade" (e.g no command line switch), shouldn't there be?

See original description
Revision history for this message
Brian Murray (brian-murray) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. I believe this is known issue with update-manager.

Changed in update-manager:
assignee: nobody → mvo
importance: Undecided → Low
status: New → Confirmed
Revision history for this message
MoMaT (momat) wrote :

Confirming. I'm using Ubuntu Server behind proxy and despite "Acquire::http::Proxy" settings in /etc/apt/apt.conf (which works fine for aptitude) can't upgrade Gutsy->Hardy using do_realease_upgrade. ("No new release found").

description: updated
Revision history for this message
Stefano Rivera (stefanor) wrote :

http_proxy=http://foo:3128/ do_release_upgrade

works for me

Revision history for this message
Graeme Hewson (ghewson) wrote :

It would be a big help to others if the instructions at http://www.ubuntu.com/getubuntu/upgrading were to mention the manual proxy setting.

Revision history for this message
Michael Vogt (mvo) wrote :

This is fixed now in intrepid. It will search for the proxy based on the apt.conf configuration, the synaptic configuration and the gconf environemnt (and of course the http_proxy environment).

Changed in update-manager:
status: Confirmed → Fix Released
Revision history for this message
Stefano Rivera (stefanor) wrote :

Unfortunatly that doesn't help me with my *really* horrible case. We have a university where everyone is behind NTLM-authenticating proxies (yes, braindead). However we have a local mirror.

Can the upgrade not be done in a way that doesn't require internet access, but just a local mirror?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.