Your message dated
with message-id <[email protected]>
and subject line apt-proxy removed from Debian unstable
has caused the Debian Bug report #267617,
regarding apt-proxy: v2 upgrade, http_proxy => exceptions.ValueError: unpack
list of wrong size
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
267617: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=267617
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: apt-proxy
Version: 1.9.17
Severity: normal
After an upgrade to apt-proxy v2, apt-proxy seized to work. Even a simple
apt-get update
would not see much of a reaction from apt-proxy.
What happened before? The upgrade process had not understood the line
export http_proxy=http://wwwproxy.nw.dv-ratio.com:3128/
in my old configuration file. So I had added
http_proxy = http://wwwproxy.nw.dv-ratio.com:3128/
to the v2 configuration file. This gave me a nice exception in
/var/log/apt-proxy.log , with the last two lines:
File
"/usr/lib/python2.3/site-packages/apt_proxy/apt_proxy.py",
line 535, in activate
(self.proxy_host, self.proxy_port) =
request.factory.http_proxy.split(':')
exceptions.ValueError: unpack list of wrong size
- plus the above symptoms; apt-proxy did not work.
At this point, I read the manual page and tried
http_proxy = wwwproxy.nw.dv-ratio.com:3128
- and that worked.
I suggest three things:
The upgrade process to v2 should parse and understand http_proxy
and ftp_proxy lines from the old configuration.
The situation should be clarified in the apt-proxy-v2.conf
generated by the update, through a comment. Something like
;; Use HTTP proxy?
; http_proxy = your.proxy.server:port
would help a lot.
Thirdly, the parser should be extended to also handle the usual
format http://your.proxy.server:port/ . It should be easy to
distinguish, as hostnames do not tend to start with http:// .
Regards, and thank you for providing fine software
Andreas
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.4.26-1-686
Locale: lang=de...@euro, lc_ctype=de...@euro
Versions of packages apt-proxy depends on:
ii bzip2 1.0.2-1 A high-quality block-sorting file
ii debconf 1.4.30 Debian configuration management sy
ii python 2.3.4-1 An interactive high-level object-o
ii python-apt 0.5.10 Python interface to libapt-pkg
ii python-twisted 1.3.0-2 Event-based framework for internet
-- debconf information:
* apt-proxy/upgrading-v2:
* apt-proxy/upgrading-v2-result:
--- End Message ---
--- Begin Message ---
Version: 1.9.37+rm
apt-proxy has been removed from Debian unstable: http://bugs.debian.org/576821
Closing its bugs with a Version higher than the last unstable upload.
More information about this script at:
http://git.debian.org/?p=users/morph/mass-bugs-close.git;a=blob_plain;f=README;hb=HEAD
--- End Message ---
