Menu
▾
▴
apt-proxy-users — Users of apt-proxy
You can subscribe to this list here.
| 2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(2) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
|
Feb
(5) |
Mar
|
Apr
(2) |
May
(3) |
Jun
|
Jul
|
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2002 |
Jan
(2) |
Feb
(5) |
Mar
(14) |
Apr
(1) |
May
(7) |
Jun
(2) |
Jul
(7) |
Aug
(13) |
Sep
(21) |
Oct
(3) |
Nov
|
Dec
|
| 2003 |
Jan
(6) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(5) |
Oct
(5) |
Nov
|
Dec
(3) |
| 2004 |
Jan
(11) |
Feb
(2) |
Mar
(4) |
Apr
|
May
(9) |
Jun
|
Jul
(1) |
Aug
(12) |
Sep
(6) |
Oct
(7) |
Nov
(10) |
Dec
(3) |
| 2005 |
Jan
(22) |
Feb
(20) |
Mar
(5) |
Apr
(10) |
May
(15) |
Jun
(14) |
Jul
(9) |
Aug
(3) |
Sep
(7) |
Oct
(1) |
Nov
(3) |
Dec
(12) |
| 2006 |
Jan
(1) |
Feb
(1) |
Mar
(5) |
Apr
|
May
|
Jun
(2) |
Jul
|
Aug
|
Sep
(2) |
Oct
|
Nov
(2) |
Dec
(2) |
| 2007 |
Jan
|
Feb
(3) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Jay S. <me...@he...> - 2005-07-11 05:38:25
|
Helloooooo out there, anyone still on this list? Thanks Jay Jay Strauss wrote: > Hi, all of a sudden I'm getting connection refused on my apt-proxy > server. I haven't made any changes. As an example of my error, I did > aptitude update on the box with the apt-proxy server running. > > Any guidance would be greatly appreciated. > > Please note that the host "iron" is IP 192.168.5.26 > > Thank you > Jay > > iron:~# aptitude update > Reading Package Lists... Done > Building Dependency Tree > Reading extended state information > Initializing package states... Done > Reading task descriptions... Done > Err http://192.168.5.26 sarge/main Packages > Connection failed > Err http://192.168.5.26 sarge/main Release > Connection failed > Err http://192.168.5.26 sarge/main Sources > Connection failed > Err http://192.168.5.26 sarge/main Release > Connection failed > Err http://192.168.5.26 sarge/updates/main Packages > Connection failed > Err http://192.168.5.26 sarge/updates/main Release > Connection failed > Err http://192.168.5.26 sarge/updates/contrib Packages > Connection failed > Err http://192.168.5.26 sarge/updates/contrib Release > Connection failed > Err http://192.168.5.26 sarge/updates/non-free Packages > Connection failed > Err http://192.168.5.26 sarge/updates/non-free Release > Connection failed > Reading Package Lists... Done > Building Dependency Tree > Reading extended state information > Initializing package states... Done > Reading task descriptions... Done > > > Below are my config files: > > iron:~# cat /etc/apt/sources.list > deb http://192.168.5.26:9999/debian sarge main > deb-src http://192.168.5.26:9999/debian sarge main > deb http://192.168.5.26:9999/security sarge/updates main contrib non-free > > iron:~# cat /etc/apt-proxy/apt-proxy.conf | grep -v -e'^#' > > APT_PROXY_CACHE=/var/cache/apt-proxy > > add_backend /debian/ \ > $APT_PROXY_CACHE/debian/ \ > http://ftp.us.debian.org/debian/dists/ \ > http://ftp.de.debian.org/debian/ \ > http://ftp.uk.debian.org/debian/ \ > +ftp.us.debian.org::debian/ > > > add_backend /non-US/ \ > $APT_PROXY_CACHE/non-US/ \ > http://non-us.debian.org/ \ > http://ftp.de.debian.org/debian-non-US/ \ > http://ftp.uk.debian.org/debian-non-US/ \ > +ftp.de.debian.org::debian-non-US/ > > > add_backend /security/ \ > $APT_PROXY_CACHE/security/ \ > http://security.debian.org/ > > > add_backend /java/ \ > $APT_PROXY_CACHE/java/ \ > ftp://ftp.tux.org/java/debian/ > > CLEANUP_DAYS=14 > CLEAN_SWEEP=60 > MAX_VERSIONS=2 > BACKEND_FREQ=240 > RSYNC_TIMEOUT=30 > WGET_TIMEOUT=30 > > iron:~# cat /etc/inetd.conf | grep -v -e'^#' > > ident stream tcp wait identd /usr/sbin/identd identd > > swat stream tcp nowait.400 root /usr/sbin/tcpd > /usr/sbin/swat > 9999 stream tcp nowait.400 aptproxy /usr/sbin/tcpd > /usr/sbin/apt-proxy -l /var/log/apt-proxy.log > > rsync stream tcp nowait root /usr/bin/rsync > rsyncd --daemon > > > ------------------------------------------------------- > This SF.Net email is sponsored by the 'Do More With Dual!' webinar > happening > July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual > core and dual graphics technology at this free one hour event hosted by > HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar > _______________________________________________ > Apt-proxy-users mailing list > Apt...@li... > https://lists.sourceforge.net/lists/listinfo/apt-proxy-users > > > |
|
From: Jay S. <me...@he...> - 2005-07-09 17:34:58
|
Hi, all of a sudden I'm getting connection refused on my apt-proxy
server. I haven't made any changes. As an example of my error, I did
aptitude update on the box with the apt-proxy server running.
Any guidance would be greatly appreciated.
Please note that the host "iron" is IP 192.168.5.26
Thank you
Jay
iron:~# aptitude update
Reading Package Lists... Done
Building Dependency Tree
Reading extended state information
Initializing package states... Done
Reading task descriptions... Done
Err http://192.168.5.26 sarge/main Packages
Connection failed
Err http://192.168.5.26 sarge/main Release
Connection failed
Err http://192.168.5.26 sarge/main Sources
Connection failed
Err http://192.168.5.26 sarge/main Release
Connection failed
Err http://192.168.5.26 sarge/updates/main Packages
Connection failed
Err http://192.168.5.26 sarge/updates/main Release
Connection failed
Err http://192.168.5.26 sarge/updates/contrib Packages
Connection failed
Err http://192.168.5.26 sarge/updates/contrib Release
Connection failed
Err http://192.168.5.26 sarge/updates/non-free Packages
Connection failed
Err http://192.168.5.26 sarge/updates/non-free Release
Connection failed
Reading Package Lists... Done
Building Dependency Tree
Reading extended state information
Initializing package states... Done
Reading task descriptions... Done
Below are my config files:
iron:~# cat /etc/apt/sources.list
deb http://192.168.5.26:9999/debian sarge main
deb-src http://192.168.5.26:9999/debian sarge main
deb http://192.168.5.26:9999/security sarge/updates main contrib non-free
iron:~# cat /etc/apt-proxy/apt-proxy.conf | grep -v -e'^#'
APT_PROXY_CACHE=/var/cache/apt-proxy
add_backend /debian/ \
$APT_PROXY_CACHE/debian/ \
http://ftp.us.debian.org/debian/dists/ \
http://ftp.de.debian.org/debian/ \
http://ftp.uk.debian.org/debian/ \
+ftp.us.debian.org::debian/
add_backend /non-US/ \
$APT_PROXY_CACHE/non-US/ \
http://non-us.debian.org/ \
http://ftp.de.debian.org/debian-non-US/ \
http://ftp.uk.debian.org/debian-non-US/ \
+ftp.de.debian.org::debian-non-US/
add_backend /security/ \
$APT_PROXY_CACHE/security/ \
http://security.debian.org/
add_backend /java/ \
$APT_PROXY_CACHE/java/ \
ftp://ftp.tux.org/java/debian/
CLEANUP_DAYS=14
CLEAN_SWEEP=60
MAX_VERSIONS=2
BACKEND_FREQ=240
RSYNC_TIMEOUT=30
WGET_TIMEOUT=30
iron:~# cat /etc/inetd.conf | grep -v -e'^#'
ident stream tcp wait identd /usr/sbin/identd
identd
swat stream tcp nowait.400 root /usr/sbin/tcpd
/usr/sbin/swat
9999 stream tcp nowait.400 aptproxy /usr/sbin/tcpd
/usr/sbin/apt-proxy -l /var/log/apt-proxy.log
rsync stream tcp nowait root /usr/bin/rsync
rsyncd --daemon
|
|
From: SourceForge.net <no...@so...> - 2005-07-09 02:49:39
|
Bugs item #1217563, was opened at 2005-06-09 10:13 Message generated for change (Comment added) made by ouef You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=112078&aid=1217563&group_id=12078 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Apt-proxy and http_proxy Initial Comment: Hi! I moved from Debian's Woody apt-proxy to Debian's Sarge apt-proxy. apt-proxy-v1tov2 converted my old apt-proxy.conf configuration file to apt-proxy-v2.conf new format. I usually use a HTTP Proxy server with user authentication to fetch packages from Debian repositories. wget works properly. In the new configuration file I use: http_proxy = http://nameuser:passworduser@httphost:hostport When I try to apt-get from a client, it hangs on client's side and later I receive "Connection failed". On server side I receive this error in the log file: 2005/06/09 15:56 CEST [Channel,0,10.26.226.231] [Fetcher.activate] (debian) servers:4/debian/dists/stable/main/binary-i386/Packages.gz 2005/06/09 15:56 CEST [Channel,0,10.26.226.231] Unhandled error in Deferred: 2005/06/09 15:56 CEST [Channel,0,10.26.226.231] Traceback (most recent call last): File "/usr/lib/python2.3/site-packages/twisted/protocols/http.py", line 557, in requestReceived self.process() File "/usr/lib/python2.3/site-packages/apt_proxy/apt_proxy.py", line 1375, in process self.fetch() File "/usr/lib/python2.3/site-packages/apt_proxy/apt_proxy.py", line 1454, in fetch (dummyFetcher, 0, running,), None) File "/usr/lib/python2.3/site-packages/twisted/internet/defer.py", line 205, in addCallbacks self._runCallbacks() --- <exception caught here> --- File "/usr/lib/python2.3/site-packages/twisted/internet/defer.py", line 338, in _runCallbacks self.result = callback(self.result, *args, **kw) File "/usr/lib/python2.3/site-packages/apt_proxy/apt_proxy.py", line 1422, in fetch_real fetcher = dummyFetcher.apEndTransfer(fetcher_class) File "/usr/lib/python2.3/site-packages/apt_proxy/apt_proxy.py", line 463, in apEndTransfer fetcher = fetcher_class(req) File "/usr/lib/python2.3/site-packages/apt_proxy/apt_proxy.py", line 317, in __init__ self.activate(request) File "/usr/lib/python2.3/site-packages/apt_proxy/apt_proxy.py", line 553, in activate (self.proxy_host, self.proxy_port) = request.factory.http_proxy.split(':') exceptions.ValueError: unpack list of wrong size Is it an authentication problem with Http proxy server? With the previous version it worked without problems. thank you in advance, riccardo ---------------------------------------------------------------------- Comment By: François Ouellet (ouef) Date: 2005-07-08 22:49 Message: Logged In: YES user_id=1166285 I am using apt-proxy 1.9.31 from debian unstable and I get the same behavior. I have an all alphanumeric username and passord. Looking at /usr/lib/python2.3/site-packages/apt_proxy/apt_proxy.py and searching for http_proxy, It seems it's not expecting anything else than a host:port. I can't program in python. It must be real easy to fix for a knowledgeable python programmer. Thanks François ---------------------------------------------------------------------- Comment By: Chris Halls (haggai) Date: 2005-06-09 13:21 Message: Logged In: YES user_id=161154 Hi it looks like you have this problem: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=309288 Do you have special characters (: or @) in the proxy password? Can you replace them with another special character as a workaround for the problem? Thanks Chris ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=112078&aid=1217563&group_id=12078 |
|
From: SourceForge.net <no...@so...> - 2005-06-18 17:22:26
|
Bugs item #1223254, was opened at 2005-06-18 10:21 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=112078&aid=1223254&group_id=12078 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: apt-proxy-import: no suitable backend Initial Comment: Upon updating to Sarge I wanted to minimize mirror traffic so I attempted to install and initialize apt-proxy version 2. Attempting to run apt-proxy-import -i /var/cachce/apt/archives gave a permissions error. I changed the shell in /etc/passwd for aptproxy to be bash, did: su - aptproxy, and attempted to re-run the above command. At this point, I was told that every package was being skipped due to the inability to find a suitable backend. After searching the bug data base, it appears that this problem was reported, then reported fixed more than ten days ago, but it appears to still be in the apt-proxy package I installed on 2005 Jun 18. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2005-06-18 10:22 Message: Logged In: NO Email me at john at betelgeuse dot us Thanks ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=112078&aid=1223254&group_id=12078 |
|
From: SourceForge.net <no...@so...> - 2005-06-18 17:21:16
|
Bugs item #1223254, was opened at 2005-06-18 10:21 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=112078&aid=1223254&group_id=12078 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: apt-proxy-import: no suitable backend Initial Comment: Upon updating to Sarge I wanted to minimize mirror traffic so I attempted to install and initialize apt-proxy version 2. Attempting to run apt-proxy-import -i /var/cachce/apt/archives gave a permissions error. I changed the shell in /etc/passwd for aptproxy to be bash, did: su - aptproxy, and attempted to re-run the above command. At this point, I was told that every package was being skipped due to the inability to find a suitable backend. After searching the bug data base, it appears that this problem was reported, then reported fixed more than ten days ago, but it appears to still be in the apt-proxy package I installed on 2005 Jun 18. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=112078&aid=1223254&group_id=12078 |
|
From: Bram M. <bra...@li...> - 2005-06-18 11:53:57
|
Chris Halls wrote: [...] > That sounds to me like you did not restart apt-proxy after making the > configuration file updates. Could that be your problem? I did restart apt-proxy several times but apparantly not when I had made the correct adjustments... So here's the correct configuration: /etc/apt-proxy/apt-proxy-v2.conf: [debian-volatile] backends = ftp://volatile.debian.net/debian-volatile /etc/apt/sources.list: deb http://localhost:9999/debian-volatile testing/volatile main Followed by: /etc/init.d/apt-proxy restart Thanks for all the help! Bram -- # Mertens Bram "M8ram" <bra...@li...> Linux User #349737 # # debian testing kernel 2.6.8-1-686 i686 512MB RAM # # 13:52:01 up 84 days, 20:06, 7 users, load average: 0.24, 0.11, 0.10 # |
|
From: Bram M. <bra...@li...> - 2005-06-18 08:44:21
|
Chris Halls wrote: [...] > That sounds to me like you did not restart apt-proxy after making the > configuration file updates. Could that be your problem? I did restart apt-proxy several times but apparantly not when I had made the correct adjustments... So here's the correct configuration: /etc/apt-proxy/apt-proxy-v2.conf: [debian-volatile] backends = ftp://volatile.debian.net/debian-volatile /etc/apt/sources.list: deb http://localhost:9999/debian-volatile testing/volatile main Followed by: /etc/init.d/apt-proxy restart Thanks for all the help! Bram -- # Mertens Bram "M8ram" <bra...@li...> Linux User #349737 # # debian testing kernel 2.6.8-1-686 i686 512MB RAM # # 10:40:03 up 84 days, 16:54, 6 users, load average: 0.23, 0.21, 0.11 # |
|
From: SourceForge.net <no...@so...> - 2005-06-17 00:27:59
|
Bugs item #1222275, was opened at 2005-06-16 17:27 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=112078&aid=1222275&group_id=12078 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: 'NoneType' object has no attribute 'fetcher' Initial Comment: Hi, I've upgraded from woody to sarge. While running apt-get update I am getting this messages in my /var/log/apt-proxy.log file: 2005/06/16 15:16 PDT [-] 2005/06/16 15:17 PDT [-] Log opened. 2005/06/16 15:17 PDT [-] twistd 1.3.0rc1 (/usr/bin/python2.3 2.3.5) starting up 2005/06/16 15:17 PDT [-] reactor class: twisted.internet.default.SelectReactor 2005/06/16 15:17 PDT [-] Loading /usr/sbin/apt-proxy... 2005/06/16 15:17 PDT [-] Updating twisted's process module. 2005/06/16 15:17 PDT [-] No updating required. 2005/06/16 15:17 PDT [-] Loaded. 2005/06/16 15:17 PDT [-] apt_proxy.apt_proxy.Factory starting on 9999 2005/06/16 15:17 PDT [-] Starting factory <apt_proxy.apt_proxy.Factory instance at 0x404cac4c> 2005/06/16 15:17 PDT [-] set uid/gid 103/65534 2005/06/16 15:17 PDT [-] [debug] Verifying database: /var/cache/apt-proxy/.apt-proxy/db/access.db 2005/06/16 15:17 PDT [-] [debug] Opening database /var/cache/apt-proxy/.apt-proxy/db/access.db 2005/06/16 15:17 PDT [Channel,0,172.16.67.1] [debug] Headers: Host: 172.16.67.1:9999, Connection: keep-alive, User-Agent: Debian APT-HTTP/1.3 2005/06/16 15:17 PDT [Channel,0,172.16.67.1] [debug] Request: GET /main/dists/stable/main/binary-i386/Packages.gz 2005/06/16 15:17 PDT [Channel,0,172.16.67.1] [Fetcher.activate] (main) servers:4/main/dists/stable/main/binary-i386/Packages.gz 2005/06/16 15:17 PDT [Channel,0,172.16.67.1] [file_ok] check_cached: /var/cache/apt-proxy/main/dists/stable/main/binary-i386/Packages.gz 2005/06/16 15:17 PDT [Channel,0,172.16.67.1] [fetch_real] Using gzip/gunzip to get /var/cache/apt-proxy/main/dists/stable/main/binary-i386/Packages.gz 2005/06/16 15:17 PDT [Channel,0,172.16.67.1] [gzip] FetcherGzip request:/main/dists/stable/main/binary-i386/Packages.gz postconvert:0 2005/06/16 15:17 PDT [Channel,0,172.16.67.1] [Fetcher.activate] (main) servers:4/main/dists/stable/main/binary-i386/Packages.gz 2005/06/16 15:17 PDT [Channel,0,172.16.67.1] [Fetcher.activate] (main) servers:4/main/dists/stable/main/binary-i386/Packages 2005/06/16 15:17 PDT [Channel,0,172.16.67.1] [file_ok] check_cached: /var/cache/apt-proxy/main/dists/stable/main/binary-i386/Packages 2005/06/16 15:17 PDT [Channel,0,172.16.67.1] Unhandled error in Deferred: 2005/06/16 15:17 PDT [Channel,0,172.16.67.1] Traceback (most recent call last): File "/usr/lib/python2.3/site-packages/apt_proxy/apt_proxy.py", line 317, in __init__ self.activate(request) File "/usr/lib/python2.3/site-packages/apt_proxy/apt_proxy.py", line 867, in activate loop.fetch(serve_cached=0) File "/usr/lib/python2.3/site-packages/apt_proxy/apt_proxy.py", line 1454, in fetch (dummyFetcher, 0, running,), None) File "/usr/lib/python2.3/site-packages/twisted/internet/defer.py", line 205, in addCallbacks self._runCallbacks() --- <exception caught here> --- File "/usr/lib/python2.3/site-packages/twisted/internet/defer.py", line 338, in _runCallbacks self.result = callback(self.result, *args, **kw) File "/usr/lib/python2.3/site-packages/apt_proxy/apt_proxy.py", line 1414, in fetch_real fetcher_class = req.backendServer.fetcher exceptions.AttributeError: 'NoneType' object has no attribute 'fetcher' 2005/06/16 15:19 PDT [Channel,0,172.16.67.1] [Fetcher] Last request removed my /etc/apt/sources.list: deb http://172.16.67.1:9999/main stable main non-free contrib deb http://172.16.67.1:9999/non-US stable/non-US main non-free contrib deb http://172.16.67.1:9999/security stable/updates main non-free contrib my /etc/apt-proxy/apt-proxy-v2.conf (the rest is default) [DEFAULT] ;; All times are in seconds, but you can add a suffix ;; for minutes(m), hours(h) or days(d) ;; Server IP to listen on ;address = 192.168.0.254 address = 172.16.67.1 ;; Server port to listen on port = 9999 Versions: apt 0.5.28.6 apt-proxy 1.9.29 Hope it helps. Darek Kedra ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=112078&aid=1222275&group_id=12078 |
|
From: Chris H. <ha...@de...> - 2005-06-16 11:38:19
|
On Thursday 09 Jun 2005 21:35, Bram Mertens wrote: > /etc/apt-proxy/apt-proxy-v2.conf: > [debian-volatile] > backends =3D ftp://ftp2.de.debian.org/debian-volatile > I also tried: > backends =3D http://ftp2.de.debian.org/debian-volatile > > > But I keep getting 503 Service unavailable errors even though the file > does exist: That sounds to me like you did not restart apt-proxy after making the=20 configuration file updates. =A0Could that be your problem? Chris |
|
From: Bram M. <bra...@li...> - 2005-06-09 20:35:20
|
Chris Halls wrote: [...] > I would recommend you rename your backend to debian-volatile, since it is not > just clamassassin: > > [debian-volatile] > backends = ftp://ftp2.de.debian.org/debian-volatile > > That way, your sources.list line is more obvious that you are pointing at > debian-volatile, not a clamassassin repository: > > deb http://localhost:9999/debian-volatile etch/volatile main Thanks for the suggestion, I followed your instructions: sources.list: deb http://localhost:9999/debian-volatile etch/volatile main I also tried: deb http://localhost:9999/debian-volatile testing/volatile main and deb http://localhost:9999/debian-volatile volatile main /etc/apt-proxy/apt-proxy-v2.conf: [debian-volatile] backends = ftp://ftp2.de.debian.org/debian-volatile I also tried: backends = http://ftp2.de.debian.org/debian-volatile But I keep getting 503 Service unavailable errors even though the file does exist: http://ftp2.de.debian.org/debian-volatile/dists/testing/volatile/main/binary-i386/Packages.gz wget http://ftp2.de.debian.org/debian-volatile/dists/testing/volatile/main/binary-i386/Packages.gz is succesfull I even tried to copy this file to /var/lib/apt/lists/locahost... but without succes. I have returned to my old config for now but I'd like to be able to get this working... Thanks again for the suggestions. Bram -- # Mertens Bram "M8ram" <bra...@li...> Linux User #349737 # # debian testing kernel 2.6.8-1-686 i686 512MB RAM # # 22:08:01 up 76 days, 4:22, 6 users, load average: 0.32, 0.29, 0.12 # |
|
From: SourceForge.net <no...@so...> - 2005-06-09 17:21:11
|
Bugs item #1217563, was opened at 2005-06-09 16:13 Message generated for change (Comment added) made by haggai You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=112078&aid=1217563&group_id=12078 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Apt-proxy and http_proxy Initial Comment: Hi! I moved from Debian's Woody apt-proxy to Debian's Sarge apt-proxy. apt-proxy-v1tov2 converted my old apt-proxy.conf configuration file to apt-proxy-v2.conf new format. I usually use a HTTP Proxy server with user authentication to fetch packages from Debian repositories. wget works properly. In the new configuration file I use: http_proxy = http://nameuser:passworduser@httphost:hostport When I try to apt-get from a client, it hangs on client's side and later I receive "Connection failed". On server side I receive this error in the log file: 2005/06/09 15:56 CEST [Channel,0,10.26.226.231] [Fetcher.activate] (debian) servers:4/debian/dists/stable/main/binary-i386/Packages.gz 2005/06/09 15:56 CEST [Channel,0,10.26.226.231] Unhandled error in Deferred: 2005/06/09 15:56 CEST [Channel,0,10.26.226.231] Traceback (most recent call last): File "/usr/lib/python2.3/site-packages/twisted/protocols/http.py", line 557, in requestReceived self.process() File "/usr/lib/python2.3/site-packages/apt_proxy/apt_proxy.py", line 1375, in process self.fetch() File "/usr/lib/python2.3/site-packages/apt_proxy/apt_proxy.py", line 1454, in fetch (dummyFetcher, 0, running,), None) File "/usr/lib/python2.3/site-packages/twisted/internet/defer.py", line 205, in addCallbacks self._runCallbacks() --- <exception caught here> --- File "/usr/lib/python2.3/site-packages/twisted/internet/defer.py", line 338, in _runCallbacks self.result = callback(self.result, *args, **kw) File "/usr/lib/python2.3/site-packages/apt_proxy/apt_proxy.py", line 1422, in fetch_real fetcher = dummyFetcher.apEndTransfer(fetcher_class) File "/usr/lib/python2.3/site-packages/apt_proxy/apt_proxy.py", line 463, in apEndTransfer fetcher = fetcher_class(req) File "/usr/lib/python2.3/site-packages/apt_proxy/apt_proxy.py", line 317, in __init__ self.activate(request) File "/usr/lib/python2.3/site-packages/apt_proxy/apt_proxy.py", line 553, in activate (self.proxy_host, self.proxy_port) = request.factory.http_proxy.split(':') exceptions.ValueError: unpack list of wrong size Is it an authentication problem with Http proxy server? With the previous version it worked without problems. thank you in advance, riccardo ---------------------------------------------------------------------- >Comment By: Chris Halls (haggai) Date: 2005-06-09 19:21 Message: Logged In: YES user_id=161154 Hi it looks like you have this problem: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=309288 Do you have special characters (: or @) in the proxy password? Can you replace them with another special character as a workaround for the problem? Thanks Chris ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=112078&aid=1217563&group_id=12078 |
|
From: SourceForge.net <no...@so...> - 2005-06-09 14:13:21
|
Bugs item #1217563, was opened at 2005-06-09 07:13 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=112078&aid=1217563&group_id=12078 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Apt-proxy and http_proxy Initial Comment: Hi! I moved from Debian's Woody apt-proxy to Debian's Sarge apt-proxy. apt-proxy-v1tov2 converted my old apt-proxy.conf configuration file to apt-proxy-v2.conf new format. I usually use a HTTP Proxy server with user authentication to fetch packages from Debian repositories. wget works properly. In the new configuration file I use: http_proxy = http://nameuser:passworduser@httphost:hostport When I try to apt-get from a client, it hangs on client's side and later I receive "Connection failed". On server side I receive this error in the log file: 2005/06/09 15:56 CEST [Channel,0,10.26.226.231] [Fetcher.activate] (debian) servers:4/debian/dists/stable/main/binary-i386/Packages.gz 2005/06/09 15:56 CEST [Channel,0,10.26.226.231] Unhandled error in Deferred: 2005/06/09 15:56 CEST [Channel,0,10.26.226.231] Traceback (most recent call last): File "/usr/lib/python2.3/site-packages/twisted/protocols/http.py", line 557, in requestReceived self.process() File "/usr/lib/python2.3/site-packages/apt_proxy/apt_proxy.py", line 1375, in process self.fetch() File "/usr/lib/python2.3/site-packages/apt_proxy/apt_proxy.py", line 1454, in fetch (dummyFetcher, 0, running,), None) File "/usr/lib/python2.3/site-packages/twisted/internet/defer.py", line 205, in addCallbacks self._runCallbacks() --- <exception caught here> --- File "/usr/lib/python2.3/site-packages/twisted/internet/defer.py", line 338, in _runCallbacks self.result = callback(self.result, *args, **kw) File "/usr/lib/python2.3/site-packages/apt_proxy/apt_proxy.py", line 1422, in fetch_real fetcher = dummyFetcher.apEndTransfer(fetcher_class) File "/usr/lib/python2.3/site-packages/apt_proxy/apt_proxy.py", line 463, in apEndTransfer fetcher = fetcher_class(req) File "/usr/lib/python2.3/site-packages/apt_proxy/apt_proxy.py", line 317, in __init__ self.activate(request) File "/usr/lib/python2.3/site-packages/apt_proxy/apt_proxy.py", line 553, in activate (self.proxy_host, self.proxy_port) = request.factory.http_proxy.split(':') exceptions.ValueError: unpack list of wrong size Is it an authentication problem with Http proxy server? With the previous version it worked without problems. thank you in advance, riccardo ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=112078&aid=1217563&group_id=12078 |
|
From: Chris H. <ha...@de...> - 2005-06-09 10:34:57
|
Hi Bill, sorry for the long delay
On Friday 20 May 2005 15:05, Bill Moseley wrote:
> Another feature I would love is to be able to query apt-proxy and 1)
> show when a package was installed (and what packages were installed
> because of it) and 1) be able just see (and sort) by package
> installation date ("what were those three CMS packages I was testing
> out last week?").
With apt-proxy using twisted, it should be too difficult to generate extra web
pages, although the access to the databases needs to be cleaned up first -
there isn't any well documented set of access functions.
> Ah, thanks. Ok, trying.... No, still not working.
I agree, it's still not working :( It seems my existing install started
working after the fixes but when I tried on a completely new cache directory,
it didn't work either.
> How does the import work? Does it look at the file name, then try to
> find that file in Packages.gz (or related .db) and look up its path?
I'll try and explain the complete flow, starting from an empty cache:
1. A client requests a Packages[.gz] file for a given backend
[in apt-proxy daemon:]
2. The Packages file is downloaded
3. If it was Packages.gz, the file is uncompressed using gzip in the
background. This was the step I broke :)
4. The uncompressed Packages file is registered in the database found at
/var/cache/apt-proxy/.apt-proxy/backends/<backend name>/packages.db
[in apt-proxy-import:]
5. apt-proxy-import is started
6. for each .deb, a-p-i extracts the package name
7. for each backend, a-p-i extracts a list of Packages files from the database
8. the contents of each Packages file is read using python-apt
9. a-p-i looks in the python-apt cache for the package name
10. if the exact version is found in a Packages file, it copies the file there
11. otherwise if a package with the same name but a different version is
found, it will copy the file to the same path as the other version.
So, going back to your original question, it looks at the package name
embedded in the .deb, and tries to find that path in the Packages.gz.
I have added a command line option to specify the configuration file, to make
it easier to start a new a-p with an empty cache listening on a different
port, but it needs some cleaning up before it is released. In my debugging I
have established that step 8 is failing for some reason: The python-apt cache
ends up being empty. I'm not sure yet why this is happening.
Chris
|
|
From: Chris H. <ha...@de...> - 2005-06-09 09:53:22
|
On Wednesday 08 Jun 2005 19:50, Bram Mertens wrote: > Hi > > I have been running apt-proxy for a while now without problems. Now I > would like to add debian-volatile to my sources following the advice on > http://www.clamav.net/binary.html. > > The instructions on this page are for apt but I can't find how I should > adapt them for apt-proxy. > > In my /etc/apt-proxy/apt-proxy-v2.conf I had the following for ClamAV: > [clamassassin] > ;; clamassassin > backends = http://debian.wgdd.de/debian > > And in my /etc/apt/sources.list: > # get clamassassin > deb http://localhost:9999/clamassassin/ testing main contrib non-free The clamav.net page says you should use this sources.list line: deb http://ftp2.de.debian.org/debian-volatile sarge/volatile main You need to replace the URL in that example with one that points to your apt-proxy: deb http://localhost:9999/clamassassin etch/volatile main So that should work. However: > I have changed my apt-proxy-v2.conf to: > [clamassassin] > ;; clamassassin > backends = ftp://ftp2.de.debian.org/debian-volatile I would recommend you rename your backend to debian-volatile, since it is not just clamassassin: [debian-volatile] backends = ftp://ftp2.de.debian.org/debian-volatile That way, your sources.list line is more obvious that you are pointing at debian-volatile, not a clamassassin repository: deb http://localhost:9999/debian-volatile etch/volatile main Chris |
|
From: Erik C.J. L. <el...@dd...> - 2005-06-08 20:49:34
|
Erik C.J. Laan wrote: > Bram Mertens wrote: [snip] > Hi Bram, > > I have no experience with apt-proxy-v2 and its .conf, but this last line > looks wierd to me. If I understand it right you are saying these > packages in volatile can be found in testing. I think your sources.list > should read: > > deb http://localhost:9999/clamassassin/ volatile main contrib non-free > >> >> I have changed my apt-proxy-v2.conf to: >> [clamassassin] >> ;; clamassassin >> backends = ftp://ftp2.de.debian.org/debian-volatile >> ;http://debian.wgdd.de/debian >> >> But no matter what I put in my sources.list I get the following error >> when I run apt-get update: >> imladris:~# apt-get update >> [...] >> Err http://localhost testing/volatile/main Packages >> 404 Not Found >> Ign http://localhost testing/volatile/main Release >> Hit http://localhost testing/main Packages >> Hit http://localhost testing/main Release >> Failed to fetch >> http://localhost:9999/clamassassin/dists/testing/volatile/main/binary-i386/Packages.gz >> 404 Not Found >> Reading Package Lists... Done >> W: Couldn't stat source package list http://localhost >> testing/volatile/main Packages >> (/var/lib/apt/lists/localhost:9999_clamassassin_dists_testing_volatile_main_binary-i386_Packages) >> - stat (2 No such file or directory) >> W: You may want to run apt-get update to correct these problems >> E: Some index files failed to download, they have been ignored, or old >> ones used instead. >> >> I have tried several combinations etch/volatile, testing/volatile, >> testing, volatile, ... in my sources.list but none of them worked. Sorry, I wasn't awake enough to realised you had already tried this. Erik -- -------------------------------------------------------------------------- Erik C.J. Laan elaan at dds.nl Please reply below the message, please cut unrelevant pieces from a reply. -------------------------------------------------------------------------- |
|
From: Erik C.J. L. <el...@dd...> - 2005-06-08 20:45:34
|
Bram Mertens wrote: > Hi > > I have been running apt-proxy for a while now without problems. Now I > would like to add debian-volatile to my sources following the advice on > http://www.clamav.net/binary.html. > > The instructions on this page are for apt but I can't find how I should > adapt them for apt-proxy. > > In my /etc/apt-proxy/apt-proxy-v2.conf I had the following for ClamAV: > [clamassassin] > ;; clamassassin > backends = http://debian.wgdd.de/debian > > And in my /etc/apt/sources.list: > # get clamassassin > deb http://localhost:9999/clamassassin/ testing main contrib non-free Hi Bram, I have no experience with apt-proxy-v2 and its .conf, but this last line looks wierd to me. If I understand it right you are saying these packages in volatile can be found in testing. I think your sources.list should read: deb http://localhost:9999/clamassassin/ volatile main contrib non-free > > I have changed my apt-proxy-v2.conf to: > [clamassassin] > ;; clamassassin > backends = ftp://ftp2.de.debian.org/debian-volatile > ;http://debian.wgdd.de/debian > > But no matter what I put in my sources.list I get the following error > when I run apt-get update: > imladris:~# apt-get update > [...] > Err http://localhost testing/volatile/main Packages > 404 Not Found > Ign http://localhost testing/volatile/main Release > Hit http://localhost testing/main Packages > Hit http://localhost testing/main Release > Failed to fetch > http://localhost:9999/clamassassin/dists/testing/volatile/main/binary-i386/Packages.gz > 404 Not Found > Reading Package Lists... Done > W: Couldn't stat source package list http://localhost > testing/volatile/main Packages > (/var/lib/apt/lists/localhost:9999_clamassassin_dists_testing_volatile_main_binary-i386_Packages) > - stat (2 No such file or directory) > W: You may want to run apt-get update to correct these problems > E: Some index files failed to download, they have been ignored, or old > ones used instead. > > I have tried several combinations etch/volatile, testing/volatile, > testing, volatile, ... in my sources.list but none of them worked. > > Where can I find examples of such configuration? > > TIA > > Bram HTH, Erik. -- -------------------------------------------------------------------------- Erik C.J. Laan elaan at dds.nl Please reply below the message, please cut unrelevant pieces from a reply. -------------------------------------------------------------------------- |
|
From: Bram M. <bra...@li...> - 2005-06-08 18:50:52
|
Hi I have been running apt-proxy for a while now without problems. Now I would like to add debian-volatile to my sources following the advice on http://www.clamav.net/binary.html. The instructions on this page are for apt but I can't find how I should adapt them for apt-proxy. In my /etc/apt-proxy/apt-proxy-v2.conf I had the following for ClamAV: [clamassassin] ;; clamassassin backends = http://debian.wgdd.de/debian And in my /etc/apt/sources.list: # get clamassassin deb http://localhost:9999/clamassassin/ testing main contrib non-free I have changed my apt-proxy-v2.conf to: [clamassassin] ;; clamassassin backends = ftp://ftp2.de.debian.org/debian-volatile ;http://debian.wgdd.de/debian But no matter what I put in my sources.list I get the following error when I run apt-get update: imladris:~# apt-get update [...] Err http://localhost testing/volatile/main Packages 404 Not Found Ign http://localhost testing/volatile/main Release Hit http://localhost testing/main Packages Hit http://localhost testing/main Release Failed to fetch http://localhost:9999/clamassassin/dists/testing/volatile/main/binary-i386/Packages.gz 404 Not Found Reading Package Lists... Done W: Couldn't stat source package list http://localhost testing/volatile/main Packages (/var/lib/apt/lists/localhost:9999_clamassassin_dists_testing_volatile_main_binary-i386_Packages) - stat (2 No such file or directory) W: You may want to run apt-get update to correct these problems E: Some index files failed to download, they have been ignored, or old ones used instead. I have tried several combinations etch/volatile, testing/volatile, testing, volatile, ... in my sources.list but none of them worked. Where can I find examples of such configuration? TIA Bram -- # Mertens Bram "M8ram" <bra...@li...> Linux User #349737 # # debian testing kernel 2.6.8-1-686 i686 512MB RAM # # 20:42:01 up 75 days, 2:56, 11 users, load average: 0.61, 0.34, 0.28 # |
|
From: Christian K. <ch...@ck...> - 2005-05-20 16:00:35
|
Hello, [please CC: me, I'm not on this list] On Fri, May 20, 2005 at 08:31:02AM +0100, Chris Halls wrote: > On Saturday 09 Apr 2005 13:27, Christian Knoke wrote: > > > > But cache cleaning does not work. In my config I have > > > > --->--->--- > > cleanup_freq = 2h > > max_age = off > > max_versions = 2 > > max_versions was broken for a while, sorry. I have uploaded 1.9.30 to > unstable which fixes this; please upgrade. Thank you. I installed 1.9.30, but it still doesn't clean the cache (to tell from du). Here are the logs (with comments): 2005/05/20 12:07 CEST [-] Log opened. 2005/05/20 12:07 CEST [-] twistd 1.3.0rc1 (/usr/bin/python2.3 2.3.5) starting up 2005/05/20 12:07 CEST [-] reactor class: twisted.internet.default.SelectReactor 2005/05/20 12:07 CEST [-] Loading /usr/sbin/apt-proxy... 2005/05/20 12:07 CEST [-] Updating twisted's process module. 2005/05/20 12:07 CEST [-] No updating required. 2005/05/20 12:07 CEST [-] Loaded. 2005/05/20 12:07 CEST [-] apt_proxy.apt_proxy.Factory starting on 8086 2005/05/20 12:07 CEST [-] Starting factory <apt_proxy.apt_proxy.Factory instance at 0xb7b12c0c> 2005/05/20 12:07 CEST [-] set uid/gid 104/65534 2005/05/20 12:07 CEST [-] [debug] Verifying database: /var/cache/apt-proxy/.apt-proxy/db/access.db 2005/05/20 12:07 CEST [-] [db] /var/cache/apt-proxy/.apt-proxy/db/access.db could not be opened, moved to /var/cache/apt-proxy/.apt-proxy/db/access.db.error 2005/05/20 12:07 CEST [-] [db] Recreating /var/cache/apt-proxy/.apt-proxy/db/access.db 2005/05/20 12:07 CEST [-] [debug] Opening database /var/cache/apt-proxy/.apt-proxy/db/access.db 2005/05/20 12:07 CEST [-] [recycle] Adopting new file: /debian-non-US/dists/sarge/non-US/non-free/binary-i386/Packages.gz 2005/05/20 12:07 CEST [-] [recycle] Adopting new file: /debian-non-US/dists/sarge/non-US/non-free/binary-i386/Packages [8530 lines skipped] 2005/05/20 14:52 CEST [-] [debug] Doing periodic cleaning up 2005/05/20 14:52 CEST [-] [debug] Periodic cleaning done It doesn't seem to take any attempt to clean up. [8 lines skipped] 2005/05/20 14:52 CEST [-] [recycle] Adopting new file: /debian/pool/main/a/apmd/libapm1_3.2.1-4_i386.deb 2005/05/20 14:52 CEST [-] [recycle] Adopting new file: /debian/pool/main/a/apmd/libapm1_3.2.2-3_i386.deb 2005/05/20 14:52 CEST [-] [recycle] Adopting new file: /debian/pool/main/a/apmd/libapm1_3.2.2-2_i386.deb 2005/05/20 14:52 CEST [-] [recycle] Adopting new file: /debian/pool/main/a/apmd/libapm1_3.2.2-1_i386.deb 2005/05/20 14:52 CEST [-] [recycle] Adopting new file: /debian/pool/main/a/a2ps/a2ps_4.13b-4.3_i386.deb 2005/05/20 14:52 CEST [-] [recycle] Adopting new file: /debian/pool/main/a/apt/apt-utils_0.5.28.1_i386.deb 2005/05/20 14:52 CEST [-] [recycle] Adopting new file: /debian/pool/main/a/apt/apt-utils_0.5.25_i386.deb 2005/05/20 14:52 CEST [-] [recycle] Adopting new file: /debian/pool/main/a/apt/apt_0.5.25_i386.deb 2005/05/20 14:52 CEST [-] [recycle] Adopting new file: /debian/pool/main/a/apt/apt_0.5.28.6_i386.deb 2005/05/20 14:52 CEST [-] [recycle] Adopting new file: /debian/pool/main/a/apt/apt-utils_0.5.24_i386.deb 2005/05/20 14:52 CEST [-] [recycle] Adopting new file: /debian/pool/main/a/apt/apt_0.5.24_i386.deb 2005/05/20 14:52 CEST [-] [recycle] Adopting new file: /debian/pool/main/a/apt/apt_0.5.28.1_i386.deb 2005/05/20 14:52 CEST [-] [recycle] Adopting new file: /debian/pool/main/a/apt/apt-utils_0.5.23_i386.deb 2005/05/20 14:52 CEST [-] [recycle] Adopting new file: /debian/pool/main/a/apt/apt-utils_0.5.27_i386.deb 2005/05/20 14:52 CEST [-] [recycle] Adopting new file: /debian/pool/main/a/apt/apt_0.5.23_i386.deb 2005/05/20 14:53 CEST [-] [recycle] Adopting new file: /debian/pool/main/a/apt/apt_0.5.27_i386.deb 2005/05/20 14:53 CEST [-] [recycle] Adopting new file: /debian/pool/main/a/apt/apt-utils_0.5.28.6_i386.deb 2005/05/20 14:53 CEST [-] [recycle] Adopting new file: /debian/pool/main/a/apt/apt-utils_0.5.26_i386.deb 2005/05/20 14:53 CEST [-] [recycle] Adopting new file: /debian/pool/main/a/apt/apt_0.5.26_i386.deb 2005/05/20 14:53 CEST [-] [recycle] Adopting new file: /debian/pool/main/a/acl/libacl1_2.2.23-1_i386.deb 2005/05/20 14:53 CEST [-] [recycle] Adopting new file: /debian/pool/main/3/3dchess/3dchess_0.8.1-11_i386.deb 2005/05/20 15:07 CEST [-] [debug] Doing periodic cleaning up 2005/05/20 15:07 CEST [-] [debug] Periodic cleaning done [14 lines skipped] At this time, the cache was still the same size. I decided to restart apt-proxy. This seems to trigger some activity: 2005/05/20 17:05 CEST [-] Received SIGTERM, shutting down. 2005/05/20 17:05 CEST [-] (Port 8086 Closed) 2005/05/20 17:05 CEST [-] Stopping factory <apt_proxy.apt_proxy.Factory instance at 0xb7b12c0c> 2005/05/20 17:05 CEST [-] [debug] Verifying database: /var/cache/apt-proxy/.apt-proxy/db/update.db 2005/05/20 17:05 CEST [-] [debug] Opening database /var/cache/apt-proxy/.apt-proxy/db/update.db 2005/05/20 17:05 CEST [-] [debug] Verifying database: /var/cache/apt-proxy/.apt-proxy/db/packages.db 2005/05/20 17:05 CEST [-] [debug] Opening database /var/cache/apt-proxy/.apt-proxy/db/packages.db 2005/05/20 17:05 CEST [-] Main loop terminated. 2005/05/20 17:05 CEST [-] Server Shut Down. 2005/05/20 17:05 CEST [-] Log opened. 2005/05/20 17:05 CEST [-] twistd 1.3.0rc1 (/usr/bin/python2.3 2.3.5) starting up 2005/05/20 17:05 CEST [-] reactor class: twisted.internet.default.SelectReactor 2005/05/20 17:05 CEST [-] Loading /usr/sbin/apt-proxy... 2005/05/20 17:05 CEST [-] Updating twisted's process module. 2005/05/20 17:05 CEST [-] No updating required. 2005/05/20 17:05 CEST [-] Loaded. 2005/05/20 17:05 CEST [-] apt_proxy.apt_proxy.Factory starting on 8086 2005/05/20 17:05 CEST [-] Starting factory <apt_proxy.apt_proxy.Factory instance at 0xb7b12bec> 2005/05/20 17:05 CEST [-] set uid/gid 104/65534 2005/05/20 17:06 CEST [-] [debug] Verifying database: /var/cache/apt-proxy/.apt-proxy/db/access.db 2005/05/20 17:06 CEST [-] [debug] Opening database /var/cache/apt-proxy/.apt-proxy/db/access.db 2005/05/20 17:06 CEST [-] Received SIGTERM, shutting down. 2005/05/20 17:06 CEST [-] (Port 8086 Closed) 2005/05/20 17:06 CEST [-] Stopping factory <apt_proxy.apt_proxy.Factory instance at 0xb7b12bec> 2005/05/20 17:06 CEST [-] [db] ========================= 2005/05/20 17:06 CEST [-] [db] Dumping update times 2005/05/20 17:06 CEST [-] [db] ========================= 2005/05/20 17:06 CEST [-] [debug] Verifying database: /var/cache/apt-proxy/.apt-proxy/db/update.db 2005/05/20 17:06 CEST [-] [debug] Opening database /var/cache/apt-proxy/.apt-proxy/db/update.db 2005/05/20 17:06 CEST [-] [db] /debian/dists/sarge/contrib/binary-i386/Release: Fri May 20 11:49:53 2005 2005/05/20 17:06 CEST [-] [db] /debian/dists/sarge-proposed-updates/contrib/binary-i386/Release: Fri May 20 11:49:56 2005 [61 lines skipped] 2005/05/20 17:06 CEST [-] [db] ========================= 2005/05/20 17:06 CEST [-] [db] Dumping access times 2005/05/20 17:06 CEST [-] [db] ========================= 2005/05/20 17:06 CEST [-] [db] /security/dists/sarge/updates/contrib/binary-i386/Release: Fri May 20 12:02:12 2005 2005/05/20 17:06 CEST [-] [db] /security/pool/updates/main/x/xfree86/xfonts-base-transcoded_4.1.0-16woody3_all.deb: Mon Feb 16 10:00:00 2004 [.......] 2005/05/20 17:06 CEST [-] [db] /debian/pool/main/a/apmd/libapm1_3.2.1-4_i386.deb: Mon Feb 23 22:32:00 2004 [.......] 2005/05/20 17:06 CEST [-] [db] /debian/pool/main/a/apmd/libapm1_3.2.2-1_i386.deb: Sat May 1 05:17:00 2004 [........] 2005/05/20 17:06 CEST [-] [db] /debian/pool/main/a/apmd/libapm1_3.2.2-3_i386.deb: Sat May 14 18:41:47 2005 [........] 2005/05/20 17:06 CEST [-] [db] /debian/pool/main/a/apmd/libapm1_3.2.2-2_i386.deb: Mon Jun 7 15:47:00 2004 [.........] 2005/05/20 17:06 CEST [-] [db] ========================= 2005/05/20 17:06 CEST [-] [db] Dumping packages 2005/05/20 17:06 CEST [-] [db] ========================= 2005/05/20 17:06 CEST [-] [debug] Verifying database: /var/cache/apt-proxy/.apt-proxy/db/packages.db 2005/05/20 17:06 CEST [-] [debug] Opening database /var/cache/apt-proxy/.apt-proxy/db/packages.db 2005/05/20 17:06 CEST [-] [db] whois: 2005/05/20 17:06 CEST [-] [db] /debian/pool/main/w/whois/whois_4.7.2_i386.deb 2005/05/20 17:06 CEST [-] [db] /debian/pool/main/w/whois/whois_4.7.4_i386.deb [......] 2005/05/20 17:06 CEST [-] [db] libapm1: 2005/05/20 17:06 CEST [-] [db] /debian/pool/main/a/apmd/libapm1_3.2.2-3_i386.deb [.......] 2005/05/20 17:06 CEST [-] Main loop terminated. 2005/05/20 17:06 CEST [-] Server Shut Down. 2005/05/20 17:06 CEST [-] Log opened. 2005/05/20 17:06 CEST [-] twistd 1.3.0rc1 (/usr/bin/python2.3 2.3.5) starting up 2005/05/20 17:06 CEST [-] reactor class: twisted.internet.default.SelectReactor 2005/05/20 17:06 CEST [-] Loading /usr/sbin/apt-proxy... 2005/05/20 17:06 CEST [-] Updating twisted's process module. 2005/05/20 17:06 CEST [-] No updating required. 2005/05/20 17:06 CEST [-] Loaded. 2005/05/20 17:06 CEST [-] apt_proxy.apt_proxy.Factory starting on 8086 2005/05/20 17:06 CEST [-] Starting factory <apt_proxy.apt_proxy.Factory instance at 0xb7b12c0c> 2005/05/20 17:06 CEST [-] set uid/gid 104/65534 2005/05/20 17:06 CEST [-] [debug] Verifying database: /var/cache/apt-proxy/.apt-proxy/db/access.db 2005/05/20 17:06 CEST [-] [debug] Opening database /var/cache/apt-proxy/.apt-proxy/db/access.db 2005/05/20 17:16 CEST [-] [debug] Doing periodic cleaning up 2005/05/20 17:16 CEST [-] [debug] Periodic cleaning done At this point, the cache size still isn't reduced. There are still many packages with more than 2 versions, for instance: karl:~# ls -l /var/cache/apt-proxy/debian/pool/main/a/apmd/ total 152 -rw------- 1 aptproxy nogroup 57104 Mar 1 20:02 apmd_3.2.2-3_i386.deb -rw-r--r-- 1 aptproxy root 24060 Feb 23 2004 libapm1_3.2.1-4_i386.deb -rw-r--r-- 1 aptproxy root 24222 May 1 2004 libapm1_3.2.2-1_i386.deb -rw-r--r-- 1 aptproxy root 24274 Jun 7 2004 libapm1_3.2.2-2_i386.deb -rw------- 1 aptproxy nogroup 24366 Mar 1 20:02 libapm1_3.2.2-3_i386.deb The access rights and groups variation is due to my manual restore of the cache. However I don't know whether this is responsible for the failed cleaning. Christian -- Christian Knoke * * * http://cknoke.de * * * * * * * * * Ceterum censeo Microsoft esse dividendum. |
|
From: Bill M. <mo...@ha...> - 2005-05-20 14:05:24
|
On Fri, May 20, 2005 at 02:02:49PM +0100, Chris Halls wrote:
> One feature I'd like to do when I have time is to implement the prefetching in
> a-p itself. We already store last time a client requested each package, so
> it would be possible to automatically download updates of all packages that
> clients have been downloading recently. Now, I just need some time, or
> someone, to implement it :)
Of course, what I do that pre-fetch for is to do fast upgrades on sid,
which if you wait a week there's quite a few.
Another feature I would love is to be able to query apt-proxy and 1)
show when a package was installed (and what packages were installed
because of it) and 1) be able just see (and sort) by package
installation date ("what were those three CMS packages I was testing
out last week?").
> > Next, I can't see to import my existing .deb into the apt-proxy
> > cache. This seems to happen for every package:
>
> I accidentally broke apt-proxy-import and max_versions a while ago. 1.9.30
> fixes this, please upgrade.
Ah, thanks. Ok, trying.... No, still not working.
How does the import work? Does it look at the file name, then try to
find that file in Packages.gz (or related .db) and look up its path?
So for libdb1-compat:
2005/05/18 21:41 PDT [-] [import] libdb1-compat_2.1.3-7_i386.deb skipped - no suitable backend found
[...]
finds it in this Packages.gz
bumby:/var/cache/apt-proxy$ zgrep libdb1-compat ./debian/dists/unstable/main/binary-i386/Packages.gz
Depends: libdb1-compat
Package: libdb1-compat
Filename: pool/main/d/db1-compat/libdb1-compat_2.1.3-7_i386.deb
And then knows to place it in pool/main/d/db1-compat/?
Here's what's happening, and my two config files:
bumby:/home/moseley# apt-get install apt-proxy
bumby:/home/moseley# apt-get update
bumby:/home/moseley# apt-cache policy apt-proxy
apt-proxy:
Installed: 1.9.30
Candidate: 1.9.30
Version Table:
*** 1.9.30 0
500 http://bumby unstable/main Packages
100 /var/lib/dpkg/status
bumby:/home/moseley# apt-proxy-import -i /var/cache/apt/archives
Updating twisted's process module.
No updating required.
2005/05/20 06:57 PDT [-] Log opened.
2005/05/20 06:57 PDT [-] [apt_pkg] Loading Packages database for /var/cache/apt-proxy/.apt-proxy/backends/security
2005/05/20 06:57 PDT [-] [apt_pkg] Loading Packages database for /var/cache/apt-proxy/.apt-proxy/backends/marillat
2005/05/20 06:57 PDT [-] [apt_pkg] Loading Packages database for /var/cache/apt-proxy/.apt-proxy/backends/debian
2005/05/20 06:57 PDT [-] [apt_pkg] Loading Packages database for /var/cache/apt-proxy/.apt-proxy/backends/debian-non-US
2005/05/20 06:57 PDT [-] [import] libdb1-compat_2.1.3-7_i386.deb skipped - no suitable backend found
2005/05/20 06:57 PDT [-] [import] libtext-charwidth-perl_0.04-2_i386.deb skipped - no suitable backend found
[...]
:r /etc/apt-proxy/apt-proxy-v2/.conf
[DEFAULT]
;; All times are in seconds, but you can add a suffix
;; for minutes(m), hours(h) or days(d)
;; Server IP to listen on
;address = 192.168.0.254
;; Server port to listen on
port = 9999
;; Control files (Packages/Sources/Contents) refresh rate
;;
;; Minimum time between attempts to refresh a file
min_refresh_delay = 1h
;; Minimum age of a file before attempting an update (NOT YET IMPLEMENTED)
;min_age = 23h
;; Uncomment to make apt-proxy continue downloading even if all
;; clients disconnect. This is probably not a good idea on a
;; dial up line.
;; complete_clientless_downloads = 1
;; Debugging settings.
;; for all debug information use this:
;; debug = all:9
debug = all:4 db:0
;; Debugging remote python console
;; Do not enable in an untrusted environment
;telnet_port = 9998
;telnet_user = apt-proxy
;telnet_password = secret
;; Network timeout when retrieving from backend servers
timeout = 15
;; Cache directory for apt-proxy
cache_dir = /var/cache/apt-proxy
;; Use passive FTP? (default=on)
;passive_ftp = on
;; Use HTTP proxy?
;http_proxy = host:port
;; Enable HTTP pipelining within apt-proxy (for test purposes)
;disable_pipelining=0
;;--------------------------------------------------------------
;; Cache housekeeping
;; Time to perform periodic housekeeping:
;; - delete files that have not been accessed in max_age
;; - scan cache directories and update internal tables
cleanup_freq = 1d
;; Maximum age of files before deletion from the cache (seconds)
max_age = 120d
;; Maximum number of versions of a .deb to keep per distribution
max_versions = 3
;; Add HTTP backends dynamicaly if not already defined? (default=on)
;dynamic_backends = on
;;---------------------------------------------------------------
;;---------------------------------------------------------------
;; Backend servers
;;
;; Place each server in its own [section]
[debian]
;; The main Debian archive
;; You can override the default timeout like this:
;timeout = 30
;; Rsync server used to rsync the Packages file (NOT YET IMPLEMENTED)
;;rsyncpackages = rsync://ftp.de.debian.org/debian
;; Backend servers, in order of preference
backends =
http://ftp.us.debian.org/debian
http://ftp.de.debian.org/debian
http://ftp2.de.debian.org/debian
ftp://ftp.uk.debian.org/debian
[debian-non-US]
;; Debian debian-non-US archive
;timeout will be the global value
backends =
http://ftp.uk.debian.org/debian-non-US
http://ftp.de.debian.org/debian-non-US
ftp://ftp.uk.debian.org/debian
[security]
;; Debian security archive
backends =
http://security.debian.org/debian-security
http://ftp2.de.debian.org/debian-security
# --
[marillat]
backends =
ftp://ftp.nerim.net/debian-marillat
;;[ubuntu]
;; Ubuntu archive
;; backends = http://archive.ubuntu.com/ubuntu
;;[ubuntu-security]
;; Ubuntu security updates
;; backends = http://security.ubuntu.com/ubuntu
;[openoffice]
;; OpenOffice.org packages
;backends =
; http://ftp.freenet.de/pub/debian-openoffice
; http://ftp.sh.cvut.cz/MIRRORS/OpenOffice.deb
; http://borft.student.utwente.nl/debian
;[apt-proxy]
;; Apt-proxy new versions
;backends = http://apt-proxy.sourceforge.net/apt-proxy
;[backports.org]
;; backports.org
;backends = http://backports.org/debian
;[blackdown]
;; Blackdown Java
;backends = http://ftp.gwdg.de/pub/languages/java/linux/debian
;[debian-people]
;; people.debian.org
;backends = http://people.debian.org
;[emdebian]
;; The Emdebian project
;backends = http://emdebian.sourceforge.net/emdebian
;[rsync]
;; An example using an rsync server. This is not recommended
;; unless http is not available, becuause rsync is only more
;; efficient for transferring uncompressed files and puts much
;; more overhead on the server. See the rsyncpacakges parameter
;; for a way of rsyncing just the Packages files.
;backends = rsync://ftp.uk.debian.org/debian
:r /etc/apt/sources.list
# Normal Sid sources
#deb http://http.us.debian.org/debian/ unstable main non-free contrib
#deb-src http://http.us.debian.org/debian/ unstable main non-free contrib
# (apt-proxy)
deb http://bumby:9999/debian unstable main non-free contrib
deb-src http://bumby:9999/debian unstable main non-free contrib
# non-free
#deb http://non-us.debian.org/debian-non-US unstable/non-US main contrib non-free
#deb-src http://non-us.debian.org/debian-non-US unstable/non-US main contrib non-free
# (apt-proxy)
deb http://bumby:9999/debian-non-US unstable/non-US main contrib non-free
deb-src http://bumby:9999/debian-non-US unstable/non-US main contrib non-free
# Experimental
#deb http://http.us.debian.org/debian/ experimental main non-free contrib
#deb-src http://http.us.debian.org/debian/ experimental main non-free contrib
#deb http://non-us.debian.org/debian-non-US experimental/non-US main contrib non-free
#deb-src http://non-us.debian.org/debian-non-US experimental/non-US main contrib non-free
# For VLC (VideoLan.org)
#deb http://download.videolan.org/pub/videolan/debian $(ARCH)/
#deb-src http://download.videolan.org/pub/videolan/debian sources/
# http://www.musicpd.org/forum/viewtopic.php?t=170
#deb http://www.yhbt.net/normalperson/debian/MusicPD/releases ./
# transcode
#deb ftp://ftp.nerim.net/debian-marillat/ unstable main
# Cinelerra
deb http://www.kiberpipa.org/~minmax/cinelerra/builds/sid ./
deb-src http://www.kiberpipa.org/~minmax/cinelerra/builds/sid ./
# Updated slimp3
deb http://www.litux.org/debian unstable/
--
Bill Moseley
mo...@ha...
|
|
From: Chris H. <ha...@de...> - 2005-05-20 13:09:48
|
On Monday 16 May 2005 17:53, Bill Moseley wrote: > So, if the apt-proxy machine is also a client then there can be two > copies of the package -- one in /var/cache/apt/archives/ and the other > in /var/cache/apt-proxy/. Is this correct? Yes, correct > Before installing apt-proxy I would run this via cron: > > apt-get -qq update && \ > apt-get -qqd dist-upgrade && \ > apt-get -qq autoclean > > That keeps my Packages list up to date and pre-fetches packages, so > when I do a dist-upgrade the packages are ready to be installed. > > So, with using apt-proxy I can use the same method as above to > pre-fetch packages (via cron during the night), but to avoid storing > the packages in two locations on the same machine I would use "clean" > instead of "autoclean". Then later when I run a dist-upgrade I'll > fetch the packages from the apt-proxy cache. > > Is the above correct? Is that a typical usage for pre-fetching > packages? Yes, that would be fine. One feature I'd like to do when I have time is to implement the prefetching in a-p itself. We already store last time a client requested each package, so it would be possible to automatically download updates of all packages that clients have been downloading recently. Now, I just need some time, or someone, to implement it :) > Next, I can't see to import my existing .deb into the apt-proxy > cache. This seems to happen for every package: I accidentally broke apt-proxy-import and max_versions a while ago. 1.9.30 fixes this, please upgrade. Chris |
|
From: Chris H. <ha...@de...> - 2005-05-20 12:51:22
|
On Friday 20 May 2005 12:32, Dely Nicolas wrote: > ok so I'm waiting for this. > > Could you begin a password section about characters allow and not, > please? I don't have unlimited time for a-p and it would be better if I spend the time on fixing the problem. This can be found by trial and error by any user. Chris |
|
From: Dely N. <Nic...@th...> - 2005-05-20 11:33:30
|
On Fri, 2005-05-20 at 09:41 +0200, Chris Halls wrote:
> It looks like the password parsing routine is too simplistic. Bug
> #309288
> points out that '@' is not accepted either. We will fix this but we
> need to
> wait until the debian sarge freeze is over. Please work around this
> by using
> other characters. I think you'll find that there are other characters
> that
> work, eg !$^*, but I haven't tested it yet.
>
> In case you can read Python, here is the code that does the parsing:
>
> self.scheme, netloc, self.path, parameters, \
> query, fragment = urlparse.urlparse(uri)
>
> if '@' in netloc:
> auth, netloc = netloc.split('@')
> self.username, self.password = auth.split(':')
>
ok so I'm waiting for this.
Could you begin a password section about characters allow and not,
please?
|
|
From: Olivier B. <Oli...@pu...> - 2005-05-20 10:33:09
|
Hi Chris,
> Thanks Olivier for your message and patch. Filing a bug report to make s=
ure=20
> this doesn't get forgotten, thanks
You're welcome. Thanks for investigate it.
I'm happy to see you back on the apt-proxy list. :-)
Good day.
Olivier
--=20
Olivier Bornet | fran=E7ais : http://puck.ch/f
Swiss Ice Hockey Results | english : http://puck.ch/e
http://puck.ch/ | deutsch : http://puck.ch/g
Oli...@pu... | italiano : http://puck.ch/i
Get my PGP-key at http://puck.ch/pgp or at http://pgp.mit.edu/
|
|
From: Chris H. <ha...@de...> - 2005-05-20 08:00:09
|
Package: apt-proxy
Version: 1.9.28
Tags: patch
Thanks Olivier for your message and patch. Filing a bug report to make sur=
e=20
this doesn't get forgotten, thanks
Chris
=2D--------- Forwarded Message ----------
Subject: [Apt-proxy-users] Problem with apt-proxy, http backend and a new=20
firewall
Date: Tuesday 19 Apr 2005 17:05
=46rom: Olivier Bornet <Oli...@pu...>
To: apt...@li...
Hello all,
since Monday, we have a new firewall at work. And since Monday, we have
problems with apt-proxy. And it seems the problem is related to this new
firewall.
We have apt-proxy version 1.9.28 from debian testing distribution. All
http backend has stopped working, and "apt-get update" stops with a
timeout.
To isolate the problem, I have try to do (aptproxy is our apt-proxy):
wget http://aptproxy:9999/debian/dists/testing/Release
and it results of a timeout after about 1 minute:
HTTP request sent, awaiting response... 504 Gateway Time-out
17:56:08 ERROR 504: Gateway Time-out.
Here is the trace from the apt-proxy log file:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D
2005/04/19 17:43 CEST [Channel,3,192.33.221.75] [debug] Headers: User-Agent:
Wget/1.9.1, Host: aptproxy:9999, Accept: */*, Connection: Keep-Alive
2005/04/19 17:43 CEST [Channel,3,192.33.221.75] [debug] Request: GET
/debian/dists/testing/Release 2005/04/19 17:43 CEST
[Channel,3,192.33.221.75] [Fetcher.activate] (debian)
servers:1/debian/dists/testing/Release 2005/04/19 17:43 CEST
[Channel,3,192.33.221.75] [file_ok] check_cached:
/var/cache/apt-proxy/debian/dists/testing/Release 2005/04/19 17:43 CEST
[Channel,3,192.33.221.75] [fetch_real] Consulting server about
/var/cache/apt-proxy/debian/dists/testing/Release 2005/04/19 17:43 CEST
[Channel,3,192.33.221.75] [Fetcher.activate] (debian)
servers:1/debian/dists/testing/Release 2005/04/19 17:43 CEST
[Channel,3,192.33.221.75] Starting factory
<apt_proxy.apt_proxy.ClientFactory instance at 0x40a1722c> 2005/04/19 17:43
CEST [Uninitialized] [http_client]
GET:/ftp/mirror/debian/dists/testing/Release 2005/04/19 17:43 CEST
[Uninitialized] [http_client] host:mirror.switch.ch 2005/04/19 17:44 CEST
[FetcherHttp,client] [http_client] handleStatus 504 - Gateway Timeout
2005/04/19 17:44 CEST [FetcherHttp,client] [Fetcher] Response code: 504 -
None 2005/04/19 17:44 CEST [FetcherHttp,client] [debug] Received:
Content-Type text/html 2005/04/19 17:44 CEST [FetcherHttp,client] [debug]
Received: Content-Length 342 2005/04/19 17:44 CEST [FetcherHttp,client]
[debug] Received: Cache-Control no-cache 2005/04/19 17:44 CEST
[FetcherHttp,client] [debug] Received: Pragma no-cache 2005/04/19 17:44 CE=
ST
[FetcherHttp,client] [Fetcher] Finished receiving data, status:504
saveData:1 2005/04/19 17:44 CEST [FetcherHttp,client] [Fetcher] Last reque=
st
removed 2005/04/19 17:44 CEST [FetcherHttp,client] [Fetcher] telling the
transport to loseConnection 2005/04/19 17:44 CEST [FetcherHttp,client]
[http-client] XXX clientConnectionLost 2005/04/19 17:44 CEST
[FetcherHttp,client] Stopping factory <apt_proxy.apt_proxy.ClientFactory
instance at 0x40a1722c> 2005/04/19 17:44 CEST [Channel,3,192.33.221.75]
[debug] Client connection closed 2005/04/19 17:44 CEST
[Channel,3,192.33.221.75] Top 10:
2005/04/19 17:44 CEST [Channel,3,192.33.221.75] 84 Exception
2005/04/19 17:44 CEST [Channel,3,192.33.221.75] 32 DBError
2005/04/19 17:44 CEST [Channel,3,192.33.221.75] 28 DBError
2005/04/19 17:44 CEST [Channel,3,192.33.221.75] 24 StandardError
2005/04/19 17:44 CEST [Channel,3,192.33.221.75] 23 ClientFactory
2005/04/19 17:44 CEST [Channel,3,192.33.221.75] 22 FetcherHttp
2005/04/19 17:44 CEST [Channel,3,192.33.221.75] 22 Protocol
2005/04/19 17:44 CEST [Channel,3,192.33.221.75] 20 SelectReactor
2005/04/19 17:44 CEST [Channel,3,192.33.221.75] 17 Warning
2005/04/19 17:44 CEST [Channel,3,192.33.221.75] 17 ValueError
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D
Using netstat on aptproxy, I can see the connection to the real debian serv=
er
is established, so all seems to be OK.
The firewall is configured to accept everything from the inside network
to the outside.
The backend is:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D
[debian]
;; The main Debian archive
backends =3D
http://mirror.switch.ch/ftp/mirror/debian
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D
What is strange, is that we can do a wget on the real file from
aptproxy computer!!! This mean:
wget http://mirror.switch.ch/ftp/mirror/debian/dists/testing/Release
is working as expected...
The ftp backends are working OK. We have just problems with the http
backends.
We also have try to use a tunnel over ssh to bypass the firewall, and in
this condition, apt-proxy is working OK.
What can I test/do to find the problem ?
Thanks in advance for your help.
=2D--------- Forwarded Message ----------
Subject: Re: [Apt-proxy-users] Problem with apt-proxy, http backend and a n=
ew=20
firewall
Date: Wednesday 20 Apr 2005 11:28
=46rom: Olivier Bornet <Oli...@pu...>
To: apt...@li...
Hello,
On Tue, Apr 19, 2005 at 06:05:20PM +0200, Olivier Bornet wrote:
> since Monday, we have a new firewall at work. And since Monday, we have
> problems with apt-proxy. And it seems the problem is related to this new
> firewall.
I have found a work-around for my problem by patching apt_proxy.py. I
don't know if this is a valid correction or not, but with this
correction, all seems to be OK.
The patch add the hostname and port to the sendCommand(), even if we
don't go trough a proxy...
Anyway, this seem to be a problem with our "new" firewall. It seems to
block simple session like:
telnet the-outside-web-server 80
GET /
You need to do at least:
telnet the-outside-web-server 80
GET / HTTP/1.0
Host: the-outside-web-server
You can also make:
telnet the-outside-web-server 80
GET http://the-outside-web-server/
Don't know if this filtering by the firewall is some kind of
"security rule", or if this is not a correct HTTP protocol to say only
"GET /".
Thanks to look at the attached patch, and let me know if this is a
correct patch or not.
Good day.
Olivier
=2D-
Olivier Bornet | fran=E7ais : http://puck.ch/f
Swiss Ice Hockey Results | english : http://puck.ch/e
http://puck.ch/ | deutsch : http://puck.ch/g
Oli...@pu... | italiano : http://puck.ch/i
Get my PGP-key at http://puck.ch/pgp or at http://pgp.mit.edu/
=2D------------------------------------------------------
|
|
From: Chris H. <ha...@de...> - 2005-05-20 07:41:16
|
On Friday 15 Apr 2005 10:59, Dely Nicolas wrote:
> My
> password contains non alpha numeric characters '%' '#',
>
> What are the rules to set non alpha numeric characters in this config
> file?
Hi, thanks for your report.
It looks like the password parsing routine is too simplistic. Bug #309288
points out that '@' is not accepted either. We will fix this but we need to
wait until the debian sarge freeze is over. Please work around this by using
other characters. I think you'll find that there are other characters that
work, eg !$^*, but I haven't tested it yet.
In case you can read Python, here is the code that does the parsing:
self.scheme, netloc, self.path, parameters, \
query, fragment = urlparse.urlparse(uri)
if '@' in netloc:
auth, netloc = netloc.split('@')
self.username, self.password = auth.split(':')
Chris
|
