Hi Andreas, my proposal to remove/disable the calls to arm() may be the correct fix but it's hard to guess whether apt-proxy has other problems that I'm triggering from both a Sarge and Sid apt-get client which results in 503 errors or if it is related to the missing arm() calls.
You say that it might be a frontend problem (apt-get). If this is the case I'm not sure there will be a apt-proxy compatibility fix for apt-get released to Sarge and I'm also not sure that apt-get in Sarge is broken at all. To me apt-proxy is the point of failure, at least with my patched-(tried-to-fix-Twisted-incompatibility)-version. Re: The apt cache "clean" strangeness: On one of my tries (with the not yet completely patched version) apt-proxy exceptioned and apt-get failed with 503 and the only way to install with the completely patched apt-proxy (restarted of course) was to "apt-get clean" and re-download/-install package X. On Sarge and Sid I get 503s everytime right now with the patched apt-proxy (especially if it needs to download dependencies) and apt-get dist-upgrade on Sid against apt-proxy does not work at all. Is there anyone out there where the diff I posted fixes apt-proxy without any side-effects? Anyway, I'm not an APT, apt-proxy or Twisted expert, so don't take my word on it. There might be other problems I run into which are not related to the removed arm() calls.
