Today I figured out that it gets better if I leave out the Squid proxy cache between aptitude and apt-proxy. But still apt-proxy hangs, and still it's happening almost always, which makes it unusable to me. (Should I raise the severity to "grave"?)
Without Squid, the "big" tracebacks don't show up in apt-proxy.log, but
still this:
2005/07/05 09:34 CEST [Channel,12,127.0.0.1] [debug] Headers: Host:
localhost:9999, Connection: keep-alive, If-Modified-Since: Sat, 18 Jun 2005
08:02:10 GMT, User-Agent: Debian APT-HTTP/1.3
2005/07/05 09:34 CEST [Channel,12,127.0.0.1] [debug] Request: GET
/blackdown/dists/unstable/non-free/binary-i386/Packages.gz
2005/07/05 09:34 CEST [Channel,12,127.0.0.1] [debug] starting verification:
/bin/gunzip ('/bin/gunzip', '-t', '-v',
'/var/cache/apt-proxy/blackdown/dists/unstable/non-free/binary-i386/Packages.gz')
2005/07/05 09:34 CEST [-] Starting factory
<twisted.internet.protocol._InstanceFactory instance at 0xb758b72c>
2005/07/05 09:34 CEST [-] Enabling Multithreading.
2005/07/05 09:34 CEST [-]
/usr/lib/python2.3/site-packages/apt_proxy/apt_proxy.py:759:
exceptions.DeprecationWarning: Deferred.arm is deprecated, and does nothing.
You should stop calling it.
And then apt-proxy hangs. After a few minutes "aptitude update" fails with:
Err http://localhost unstable/non-free Release
Connection failed
Thanks,
- Stephan.
signature.asc
Description: Digital signature
