Bug#349447: apt-proxy: patch does not work
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.
Bug#349447: apt-proxy: patch does not work
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. pgpyZwnwjp2kk.pgp Description: PGP signature
Bug#349447: apt-proxy: patch does not work
Summary of my private reply to Andreas for the record: 1) I only use FTP backends 2) Yes all apt-get clients ran flawlessly before the upgrade with apt-proxy and Twisted in Sarge. Actually I upgraded to Sid due to other reasons and I'm not sure I will downgrade as there are core packages which I need to be newer than in Sarge or Testing without pinning etc. 3) I can imagine apt-proxy having other bugs which only surfaced now in Sid and with the new Twisted 4) I may turn on debug logs and try again
Bug#349447: apt-proxy: patch does not work
Package: apt-proxy Version: 1.9.32-0 Followup-For: Bug #349447 Hi, sorry for cp from BTS website, but I wanted to clarify that (at least here ony my server) the proposed workaround I posted to #349447 does not fix the problem. yes, apt-proxy seems to work but fails in many places as presumably the success-/error-handlers are not called correctly anymore. advice of Twisted experts needed. Tuncer, did you even check the source? This fix is already in place since _Sarge_, arm() is defined as: def arm(): pass In Etch's twisted (2.0.X) it's defined with a deprecation warning, which you should be able to see on your apt-proxy logs. Now in twisted 2.1.0 this function was completely removed as proposed by the deprecation warning. That (and the move of the web module) broke apt-proxy with twisted 2.1.0. The only version I could find on debians server that includes a real implementation for arm() is 0.15.5, which I guess is from woody. The callbacks are definitely called, as well as the Errbacks. I can see that in the log of apt-proxy. I'd also like to have a twisted expert to have a look at apt-proxy, but for knowing that the removal of arm()-calls and adding the dependecy on twisted-web fixes this bug-report you don't need one. At least not when you're able to read python code. Regarding your problems: I already stated that the 2 examples you gave pretty much look like frontend-problems, i.e. apt-get or whatever you use. Those problems might have been introduced by the same time you installed the fixed version of apt-proxy. Or something really weird is going on on your server if it actually reads packages from /var/cache/apt/archives (which is the place that apt-get clean cleans). Andreas -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (990, 'unstable'), (500, 'experimental'), (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-cherry Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Versions of packages apt-proxy depends on: ii adduser 3.80 Add and remove users and groups ii bzip2 1.0.3-2high-quality block-sorting file co ii debconf [debconf-2.0] 1.4.68 Debian configuration management sy ii logrotate 3.7.1-2Log rotation utility ii python2.3.5-5An interactive high-level object-o ii python-apt0.6.16 Python interface to libapt-pkg ii python-bsddb3 3.3.0-6Python interface to libdb3 ii python-twisted2.1.0-2Event-based framework for internet ii python-twisted-web0.5.0-1An HTTP protocol implementation to apt-proxy recommends no packages. -- debconf information: * apt-proxy/upgrading-v2: * apt-proxy/upgrading-v2-result: -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
