On 25.01.06 09:11:54, Tuncer Ayaz wrote: > 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.
As I said before, the missing arm calls produced warnings with twisted 2.0 and did nothing in twisted 1.3. Now apart from that: apt-proxy had several issues in the past and besides my own system here probably still has issues. > 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. You never mentioned Sarge Systems, of course their apt-get should be Ok and thus the failure probably lies on apt-proxy side, however it can't be the removed arm() callls, it just can't. If apt-proxy doesn't work for you anymore, turn on debugging and file a bugreport. Though honestly I don't think anyone has time/cares ATM for apt-proxy.... > 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. Then apt-get thought the package it downloaded from apt-proxy was already completely downloaded but it wasn't or apt-proxy produced garbage in the file it sent. From this description it might be an apt-proxy problem, especially when comparing apt-proxy's bugginess to the one of apt-get... > 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. So, as I said above turn on debugging and see where that takes you. BTW: Does "the old" apt-proxy work in tahose cases, i.e. the one with arm-calls and an older twisted? > Is there anyone out there where the diff I posted fixes apt-proxy > without any side-effects? It works here, though I did not yet check my http-backends. If you're interested in those results I can test them on the weekend and let you know how it goes. I suspect that the new twisted-web package might have broken apt-proxy's http backend. The tests I did so far were always using ftp-backends > 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. That's all I wanted to clarify, it _can't_ be related to the arm calls, as they practically weren't there before the new twisted. But it can be related to the twisted, though probably not to the Defer-stuff, but something else. Andreas -- You too can wear a nose mitten.
pgp4IgWU8szwu.pgp
Description: PGP signature
