Your message dated Sun, 8 Jul 2007 15:51:09 +0200
with message-id <[EMAIL PROTECTED]>
and subject line closing failed upgrade report
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: apt-proxy
Version: 1.9.17
Since I've upgraded to apt-proxy v2, I always get error messages like:
Err http://192.168.55.2 unstable/main Packages
Connection failed
Err http://192.168.55.2 unstable/main Release
Connection failed
Err http://192.168.55.2 unstable/contrib Packages
Connection failed
Nothing is written to the log file, despite having the line:
debug = all:9 db:4
My backend in the conf file are:
[debian]
backends =
http://ftp.us.debian.org/debian
http://ftp.de.debian.org/debian
http://ftp.uk.debian.org/debian
[non-US]
backends =
http://non-us.debian.org
http://ftp.de.debian.org/debian-non-US
http://ftp.uk.debian.org/debian-non-US
[security]
backends =
http://security.debian.org
If I telnet or use a browser to go to 192.168.55.2:9999 it says the
following (this doesn't look good, my it might be expected - I don't
know!):
Updating twisted's process module.
No updating required.
Traceback (most recent call last):
File "/usr/sbin/apt-proxy", line 22, in ?
application.run(0)
AttributeError: Componentized instance has no attribute 'run'
(So I'm guessing thats not even starting which is why nothing gets
written to the log, but that just a guess - to be honest I've got no
idea what twisted even does!)
Package versions:
ii python-twisted 1.3.0-2
ii python-apt 0.5.10
ii python 2.3.4-3sid
ii apt-proxy 1.9.17
Linux trinity 2.6.7 #1 SMP Sat Jun 26 14:51:58 BST 2004 i686 GNU/Linux
Thanks,
Matt Nottingham
--- End Message ---
--- Begin Message ---
Bug 268797 had it's previous update in september 2004,
that is almost three years. And it did state
| After chatting IRC a workaround was established - if /etc/inetd.conf
| is edited and the (old) reference to apt-proxy removed (and inet
| restarted) then it all works as normal.
So now closing this bugreport because
* submitter reports it works
* the long time of no update.
* lately not seen any other upgrade bugs like this one
Cheers
Geert Stappers
--- End Message ---
