I just verified that all downloads go through the proxy when using
update-manager (I used a squid proxy for the verification). I strongly
suspect this is a bug with apt-cacher. Please reopen if the apt-cacher
logs indicate that this is not the case and attach them here.
Thanks,
Michael
**
I changed the code so that the error message is clearer at least.
--
When apt-cacher is used, Update-Manger fails (not #78673 duplicate)
https://bugs.launchpad.net/bugs/113658
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
here's my workaround
cp /etc/apt/sources.list /etc/apt/sources.list.backup
insert=`sed -e s/^A.* \//; s/\;$// ; s,/$,, /etc/apt/apt.conf`
sed -i -e s,http://,$insert/,; /etc/apt/sources.list
cat /etc/apt/sources.list
mv /etc/apt/apt.conf /etc/apt/apt.conf.proxy
update-manager -d -c
cp
I have reported shemgp's fix (see bug 156070) upstream:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=502985
--
When apt-cacher is used, Update-Manger fails (not #78673 duplicate)
https://bugs.launchpad.net/bugs/113658
You received this bug notification because you are a member of Ubuntu
It looks to me like that there was an update to apt-cacher in Intrepid
that may resolve this bug. If anybody could test a distribution upgrade
using an apt-cacher server on Intrepid that would be quite helpful.
Thanks in advance.
** Changed in: update-manager (Ubuntu)
Status: Confirmed =
When I upgrade to Intrepid after the release, I'll test that. However, I
doubt whether any fix to apt-cacher can fix this bug, since apt-cacher
is behaving correctly. It's update-manager that doesn't correctly handle
APT's configuration option Acquire::http::Proxy. The proof is that when
The bug report that has the apt-cacher fix is bug 156070.
--
When apt-cacher is used, Update-Manger fails (not #78673 duplicate)
https://bugs.launchpad.net/bugs/113658
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
I can confirm that apt-cacher 1.6.4ubuntu1 in intrepid which includes
the fix described in bug 156070 does indeed work properly as a proxy for
update-manager when it's used via Acquire::http::proxy. Marking this bug
as closed.
** Changed in: update-manager (Ubuntu)
Status: Incomplete = Fix
** Tags added: apt-cacher dist-upgrade distribution update-manager
upgrade
--
When apt-cacher is used, Update-Manger fails (not #78673 duplicate)
https://bugs.launchpad.net/bugs/113658
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Changed in: update-manager (Ubuntu)
Importance: Undecided = Medium
Target: None = later
--
When apt-cacher is used, Update-Manger fails (not #78673 duplicate)
https://bugs.launchpad.net/bugs/113658
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I confirm that this bug still exists in the update from Hardy to
Intrepid Beta
Here are the messages from console (I translated them from Italian so
probably they not fully compliant with the originals):
extracting 'intrepid.tar.gz'
authenticate 'intrepid.tar.gz' against 'intrepid.tar.gz.gpg'
** Tags added: proxy
--
When apt-cacher is used, Update-Manger fails (not #78673 duplicate)
https://bugs.launchpad.net/bugs/113658
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
it is similar to apt-cacher, includes its own cache, and doesn't require
changes the the client sources.list.
Page you are referring to says, that client sources.list file NEEDS to be
modified. Is that so?
--
When apt-cacher is used, Update-Manger fails (not #78673 duplicate)
Any hopes to have this fixed before 8.10 is released? I installed apt-
cacher on my company's server hoping to ease the bandwidth pain during
the upgrade of our ubuntu boxes.
Claudio's workaround is fine, but I'd rather prefer update-manager to do
the right thing by itself, instead of telling
The problem seems to manifest in
UpdateManager/Core/DistUpgradeFetcherCore.py , in method
DistUpgradeFetcherCore.authenticate:
authenticate '/tmp/tmpy-qZkJ/feisty.tar.gz' against '/tmp/tmpy-
qZkJ/feisty.tar.gz.gpg'
The latter does not exist on the local machine, neither in the apt-
cacher cache.
I'll try the workaround, but this really needs to be fixed. Aptitude
works from the command line. Why is update-manager reinventing the wheel
in the first place? Why not let aptitude do what it's good at?
Use case:
I have satellite internet with an inadequate bandwidth quota. I have two
machines
I would like to see this fixed as well... Workarounds:
- maybe apt-proxy would be a workaround here for Scott and others:
https://help.ubuntu.com/community/AptProxy - it is similar to apt-cacher,
includes its own cache, and doesn't require changes the the client sources.list.
- also, the very
Still not fixed, upgrading from 7.10 to 8.04. What's weird is that using
a proxy worked fine with the graphical updater -- this only affects my
server.
I have bandwidth to spare, but right now, none of the mirrors do. Oh
well -- looks like that's 2 gigs more bandwidth wasted because of this
bug.
Same here... upgrading 7.04 to 7.10
workaround remove the /etc/apt/apt.conf.d/proxy file
sudo mv /etc/apt/apt.conf.d/proxy /etc/apt/apt.conf.d/proxy.old
modified the /etc/apt/sources.list as explained from Claudio Satriano
HTH
--
When apt-cacher is used, Update-Manger fails (not #78673
Confirmed that the workaround from Claudio Satriano with modified
sources.list is a workaround for this issue.
** Changed in: update-manager (Ubuntu)
Status: New = Confirmed
--
When apt-cacher is used, Update-Manger fails (not #78673 duplicate)
https://bugs.launchpad.net/bugs/113658
You
I confirm this bug on all my machines using apt-cacher 1.5.3 on a Debian Etch
server and trying to upgrade the client from Feisty to Gutsy.
As soon as I remove the line Acquire::http::Proxy from /etc/apt/apt.conf
, the upgrade starts.
--
When apt-cacher is used, Update-Manger fails (not
Can this be related to Bug #24250 ??
--
When apt-cacher is used, Update-Manger fails (not #78673 duplicate)
https://bugs.launchpad.net/bugs/113658
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Hmm, after further investigation, I do believe it is a proxy-related
problem (see Bug #24250), not directly connected to apt-cacher.
In fact, if I use a syntax like the following for all the entries in
/etc/apt/sources.list:
deb http://hostname:3142/it.archive.ubuntu.com/ubuntu/ feisty main
I forgot to say that on this machine I have apt running as a client of
apt-cacher on another machine - I've only just seen this bug report so I
can't retry the upgrade to Gutsy. However, here's the relevant config
file from /etc/apt/apt.conf.d:
Acquire::http::Proxy http://valluga:3142;;
Valluga
I had exactly this problem with Xubuntu on a Feisty to Gutsy RC upgrade
on Oct 15th, i.e. before 7.10 release. I tried doing sudo dbus-launch
update-manager -d and so on, but nothing worked.
In the end I did an aptitude dist-upgrade, which worked well - however
update-manager should be fixed.
I
See dist-upgrade logs attached
** Attachment added: dist-upgrade-logs.tar.gz
http://librarian.launchpad.net/7592377/dist-upgrade-logs.tar.gz
--
When apt-cacher is used, Update-Manger fails (not #78673 duplicate)
https://bugs.launchpad.net/bugs/113658
You received this bug notification
26 matches
Mail list logo
