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: Chris H. <ha...@de...> - 2004-11-15 10:55:07
|
On Sun, 2004-11-14 at 18:15 +0100, mi wrote: > I just like to make sure. > With ap2 there's no point in preserving the 9999/tcp entry in /etc/services (debian) i guess. > If not downgrading some day (and i see no reason yet) it's obsolete, right ? > Since this file if often updated (i.r. overwritten) when updating packages, the entry will be soon gone. It's obsolete for now, yes. It would be nice if someone had the time to add inetd support as an option, but it would need a different inetd entry anyway. Chris |
|
From: mi <ww...@gm...> - 2004-11-14 17:16:47
|
I just like to make sure.
With ap2 there's no point in preserving the 9999/tcp entry in /etc/services=
(debian) i guess.
If not downgrading some day (and i see no reason yet) it's obsolete, right ?
Since this file if often updated (i.r. overwritten) when updating packages,=
the entry will be soon gone.
=B0
/\/
|
|
From: <lar...@sp...> - 2004-10-06 02:03:00
|
Quoting Thomas R=F6sch <th...@sd...>: >[...] > No, but just read the fix in the bug data base: disable http-pipelining > in your config file. > > Tom > > D'Oh! (*blushes*) Thanks, Tom! |
|
From: Steve C. <co...@ko...> - 2004-10-05 20:01:33
|
Switched to 1.9.18 available in Unstable. Slow as death is right. It reduced memory from ~220MB in Twisted to about ~20MB but the performance has fallen right off a cliff. |
|
From: <th...@sd...> - 2004-10-05 08:10:28
|
Larry McCarthy wrote: > Warning! Please trim if you're going to include this post in a reply! > > Apt-proxy 2 has lately become slow as death. I think it started after the last > minor upgrade in Sid. The default logging level got turned up in that release, > but it also slowed to a crawl, even (especially!) for cached Debs. I see a lot > of these (see below) in the log; is this normal? No, but just read the fix in the bug data base: disable http-pipelining in your config file. Tom |
|
From: Larry M. <Lar...@Sp...> - 2004-10-05 05:51:52
|
Warning! Please trim if you're going to include this post in a reply! Apt-proxy 2 has lately become slow as death. I think it started after the last minor upgrade in Sid. The default logging level got turned up in that release, but it also slowed to a crawl, even (especially!) for cached Debs. I see a lot of these (see below) in the log; is this normal? - Larry <-- /var/log/apt-proxy.log snippet --> 2004/10/04 22:43 PDT [Channel,246,192.168.1.15] [debug] Request: GET /debian/pool/main/p/python-imaging/python-imaging_1.1.4-3_all.deb 2004/10/04 22:43 PDT [Channel,246,192.168.1.15] [client] have active fetcher: /debian/pool/main/p/python-imaging/python-imaging_1.1.4-3_all.deb 2004/10/04 22:43 PDT [Channel,246,192.168.1.15] [debug] Headers: Host: ipanema:9999, Connection: keep-alive, User-Agent: Debian APT-HTTP/1.3 2004/10/04 22:43 PDT [Channel,246,192.168.1.15] [debug] Request: GET /debian/pool/main/g/gramps/gramps_1.0.7-4_all.deb 2004/10/04 22:43 PDT [Channel,246,192.168.1.15] [fetcher_activate] (debian) http://mirrors.kernel.org:80/debian/pool/main/g/gramps/gramps_1.0.7-4_all.deb 2004/10/04 22:43 PDT [Channel,246,192.168.1.15] [file_ok] check_cached: /var/cache/apt-proxy/debian/pool/main/g/gramps/gramps_1.0.7-4_all.deb 2004/10/04 22:43 PDT [-] [file_ok] Modification time:Tue Sep 28 21:32:02 2004 2004/10/04 22:43 PDT [-] [file_ok] file is immutable: /var/cache/apt-proxy/debian/pool/main/g/gramps/gramps_1.0.7-4_all.deb 2004/10/04 22:43 PDT [-] [fetch_real] Using cached copy of /var/cache/apt-proxy/debian/pool/main/g/gramps/gramps_1.0.7-4_all.deb 2004/10/04 22:43 PDT [-] [fetcher_activate] (debian) http://mirrors.kernel.org:80/debian/pool/main/g/gramps/gramps_1.0.7-4_all.deb 2004/10/04 22:45 PDT [Channel,246,192.168.1.15] Unhandled error in Deferred: 2004/10/04 22:45 PDT [Channel,246,192.168.1.15] Failure: exceptions.Exception: Consumer asked us to stop producing 2004/10/04 22:45 PDT [Channel,246,192.168.1.15] [debug] Client connection closed 2004/10/04 22:45 PDT [Channel,246,192.168.1.15] Top 10: 2004/10/04 22:45 PDT [Channel,246,192.168.1.15] 270 Request 2004/10/04 22:45 PDT [Channel,246,192.168.1.15] 237 FetcherFile 2004/10/04 22:45 PDT [Channel,246,192.168.1.15] 182 Server 2004/10/04 22:45 PDT [Channel,246,192.168.1.15] 174 FileSender 2004/10/04 22:45 PDT [Channel,246,192.168.1.15] 140 Channel 2004/10/04 22:45 PDT [Channel,246,192.168.1.15] 85 Exception 2004/10/04 22:45 PDT [Channel,246,192.168.1.15] 63 StringTransport 2004/10/04 22:45 PDT [Channel,246,192.168.1.15] 42 Deferred 2004/10/04 22:45 PDT [Channel,246,192.168.1.15] 33 DBError 2004/10/04 22:45 PDT [Channel,246,192.168.1.15] 24 StandardError <-- End of snippet --> |
|
From: Larry M. <Lar...@Sp...> - 2004-10-05 04:49:19
|
There are new versions appearing every so often over the past few weeks in Debian Sid and Sarge. |
|
From: Steve C. <co...@ko...> - 2004-10-04 18:28:13
|
All the files seem to have reverted to 2002 versions. Is this project closed? :( |
|
From: Amit G. <ag...@cs...> - 2004-10-01 18:32:24
|
Hi all, I want to setup apt-proxy for SuSE. Has anybody tried it?? Can someone provide good how to or tutorial for this. Thanks in advance. ----- with regards, Amit Goyal |
|
From: Eric <cr...@my...> - 2004-09-26 02:10:06
|
I'm trying to get v2 up and working on a sarge system. Apt-proxy seems to work right, the "apt-get update" worked through the apt-proxy just fine. When I tried to import the apt archives, this happens:
root@gideon:/# apt-proxy-import -i /var/cache/apt/archives
Updating twisted's process module.
No updating required.
Traceback (most recent call last):
File "/usr/sbin/apt-proxy-import", line 73, in ?
factoryConfig(factory)
File "/usr/lib/python2.3/site-packages/apt_proxy/apt_proxy_conf.py", line 125, in factoryConfig
backend = Backend(name, server, factory)
File "/usr/lib/python2.3/site-packages/apt_proxy/apt_proxy.py", line 1175, in __init__
packages.AptPackages(self, factory)
File "/usr/lib/python2.3/site-packages/apt_proxy/packages.py", line 117, in __ init__
self.packages = shelve.open(self.status_dir+'/'+'packages.db')
File "/usr/lib/python2.3/shelve.py", line 231, in open
return DbfilenameShelf(filename, flag, protocol, writeback, binary)
File "/usr/lib/python2.3/shelve.py", line 212, in __init__
Shelf.__init__(self, anydbm.open(filename, flag), protocol, writeback, binar y)
File "/usr/lib/python2.3/anydbm.py", line 83, in open
return mod.open(file, flag, mode)
File "/usr/lib/python2.3/dbhash.py", line 16, in open
return bsddb.hashopen(file, flag, mode)
File "/usr/lib/python2.3/bsddb/__init__.py", line 192, in hashopen
d.open(file, db.DB_HASH, flags, mode)
bsddb._db.DBAccessError: (13, 'Permission denied')
Exception exceptions.AttributeError: "DbfilenameShelf instance has no attribute 'writeback'" in ignored
the twisted version is 1.3.0-3
|
|
From: mi <ww...@gm...> - 2004-09-25 18:45:50
|
Debian Sarge runs an a.p. of nearly version 2 (more exact, 1.9x), with a new config syntax, where the old file 'apt-proxy.conf' is used by version 1 only. Both files are present in /etc/apt-proxy/ so that you can up/downgrade without editing the config files. You have to keep the correct one (or both) up to date. Attached below is my apt-proxy-v2.conf. It runs on y dialup box and is designed for only occasionally serving other boxes on small a home LAN. ';' leads comment lines in this version-2-type config. Note the 'http' debian package server URLs. Also, as far as i know, there's no 'security' service for testing (but will be for sarge when it's getting released). I also attach an example sources.list. hth -- Michel... [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 ;; Should be: 10h min_refresh_delay = 36000 ;; 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 db:6 ;; 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 = 300 ;; 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 ;; Disable HTTP pipelining within apt-proxy (for test purposes) ;disable_pipelining=1 ;;-------------------------------------------------------------- ;; 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 = 7d ;; Maximum age of files before deletion from the cache (seconds) max_age = off ;; 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] ;; Debian archive ;timeout will be the global value backends = http://ftp.de.debian.org/debian ; ftp://ftp.de.debian.org/debian [non-US] ;; Debian non-US archive ;timeout will be the global value backends = http://ftp.de.debian.org/debian-non-US ; ftp://ftp.de.debian.org/debian-non-US ; http://ftp.non-us.debian.org/debian-non-US ;[security] ;; Debian security archive ; backends = ; http://security.debian.org/debian-security ; http://ftp2.de.debian.org/debian-security Here's an example /etc/apt/sources.list: # __________ TESTING: # deb http://chewbacca:9999/debian testing main contrib non-free deb http://chewbacca:9999/non-US testing/non-US main contrib non-free |
|
From: <Mat...@we...> - 2004-09-20 09:57:53
|
> Hi, Hi Jay! > I"m feeling like a nob, but I can"t get this to work. In the > past, I"ve had apt-proxy v1 working, but that machine is long > gone so I can"t copy from it. > > I"m running apt-proxy on a debian Sarge machine, and I"m > trying to access the proxy from a Sarge machine (fresh install > last night) > > I"m getting the following error: > > laptop:~# apt-get update > Err http://pt testing/main Packages > 404 is not serviced by this server > Ign http://pt testing/main Release > Err http://pt testing/main Sources > 404 is not serviced by this server > Ign http://pt testing/main Release [...] > Below are my config files. Hoping for some help, because I"m stuck. > > Thanks > Jay > > my client, sources.list: > > laptop:~# cat /etc/apt/sources.list > > deb http://pt:9999 testing main > deb-src http://pt:9999 testing main > > #deb http://security.debian.org/ testing/updates main Add the name of the backend to your servers in /etc/apt/sources.list: deb http://pt:9999/main testing main deb-src http://pt:9999/main testing main should work. Bye, Matthias |
|
From: Martijn B. <e.a...@tn...> - 2004-09-20 09:35:28
|
Hi, I have noticed that apt-proxy when the space on the disk it uses drop below approximately 30Mb. I only guess why, but I think that apt-proxy should check diskspace and delete part of the contents of the cache to make space for new packages. Bye, Martijn Brouwer |
|
From: Jay S. <me...@he...> - 2004-09-19 19:05:41
|
Hi, I'm feeling like a nob, but I can't get this to work. In the past, I've = had apt-proxy v1 working, but that machine is long gone so I can't copy from = it. I'm running apt-proxy on a debian Sarge machine, and I'm trying to = access the proxy from a Sarge machine (fresh install last night) I'm getting the following error: laptop:~# apt-get update Err http://pt testing/main Packages 404 is not serviced by this server Ign http://pt testing/main Release Err http://pt testing/main Sources 404 is not serviced by this server Ign http://pt testing/main Release Failed to fetch = http://pt:9999/dists/testing/main/binary-i386/Packages.gz 404 is not = serviced by this server Failed to fetch http://pt:9999/dists/testing/main/source/Sources.gz 404 = is not serviced by this server Reading Package Lists... Done W: Couldn't stat source package list http://pt testing/main Packages = (/var/lib/apt/lists/pt:9999_dists_testing_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 know apt-proxy is listening on 9999 since I can telnet to it. Below = are my=20 config files. Hoping for some help, because I'm stuck.=20 Thanks Jay my client, sources.list: laptop:~# cat /etc/apt/sources.list deb http://pt:9999 testing main deb-src http://pt:9999 testing main #deb http://security.debian.org/ testing/updates main my server's /etc/apt-proxy/apt-proxy.conf APT_PROXY_CACHE=3D/var/cache/apt-proxy add_backend /main/ \ $APT_PROXY_CACHE/debian/ \ ftp.us.debian.org::debian/ \ ftp.de.debian.org::debian/ \ ftp2.de.debian.org::debian/ \ ftp.uk.debian.org::debian/ add_backend /non-US/ \ $APT_PROXY_CACHE/non-US/ \ ftp.de.debian.org::debian-non-US/ \ ftp2.de.debian.org::debian-non-US/ \ ftp.uk.debian.org::debian/non-US/ add_backend /security/ \ $APT_PROXY_CACHE/security/ \ security.debian.org::debian-security/ \ non-us.debian.org::debian-security/ CLEANUP_DAYS=3D14 CLEAN_SWEEP=3D60 MAX_VERSIONS=3D2 BACKEND_FREQ=3D240 RSYNC_TIMEOUT=3D30 WGET_TIMEOUT=3D30 |
|
From: mi <ww...@gm...> - 2004-09-07 03:17:43
|
Hello, i'm just looking into tha ap2 logs, and here i find: << 2004/09/07 04:37 CEST [Channel,0,192.168.0.3] [file_ok] check_cached: /var/cache/apt-proxy/debian/pool/main/g/gnustep-gui/libgnustep-gui0_0.9.3-4_i386.deb 2004/09/07 04:37 CEST [Channel,0,192.168.0.3] [fetch_real] Consulting server about /var/cache/apt-proxy/debian/pool/main/g/gnustep-gui/libgnustep-gui0_0.9.3-4_i386.deb >> What does it mean, 'Consulting server about ...' -- which server ? The debian mirror ? Oh, and i didn't find any description of the logging-levels in the docs here (sarge). What about the optional 'db' keyword, and are there others ? I set it to 'debug = all db:6'. -- Michel... . |
|
From: Larry M. <Lar...@Sp...> - 2004-08-30 05:27:38
|
Quoting apt...@li...: > When starting a bundle of dowonloads on a single desktop machine, ap v2 seems > to > 'confuse' the download time estimation by aptitude. I've seen the same thing with plain old apt-get against an apt-proxy server on my near-dialup (384/192) DSL. I think this has to do with apt-proxy filling it's cache, and then delivering to the client from that cache. It's a bit, well, "lumpy." But, as you say, in the end, it comes to about the same speed as going direct to the mirror. And, of course, the second, third, etc. updates are at LAN speed!!! - Larry. p.s. - V1.x did the same thing. |
|
From: mi <ww...@gm...> - 2004-08-29 15:53:39
|
When starting a bundle of dowonloads on a single desktop machine, ap v2 seems to 'confuse' the download time estimation by aptitude. Looks like parallel or background (wget?) downloads aren't shown exactly in aptitude, so that only one of a few, and seems to be very slow, where one or more others seem to finish immediately after the first one is done. Then, after some minutes, ap 'fin tunes' more accurateley, and the rest of the donwloading works very stable and smooth at a rather high throughput. At some points i can see such 'distortions' again, though. This is on a slow dialup. Don't know how it looks on a fast line ? -- Michel... . |
|
From: Chris H. <ha...@de...> - 2004-08-25 10:37:19
|
On Mon, 2004-08-23 at 19:07, mi wrote: > Does a-p-ipmort still work for ap v2 ? Yes, it has been rewritten for v2. Chris |
|
From: mi <ww...@gm...> - 2004-08-23 17:08:10
|
Does a-p-ipmort still work for ap v2 ? Chris Halls <ha...@de...>: > The old apt-proxy used to use the file atime to keep track of when a file was last downloaded, > but this has problems if you do not update atimes or access the cache files > with other tools, so ranty wrote code to store the file times in a > database instead. -- Michel... . |
|
From: Chris H. <ha...@de...> - 2004-08-23 09:24:29
|
On Mon, 2004-08-23 at 03:12, mi wrote: > btw. What does this 'adopting new file' stuff in the log mean ? It means apt-proxy noticed a file in the cache that is not in its database and is adding it to the database. The old apt-proxy used to use the file atime to keep track of when a file was last downloaded, but this has problems if you do not update atimes or access the cache files with other tools, so ranty wrote code to store the file times in a database instead. Chris |
|
From: Chris H. <ha...@de...> - 2004-08-23 09:22:21
|
On Mon, 2004-08-23 at 03:15, mi wrote: > I still would prefer to be able to control the ap port by xinetd.conf. > Is the decision to make it standalone only inevitable ? 'Only inevitable' doesn't make sense. I guess you mean, will it always be like this? The answer is, it is possible to add support for inetd/xinetd, but is low priority compared to the other bugs that need fixing first. Chris |
|
From: mi <ww...@gm...> - 2004-08-23 01:15:29
|
Sorry, i just read the previous postings. I didn't realize (and also didn't read it in the docs) the standalone thing. It's fixed by uncommenting the apt-proxy entry for xinetd, now. I still would prefer to be able to control the ap port by xinetd.conf. Is the decision to make it standalone only inevitable ? -- Michel... . |
|
From: mi <ww...@gm...> - 2004-08-23 01:13:02
|
btw. What does this 'adopting new file' stuff in the log mean ? It seems to work only while doing donwload ? -- Michel... . |
|
From: mi <ww...@gm...> - 2004-08-22 23:51:54
|
Hello, I did upgrade to ap2 (debian sarge). But now aptitude 'u' update package list can't connect to ap. The ap log says 'any:999 already in use.' See attachments. Version 1 worked ok before. Any idea ? -- Michel... . |
|
From: Larry M. <Lar...@Sp...> - 2004-08-21 23:06:08
|
Solved. Chris replied that apt-proxy-v2 is a standalone daemon that doesn't (yet) run under inetd or xinetd. If you have this problem, it's easy to fix under xinetd even for noobs like me :) * Save the apt-proxy xinetd service start-up file to a safe place (in anticipation of xinetd support Real Soon Now), like so: # mv /etc/xinetd.d/apt-proxy /usr/share/doc/apt-proxy # Or someplace * Make sure apt-proxy is stopped, restart xinetd, then start apt-proxy: # /etc/init.d/apt-proxy stop Stopping apt-proxy. # /etc/init.d/xinetd restart Stopping internet superserver: xinetd. Starting internet superserver: xinetd. # /etc/init.d/apt-proxy start Starting apt-proxy. # Works fine for me. Thanks, Chris! [ Giant distracting inline thread snipped ] |
