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: Chris H. <ha...@de...> - 2005-12-13 17:00:46
|
Hi On Thursday 10 Nov 2005 17:54, Micha wrote: > I notice libc6 is in directory 'glibc' and e2fslibs in 'e2fsprogs'...but > why ? How does the ap cache sorting work ? apt-proxy mirrors the debian archive structure - it does not sort packages itself. The directory name is taken from the source package - in this case, libc6 is built from the source package 'glibc'. You can see the source package name at bugs.debian.org/libc6 Chris |
From: Erik C.J. L. <el...@dd...> - 2005-12-13 14:29:52
|
Micha wrote: > Hi. > > I'm no more onlist, please cc to me directly. [snip] > To the topic. > I looked for vlc, the videolan project streamer/player, and found > their project site <http://www.videolan.org> features a debian package > repository. The provided path, > deb http://download.videolan.org/pub/videolan/debian sid main > is working. AFAICS anything's ok with the repository structure. > > So i made this entry into ap2 config: > > [videolan] > backends = > http://download.videolan.org/pub/videolan/debian > > ...and inserted a line into apt sources.list: > > deb http://localhost/videolan sid main ^^^^ I think you need to insert the portnumber here, so it looks like this: deb http://localhost:9999/videolan sid main (9999 is the default portnumber). Also, do you really what sid in there, or etch? HTH, Erik. |
From: Micha <ear...@gm...> - 2005-12-12 12:57:12
|
Hi, just made the regular daily update (well, this time after it was suspendet for some edays) and noticed ap's running very slow, with pauses between every download (which run at normal speed themwselves) and sometimes even within a single download. Parallel streaming is _not_ enabled in the config. After 60 packages or so i interrupted the update. Debug level was all:9 so i got some logging (last lines): (...) 2005/12/12 13:14 CET [FetcherHttp,client] [db] openssh-server: 2005/12/12 13:14 CET [FetcherHttp,client] [db] /debian/pool/main/o/openssh/openssh-server_4.2p1-5_i386.deb 2005/12/12 13:14 CET [FetcherHttp,client] [db] gstreamer0.8-ffmpeg: 2005/12/12 13:14 CET [FetcherHttp,client] [db] /debian/pool/main/g/gst-ffmpeg/gstreamer0.8-ffmpeg_0.8.5-2_i386.deb 2005/12/12 13:14 CET [FetcherHttp,client] [db] /debian/pool/main/g/gst-ffmpeg/gstreamer0.8-ffmpeg_0.8.7-4_i386.deb 2005/12/12 13:14 CET [FetcherHttp,client] [db] binutils: 2005/12/12 13:14 CET [FetcherHttp,client] [db] /debian/pool/main/b/binutils/binutils_2.15-6_i386.deb 2005/12/12 13:14 CET [FetcherHttp,client] [db] /debian/pool/main/b/binutils/binutils_2.16.1-2_i386.deb 2005/12/12 13:14 CET [FetcherHttp,client] [db] /debian/pool/main/b/binutils/binutils_2.16.1cvs20051117-1_i386.deb 2005/12/12 13:14 CET [FetcherHttp,client] [Fetcher] Last request removed 2005/12/12 13:14 CET [FetcherHttp,client] [http-client] XXX clientConnectionLost 2005/12/12 13:14 CET [FetcherHttp,client] Stopping factory <apt_proxy.apt_proxy.ClientFactory instance at 0xb6a5d88c> 2005/12/12 13:14 CET [Channel,73,127.0.0.1] [debug] Client connection closed 2005/12/12 13:14 CET [Channel,73,127.0.0.1] Top 10: 2005/12/12 13:14 CET [Channel,73,127.0.0.1] 282 WeakKeyDictionary 2005/12/12 13:14 CET [Channel,73,127.0.0.1] 94 Exception 2005/12/12 13:14 CET [Channel,73,127.0.0.1] 32 DBError 2005/12/12 13:14 CET [Channel,73,127.0.0.1] 31 SelectReactor 2005/12/12 13:14 CET [Channel,73,127.0.0.1] 28 ProtocolToConsumerAdapter 2005/12/12 13:14 CET [Channel,73,127.0.0.1] 28 DBError 2005/12/12 13:14 CET [Channel,73,127.0.0.1] 26 Protocol 2005/12/12 13:14 CET [Channel,73,127.0.0.1] 24 StandardError 2005/12/12 13:14 CET [Channel,73,127.0.0.1] 17 Warning 2005/12/12 13:14 CET [Channel,73,127.0.0.1] 17 ValueError Apparently, ap2 was busy with recreating (? or whatever) the database in the background. This is only an AMD K6 (500mhz) with 512MB, but anything is fully optimized and it's rarely grunting under load. But i suspect a bottleneck somewhere. I set debug = all:9 db:0, restarted ap, and bingo it worked fast as usual again. After some 20 packages i interrupted the update agian, and here are the last logline: (...) 2005/12/12 13:28 CET [Channel,28,127.0.0.1] [Fetcher.activate] (debian) servers:1/debian/pool/main/d/dbus/python2.3-dbus_0.23.4-8_i386.deb 2005/12/12 13:28 CET [Channel,28,127.0.0.1] Starting factory <apt_proxy.apt_proxy.ClientFactory instance at 0xb6adc1cc> 2005/12/12 13:28 CET [Uninitialized] [http_client] GET:/debian/pool/main/d/dbus/python2.3-dbus_0.23.4-8_i386.deb 2005/12/12 13:28 CET [Uninitialized] [http_client] host:ftp2.de.debian.org 2005/12/12 13:28 CET [FetcherHttp,client] [http_client] handleStatus 200 - OK 2005/12/12 13:28 CET [FetcherHttp,client] [debug] Received: Date Mon, 12 Dec 2005 12:28:56 GMT 2005/12/12 13:28 CET [FetcherHttp,client] [debug] Received: Server Apache/2.0.54 (Debian GNU/Linux) 2005/12/12 13:28 CET [FetcherHttp,client] [debug] Received: Last-Modified Mon, 28 Nov 2005 22:02:07 GMT 2005/12/12 13:28 CET [FetcherHttp,client] [debug] Received: ETag "165c084-23470-410515c0" 2005/12/12 13:28 CET [FetcherHttp,client] [debug] Received: Accept-Ranges bytes 2005/12/12 13:28 CET [FetcherHttp,client] [debug] Received: Content-Length 144496 2005/12/12 13:28 CET [FetcherHttp,client] [debug] Received: Connection close 2005/12/12 13:28 CET [FetcherHttp,client] [debug] Received: Content-Type application/x-debian-package 2005/12/12 13:28 CET [Channel,28,127.0.0.1] [Fetcher] Last request removed 2005/12/12 13:28 CET [Channel,28,127.0.0.1] [debug] Client connection closed 2005/12/12 13:28 CET [Channel,28,127.0.0.1] Top 10: 2005/12/12 13:28 CET [Channel,28,127.0.0.1] 274 WeakKeyDictionary 2005/12/12 13:28 CET [Channel,28,127.0.0.1] 93 Exception 2005/12/12 13:28 CET [Channel,28,127.0.0.1] 32 DBError 2005/12/12 13:28 CET [Channel,28,127.0.0.1] 28 DBError 2005/12/12 13:28 CET [Channel,28,127.0.0.1] 27 SelectReactor 2005/12/12 13:28 CET [Channel,28,127.0.0.1] 26 Protocol 2005/12/12 13:28 CET [Channel,28,127.0.0.1] 24 StandardError 2005/12/12 13:28 CET [Channel,28,127.0.0.1] 24 ProtocolToConsumerAdapter 2005/12/12 13:28 CET [Channel,28,127.0.0.1] 17 Warning 2005/12/12 13:28 CET [Channel,28,127.0.0.1] 17 ValueError 2005/12/12 13:28 CET [FetcherHttp,client] [Fetcher] Finished receiving data, status:200 saveData:1 2005/12/12 13:29 CET [FetcherHttp,client] [max_versions] [['0.23.4-8', '/debian/pool/main/d/dbus/python2.3-dbus_0.23.4-8_i386.deb'], ['0.23.4-7', '/debian/pool/main/d/dbus/python2.3-dbus_0.23.4-7_i386.deb'], ['0.23.4-1', '/debian/pool/main/d/dbus/python2.3-dbus_0.23.4-1_i386.deb']] 2005/12/12 13:29 CET [FetcherHttp,client] [apt_pkg] No Packages files available for cyril backend 2005/12/12 13:29 CET [FetcherHttp,client] [apt_pkg] No Packages files available for java backend 2005/12/12 13:29 CET [FetcherHttp,client] [apt_pkg] No Packages files available for videolan backend 2005/12/12 13:29 CET [FetcherHttp,client] [max_versions] Current Versions: [('0.23.4-1', 'debian/pool/main/d/dbus/python2.3-dbus_0.23.4-1_i386.deb')] 2005/12/12 13:29 CET [FetcherHttp,client] [max_versions] Deleting /var/cache/apt-proxy//debian/pool/main/d/dbus/python2.3-dbus_0.23.4-7_i386.deb 2005/12/12 13:29 CET [FetcherHttp,client] [max_versions] reset at debian/pool/main/d/dbus/python2.3-dbus_0.23.4-1_i386.deb 2005/12/12 13:29 CET [FetcherHttp,client] [http-client] XXX clientConnectionLost 2005/12/12 13:29 CET [FetcherHttp,client] Stopping factory <apt_proxy.apt_proxy.ClientFactory instance at 0xb6adc1cc> But was the database process also running time ? I didn't know how to determine that. So i tried with debug = all:9 again to see if it would run slow again. I couldn't see any database activity this time, it just said, 2005/12/12 13:44 CET [-] [debug] Verifying database: /var/cache/apt-proxy/.apt-proxy/db/access.db 2005/12/12 13:44 CET [-] [debug] Opening database /var/cache/apt-proxy/.apt-proxy/db/access.db and that's all. But hey, the database activity started immediately again when the update continued again ! Like shown above, it went through all kind of packages which are completely unrelated to the actual update. And again the download/serving was heavily disrupted. The last loglines until finishing were: 2005/12/12 13:50 CET [FetcherHttp,client] [db] gstreamer0.8-ffmpeg: 2005/12/12 13:50 CET [FetcherHttp,client] [db] /debian/pool/main/g/gst-ffmpeg/gstreamer0.8-ffmpeg_0.8.5-2_i386.deb 2005/12/12 13:50 CET [FetcherHttp,client] [db] /debian/pool/main/g/gst-ffmpeg/gstreamer0.8-ffmpeg_0.8.7-4_i386.deb 2005/12/12 13:50 CET [FetcherHttp,client] [db] binutils: 2005/12/12 13:50 CET [FetcherHttp,client] [db] /debian/pool/main/b/binutils/binutils_2.15-6_i386.deb 2005/12/12 13:50 CET [FetcherHttp,client] [db] /debian/pool/main/b/binutils/binutils_2.16.1-2_i386.deb 2005/12/12 13:50 CET [FetcherHttp,client] [db] /debian/pool/main/b/binutils/binutils_2.16.1cvs20051117-1_i386.deb 2005/12/12 13:50 CET [FetcherHttp,client] [Fetcher] Last request removed 2005/12/12 13:50 CET [FetcherHttp,client] [http-client] XXX clientConnectionLost 2005/12/12 13:50 CET [FetcherHttp,client] Stopping factory <apt_proxy.apt_proxy.ClientFactory instance at 0xb5831e6c> 2005/12/12 13:50 CET [Channel,14,127.0.0.1] [debug] Client connection closed 2005/12/12 13:50 CET [Channel,14,127.0.0.1] Top 10: 2005/12/12 13:50 CET [Channel,14,127.0.0.1] 265 WeakKeyDictionary 2005/12/12 13:50 CET [Channel,14,127.0.0.1] 93 Exception 2005/12/12 13:50 CET [Channel,14,127.0.0.1] 41 SelectReactor 2005/12/12 13:50 CET [Channel,14,127.0.0.1] 32 DBError 2005/12/12 13:50 CET [Channel,14,127.0.0.1] 28 DBError 2005/12/12 13:50 CET [Channel,14,127.0.0.1] 26 Protocol 2005/12/12 13:50 CET [Channel,14,127.0.0.1] 24 StandardError 2005/12/12 13:50 CET [Channel,14,127.0.0.1] 20 DelayedCall 2005/12/12 13:50 CET [Channel,14,127.0.0.1] 20 ProtocolToConsumerAdapter 2005/12/12 13:50 CET [Channel,14,127.0.0.1] 17 Warning I wonder if the db debug level triggers a whole db lookup which somehow's using up rather much resources (both hd and cpu) ? This is ap 19.x, debian testing/unstable, kernel 2.6.13 with a low-latency-desktop kernel (*) HTH, micha *) The respective description of the kernel source is, CONFIG_PREEMPT: This option reduces the latency of the kernel by making all kernel code (that is not executing in a critical section) preemptible. This allows reaction to interactive events by permitting a low priority process to be preempted involuntarily even if it is in kernel mode executing a system call and would otherwise not be about to reach a natural preemption point. This allows applications to run more 'smoothly' even when the system is under load, at the cost of slighly lower throughput and a slight runtime overhead to kernel code. Select this if you are building a kernel for a desktop or embedded system with latency requirements in the milliseconds range. |
From: Micha <ear...@gm...> - 2005-12-10 21:42:48
|
Hi. I'm no more onlist, please cc to me directly. First of all, i run a.p.2 for some year(s) now and through several upgrades (even from ppp dialup to ppoe ADSL) it worked well enough. Since i'm on a ADSL flatrate now i don't really need ap2, strictly. However, i like the concept, and thus like to run the software just to help it improve. It's only a small homenet here, about 6 machines. To the topic. I looked for vlc, the videolan project streamer/player, and found their project site <http://www.videolan.org> features a debian package repository. The provided path, deb http://download.videolan.org/pub/videolan/debian sid main is working. AFAICS anything's ok with the repository structure. So i made this entry into ap2 config: [videolan] backends =3D=20 http://download.videolan.org/pub/videolan/debian ...and inserted a line into apt sources.list: deb http://localhost/videolan sid main and that just doesn't work. Aptitude reports, "Couldn't stat...(barf)... error 404" which is the tpyical error report for pathes that couldn't be found on the server. In the ap log i found *nothing* at all about any requested URLs ! I think there should be at least a single line about it by default, anyway ? In the config, i set debug =3D all:4 db:0 but that didn't change anything. (ok, need to try all:9 next) This is ap version 1.9.32, on debian etch (testing). In the ap log there are some python2.3 errors but i guess they are not critical since it always worked, anyway. =B0 /\/ |
From: David R. <dr...@ry...> - 2005-12-07 14:23:54
|
Hi there, I'm running a small group of servers and apt-proxy looks just what I need for cutting down on downloading. To get things started I want to use the standard Debian sarge 3.1 release on a DVD as a source of packages. Just as an experiment I have commented out the http servers in the [debian] list of backend servers in apt-proxy-v2.conf, and inserted 'file:///media/cdrom sarge main', which normally works for my setup. For the apt clients I use 'deb http://192.168.0.1:9999/debian/ sarge main contrib non-free'. The apt-proxy log file gets quite excited, but it takes a bit of understanding and I'm not there yet. Before I waste any time here I wonder if someone could let me know whether my hope of using a cdrom as input is a reasonable one.. TIA, David R. |
From: SourceForge.net <no...@so...> - 2005-11-24 00:25:13
|
Bugs item #1223254, was opened at 2005-06-18 17:21 Message generated for change (Comment added) made by cbz 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: chris (cbz) Date: 2005-11-24 00:25 Message: Logged In: YES user_id=24312 Additionally, the other message printed out repeatedly is: No Packages files available for %s backend ---------------------------------------------------------------------- Comment By: chris (cbz) Date: 2005-11-24 00:17 Message: Logged In: YES user_id=24312 This is still a problem as of version 1.9.32 of apt-proxy. From a brief look at the problem, when 'import_file' in packages.py is reached, the value of 'paths' returned by: try: paths = get_mirror_path(factory, dir+'/'+file) except SystemError: log.msg(file + ' skipped - wrong format or corrupted', 'import') return is the empty array. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2005-06-18 17: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-11-24 00:17:51
|
Bugs item #1223254, was opened at 2005-06-18 17:21 Message generated for change (Comment added) made by cbz 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: chris (cbz) Date: 2005-11-24 00:17 Message: Logged In: YES user_id=24312 This is still a problem as of version 1.9.32 of apt-proxy. From a brief look at the problem, when 'import_file' in packages.py is reached, the value of 'paths' returned by: try: paths = get_mirror_path(factory, dir+'/'+file) except SystemError: log.msg(file + ' skipped - wrong format or corrupted', 'import') return is the empty array. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2005-06-18 17: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: Micha <ear...@gm...> - 2005-11-10 17:54:59
|
Hello, I notice libc6 is in directory 'glibc' and e2fslibs in 'e2fsprogs'...but why ? How does the ap cache sorting work ? This is version 2, release 1.9.32, on Debian Testing. This is the directory structure of /var/cache/apt-proxy: ./.apt-proxy ./.apt-proxy/db ./.apt-proxy/backends ./.apt-proxy/backends/ubuntu-security ./.apt-proxy/backends/security ./.apt-proxy/backends/ubuntu ./.apt-proxy/backends/debian ./.apt-proxy/backends/debian-non-US ./.apt-proxy/backends/java ./debian ./debian/dists ./debian/dists/stable ./debian/dists/testing ./debian/pool ./debian/pool/main ./debian/pool/non-free ./debian/pool/contrib ./security ./security/dists ./security/dists/stable ./security/dists/testing ./security/pool ./security/pool/updates ./java ./java/dists ./java/dists/sarge ./java/pool ./java/pool/non-free |
From: SourceForge.net <no...@so...> - 2005-10-19 23:29:34
|
Bugs item #1332714, was opened at 2005-10-19 16:29 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=1332714&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: http backend with basic authentication Initial Comment: It seems that apt-proxy in the current sarge stable version does not support http basic authentication for the backends. here is an easy patch that could fix that, in the hope it could help anybody. -Tim K --- apt_proxy.py.orig 2005-10-20 00:41:58.000000000 +0200 +++ apt_proxy.py 2005-10-20 01:20:05.000000000 +0200 @@ -26,6 +26,7 @@ import time import string import packages +import base64 from twisted.python.failure import Failure import memleak from twisted.internet import error @@ -583,9 +584,13 @@ + self.request.backendServer.host + ":" + str(self.request.backendServer.port) + "/" + self.request.backendServer.path + "/" + self.request.backend_uri) - + self.sendHeader('host', self.request.backendServer.host) + # if we have a username send basic authentication to the server + if self.request.backendServer.username: + self.sendHeader('Authorization', 'Basic ' + base64.encodestring (self.request.backendServer.username+':'+self.request.ba ckendServer.password)) + if self.local_mtime != None: datetime = http.datetimeToString (self.local_mtime) self.sendHeader('if-modified-since', datetime) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=112078&aid=1332714&group_id=12078 |
From: Remco J. <R....@od...> - 2005-09-24 10:14:13
|
Hi list, I have installed apt-proxy on my Debian Sarge server using apt-get. I the= n changed /etc/apt/sources.list of that same server to use the apt-proxy. Next I ran 'apt-get update' in a shell. Everything went fine untill the update script wanted to download the non-free Packages file. It kept 'waiting for headers' and eventually timed out. In /var/log/apt-proxy.log I found the following lines: 2005/09/24 11:18 CEST [Channel,4,10.0.0.1] [debug] Headers: Host: geert:9999, Connection: keep-alive, User-Agent: Debian APT-HTTP/1.3 2005/09/24 11:18 CEST [Channel,4,10.0.0.1] [debug] Request: GET /debian/dists/sarge/non-free/binary-i386/Packages.gz 2005/09/24 11:18 CEST [Channel,4,10.0.0.1] Starting factory <apt_proxy.apt_proxy.ClientFactory instance at 0x406f38ec> 2005/09/24 11:18 CEST [FetcherHttp,client] [apt_pkg] REGISTERING PACKAGE:/debian/dists/sarge/contrib/binary-i386/Release 2005/09/24 11:18 CEST [FetcherHttp,client] Stopping factory <apt_proxy.apt_proxy.ClientFactory instance at 0x406dda2c> 2005/09/24 11:20 CEST [Channel,4,10.0.0.1] [debug] Client connection clos= ed 2005/09/24 11:20 CEST [Channel,5,10.0.0.1] [debug] Headers: Host: geert:9999, Connection: keep-alive, User-Agent: Debian APT-HTTP/1.3 2005/09/24 11:20 CEST [Channel,5,10.0.0.1] [debug] Request: GET /debian/dists/sarge/non-free/binary-i386/Packages.gz 2005/09/24 11:20 CEST [FetcherHttp,client] Traceback (most recent call la= st): File "/usr/lib/python2.3/site-packages/twisted/application/app.py", line 95, in runReactorWithLogging reactor.run() File "/usr/lib/python2.3/site-packages/twisted/internet/default.py", line 126, in run self.mainLoop() File "/usr/lib/python2.3/site-packages/twisted/internet/default.py", line 137, in mainLoop self.doIteration(t) File "/usr/lib/python2.3/site-packages/twisted/internet/default.py", line 526, in doSelect _logrun(selectable, _drdw, selectable, method, dict) --- <exception caught here> --- File "/usr/lib/python2.3/site-packages/twisted/python/log.py", line 65, in callWithLogger callWithContext({"system": lp}, func, *args, **kw) File "/usr/lib/python2.3/site-packages/twisted/python/log.py", line 52, in callWithContext return context.call({ILogContext: newCtx}, func, *args, **kw) File "/usr/lib/python2.3/site-packages/twisted/python/context.py", line 43, in callWithContext return func(*args,**kw) File "/usr/lib/python2.3/site-packages/twisted/internet/default.py", line 549, in _doReadOrWrite selectable.connectionLost(f) File "/usr/lib/python2.3/site-packages/twisted/internet/tcp.py"= , line 447, in connectionLost Connection.connectionLost(self, reason) File "/usr/lib/python2.3/site-packages/twisted/internet/tcp.py"= , line 294, in connectionLost protocol.connectionLost(reason) File "/usr/lib/python2.3/site-packages/twisted/protocols/http.py", line 361, in connectionLost self.handleResponseEnd() File "/usr/lib/python2.3/site-packages/twisted/protocols/http.py", line 367, in handleResponseEnd self.handleResponse(b) File "/usr/lib/python2.3/site-packages/apt_proxy/apt_proxy.py", line 628, in handleResponse if self.http_status =3D=3D http.NOT_MODIFIED: exceptions.AttributeError: FetcherHttp instance has no attribute 'http_status' Does anyone know how to fix this? Any help would be appreciated. Remco |
From: SourceForge.net <no...@so...> - 2005-09-19 07:23:33
|
Bugs item #1295094, was opened at 2005-09-19 19:23 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=1295094&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: Lee Begg (llnz) Assigned to: Nobody/Anonymous (nobody) Summary: apt-proxy-import fails to read Packages.bz2 files Initial Comment: From the log: 2005/09/19 18:08 NZST [-] [apt_pkg] No Packages files available for debian-amd64 backend From the filesystem: sleep:/home/aptproxy/debian-amd64/dists/sid/main/binary-amd64# ls Packages.bz2 Background: Recent (sid) apt-get's fetch Packages.bz2 instead of Packages.gz Apt-proxy needs to read the Packages.bz2 files. When it doesn't, apt-proxy-import fails to find any package file and can not import existing debs. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=112078&aid=1295094&group_id=12078 |
From: Jay S. <me...@he...> - 2005-09-12 00:21:17
|
Perhaps you should verify what's up, first: > > (login to a shell as root) > cd /var/lib/apt/lists > ls -al > > -> Is there an (empty) directory like, exactly, except the date: > drwxr-xr-x 2 root root 4,0K 2005-09-06 23:24 partial/ > > -> If not, try to create the repective dir like this: > (but this should never be necessary anyway) > mkdir -m 755 partial Thanks Micha, Creating the "partial" directory solved my problem. I don't know why it was missing in the first place Thanks again Jay |
From: Micha <ear...@gm...> - 2005-09-11 15:48:32
|
Jay Strauss <me...@he...>: > I don't have an update command: This wasn't meant to be a command. I am sorry.=20 I was thinking of any of the GUI package manager. If you like to use apt-get, it's just 'apt-get update' , like you did: > iron:~# apt-get update > E: Lists directory /var/lib/apt/lists/partial is missing. Perhaps you should verify what's up, first: (login to a shell as root) cd /var/lib/apt/lists ls -al -> Is there an (empty) directory like, exactly, except the date: drwxr-xr-x 2 root root 4,0K 2005-09-06 23:24 partial/ -> If not, try to create the repective dir like this: (but this should never be necessary anyway) mkdir -m 755 partial=20 ...and run the update command again. =20 btw.=20 =B0 /\/ |
From: Jay S. <me...@he...> - 2005-09-11 14:06:54
|
Micha wrote: > > Try 'update package list' as root. > If the network has latency, try more than once. > If it still does not work, set debug level higher (config) and also look at > other logfiles, like syslog and auth. I don't have an update command: jstrauss@ubuntu:~$ ssh root@fe Password: iron:~# update package list -bash: update: command not found iron:~# apt-get update package list E: The update command takes no arguments iron:~# apt-get update E: Lists directory /var/lib/apt/lists/partial is missing. Thanks Jay |
From: Micha <ear...@gm...> - 2005-09-11 11:19:36
|
Try 'update package list' as root. If the network has latency, try more than once. If it still does not work, set debug level higher (config) and also look at other logfiles, like syslog and auth.=20 =B0 /\/ |
From: Jay S. <me...@he...> - 2005-09-11 04:09:18
|
Hi, On 192.168.1.26 "iron" I run apt-proxy. From other boxes on my network I can point and use my apt-proxy server. But, from "iron" I can't access apt-proxy. I get the following: iron:~# aptitude update Reading Package Lists... Done Building Dependency Tree Reading extended state information Initializing package states... Done Reading task descriptions... Done Reading Package Lists... Done Building Dependency Tree Reading extended state information Initializing package states... Done Reading task descriptions... Done W: Couldn't stat source package list http://192.168.1.26 stable/main Packages (/var/lib/apt/lists/192.168.1.26:9999_debian_dists_stable_main_binary-i386_Packages) - stat (2 No such file or directory) W: Couldn't stat source package list http://security.debian.org stable/updates/main Packages (/var/lib/apt/lists/security.debian.org_dists_stable_updates_main_binary-i386_Packages) - stat (2 No such file or directory) W: You may want to update the package lists to correct these missing files W: Warning: could not lock the cache file. Opening in read-only mode below is: iron:~# cat /etc/apt/sources.list deb http://192.168.1.26:9999/debian stable main deb-src http://192.168.1.26:9999/debian stable main deb http://security.debian.org/ stable/updates main nothing particular is showing up in the /var/log/apt-proxy.log any suggestions would be great Thanks Jay |
From: SourceForge.net <no...@so...> - 2005-08-04 20:47:20
|
Feature Requests item #1252202, was opened at 2005-08-04 22:47 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=362078&aid=1252202&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 Priority: 5 Submitted By: frosch01 (frosch01) Assigned to: Nobody/Anonymous (nobody) Summary: Handling for gpg signed packages Initial Comment: Hi, with newer version of apt I received warnings about unsafe packages. It was no big thing to get the signing keys and I think it is a good thing. Unfortunately apt-proxy has no support for handling of gpg signs. Are there any plans to bring up support for this? frosch01 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=362078&aid=1252202&group_id=12078 |
From: Chris H. <ha...@de...> - 2005-08-01 15:52:20
|
Hi On Monday 01 Aug 2005 10:20, Brendon Lloyd Higgins wrote: > I'm on dialup, so resuming can be very handy with large files. I haven't > experienced apt-proxy properly resuming downloads. The only workaround is > that I set the option so that apt-proxy keeps downloading when the local > connection has been closed, but this doesn't solve the problem of resuming > between disconnections. Is this sort of thing possible? Or will I have to > do that for large packages manually (major pain)? I'm afraid that download resumes aren't available yet. This is on the planned feature list but the downloading procedure needs some structural improvements before I add download resumes and bandwidth limiting. If anyone has time to help out with apt-proxy coding please speak up. Chris |
From: Brendon L. H. <bh...@us...> - 2005-08-01 09:20:58
|
I'm on dialup, so resuming can be very handy with large files. I haven't=20 experienced apt-proxy properly resuming downloads. The only workaround is=20 that I set the option so that apt-proxy keeps downloading when the local=20 connection has been closed, but this doesn't solve the problem of resuming= =20 between disconnections. Is this sort of thing possible? Or will I have to d= o=20 that for large packages manually (major pain)? Peace, Brendon |
From: SourceForge.net <no...@so...> - 2005-07-29 14:30:38
|
Bugs item #1222275, was opened at 2005-06-17 00:27 Message generated for change (Comment added) made by sharkey 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 ---------------------------------------------------------------------- Comment By: Eric Sharkey (sharkey) Date: 2005-07-29 14:30 Message: Logged In: YES user_id=8749 I had this problem, too. The solution for me was to comment out the auto-generated backends and uncomment the backends with the comment: ;This backend has been commented out to prevent clash with a ;backend of the same name imported from v1 configuration The imported backends were set to use rsync, even though the v1 conf didn't specify rsync, and this caused the problem. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=112078&aid=1222275&group_id=12078 |
From: Chris H. <ha...@de...> - 2005-07-13 19:12:13
|
On Tue, Jul 12, 2005 at 05:25:28AM -0500, Jay Strauss wrote: > Chris Halls wrote: > >touch /var/log/apt-proxy.log > >chown aptproxy:adm /var/log/apt-proxy.log > > Bingo, that was the problem. It's all working now. Is there something > I should do to prevent this in the future? Or is this such a nothing > that I should just fix it as needed? Well, you wouldn't normally expect files in /var/log to be deleted instead of rotated. Whatever happened must be specific to your system. The logrotate script is configured to rotate the logfile once a week so it would have corrected itself eventually. > Thanks again You're welcome Chris |
From: Jay S. <me...@he...> - 2005-07-12 10:25:50
|
Chris Halls wrote: > On Mon, Jul 11, 2005 at 10:45:05PM -0500, Jay Strauss wrote: > >>I do not have a /var/log/apt-proxy.log file > > > That is a problem. apt-proxy does not run with enough priviledges to > create a file in /var/log, so this file must always be present. It is > created in apt-proxy's postinst and rotated by logrotate. You need to > recreate it > > touch /var/log/apt-proxy.log > chown aptproxy:adm /var/log/apt-proxy.log Bingo, that was the problem. It's all working now. Is there something I should do to prevent this in the future? Or is this such a nothing that I should just fix it as needed? Thanks again Jay |
From: Chris H. <ha...@de...> - 2005-07-12 08:30:21
|
On Mon, Jul 11, 2005 at 10:45:05PM -0500, Jay Strauss wrote: > I do not have a /var/log/apt-proxy.log file That is a problem. apt-proxy does not run with enough priviledges to create a file in /var/log, so this file must always be present. It is created in apt-proxy's postinst and rotated by logrotate. You need to recreate it touch /var/log/apt-proxy.log chown aptproxy:adm /var/log/apt-proxy.log > when I try to connect I get a bunch of these in my /var/log/daemon.log file: > > Jul 11 22:39:31 localhost apt-proxy[2554]: connect from 192.168.5.26 Great, that shows the problem I quoted hasn't occured for you. > > I did /etc/init.d/inetd restart, but it did not effect the above error. > Like I said, it used to work, I changed _NOTHING_ and now it doesn't work Well the log file doesn't delete itself for no reason. If something stops working, its usually a reasonable assumption to guess that something changed, even if you didn't change it deliberately yourself. e.g. a file got deleted, you ran out of disk space, a configuration file got corrupted etc. Chris |
From: Jay S. <me...@he...> - 2005-07-12 03:45:22
|
I apologize for the "hellllooooo" comment. I didn't realize my original post was on a weekend, and it wasn't the timing. I do not have a /var/log/apt-proxy.log file when I try to connect I get a bunch of these in my /var/log/daemon.log file: Jul 11 22:39:31 localhost apt-proxy[2554]: connect from 192.168.5.26 (192.168.5.26) Jul 11 22:39:31 localhost apt-proxy[2556]: connect from 192.168.5.26 (192.168.5.26) Jul 11 22:39:31 localhost apt-proxy[2558]: connect from 192.168.5.26 (192.168.5.26) Jul 11 22:39:31 localhost apt-proxy[2560]: connect from 192.168.5.26 (192.168.5.26) Jul 11 22:39:31 localhost apt-proxy[2562]: connect from 192.168.5.26 (192.168.5.26) I did /etc/init.d/inetd restart, but it did not effect the above error. Like I said, it used to work, I changed _NOTHING_ and now it doesn't work Thanks Jay Chris Halls wrote: > On Mon, Jul 11, 2005 at 12:38:04AM -0500, Jay Strauss wrote: > >>Helloooooo out there, anyone still on this list? > > > Yes, but debconf is on this week and I'm not checking all mailing lists > regularly. > > Please post the output in /var/log/apt-proxy.log. If there is none, try > following this advice in the README: > > Q: A connection cannot be established with apt-proxy on a remote machine. > Nothing appears in the apt-proxy.log file. > > A: apt-proxy is run by tcpd, which may deny connections depending on how it is > set up. If a connection is denied by tcpd, you will find a log message in > /var/log/daemon.log such as: > apt-proxy[nnnn]: refused connect from <hostname> > > You should check /etc/hosts.allow and hosts.deny. For example, the standard > ALL: PARANOID in /etc/hosts.deny will deny acess to clients whose hostname > cannot be looked up. > > If that doesn't help, double check that your inetd really is running. > > Hope that helps > Chris > > |
From: Chris H. <ha...@de...> - 2005-07-12 00:18:00
|
On Mon, Jul 11, 2005 at 12:38:04AM -0500, Jay Strauss wrote: > Helloooooo out there, anyone still on this list? Yes, but debconf is on this week and I'm not checking all mailing lists regularly. Please post the output in /var/log/apt-proxy.log. If there is none, try following this advice in the README: Q: A connection cannot be established with apt-proxy on a remote machine. Nothing appears in the apt-proxy.log file. A: apt-proxy is run by tcpd, which may deny connections depending on how it is set up. If a connection is denied by tcpd, you will find a log message in /var/log/daemon.log such as: apt-proxy[nnnn]: refused connect from <hostname> You should check /etc/hosts.allow and hosts.deny. For example, the standard ALL: PARANOID in /etc/hosts.deny will deny acess to clients whose hostname cannot be looked up. If that doesn't help, double check that your inetd really is running. Hope that helps Chris |