Thanks for following up. I'm closing this report due to your last comment.
Don't hesitate to submit any new bug.
** Changed in: update-manager (Ubuntu)
Status: Incomplete = Invalid
** Changed in: apt-cacher (Ubuntu)
Status: New = Invalid
--
update-manager ignores karmic
Jean-Baptiste Lallement schrieb:
@Florian, did you check if the version in jaunty-proposed helps with
this problem?
No, I have no jaunty installation anymore.
--
update-manager ignores karmic
https://bugs.launchpad.net/bugs/466521
You received this bug notification because you are a member of
@Florian, did you check if the version in jaunty-proposed helps with
this problem?
** Changed in: update-manager (Ubuntu)
Status: New = Incomplete
--
update-manager ignores karmic
https://bugs.launchpad.net/bugs/466521
You received this bug notification because you are a member of Ubuntu
Thanks for your bugreport.
Could you please check if the version in jaunty-proposed helps with this
problem? It fixes a proxy releated bug.
--
update-manager ignores karmic
https://bugs.launchpad.net/bugs/466521
You received this bug notification because you are a member of Ubuntu
Bugs, which
MetaRelease.py (the Python code that does the check for a new release)
uses urllib2 directly, and doesn't use the apt/synaptic settings.
Although urllib2 looks at the environment variables for proxy settings,
sudo zaps these for security reasons. I was able to make it work by
using sudo -s to get
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/34770481/Dependencies.txt
--
update-manager ignores karmic
https://bugs.launchpad.net/bugs/466521
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Also affects: apt-cacher (Ubuntu)
Importance: Undecided
Status: New
--
update-manager ignores karmic
https://bugs.launchpad.net/bugs/466521
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
The problem is somewhere between update-manager and apt-cacher. I just
removed the proxy definition from apt.conf.d and started update-manager,
which now noticed the new release. Then I quit update-manager, put the
apt-cacher proxy definition back in, started update-manager again and
now the
