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...> - 2005-05-20 07:31:16
|
Hi, it took a while to get this fixed On Saturday 09 Apr 2005 13:27, Christian Knoke wrote: > [please CC: me, I'm not on this list] > > 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. Chris |
|
From: Chris H. <ha...@de...> - 2005-05-19 21:59:10
|
On Tuesday 17 May 2005 21:38, Tony Heal wrote: > I have apt-proxy v 1.3.0 install on Debian woody. > /usr/sbin/apt-proxy: cannot create /var/cache/apt-proxy/debian///dists.log: > permission denied Someone else reported a similar problem. Updating to 1.3.7 fixed it for them, and there are many other bugfixes in that version. I recommend you update: wget http://apt-proxy.sourceforge.net/apt-proxy/stable/apt-proxy_1.3.7_all.deb as root: dpkg -i apt-proxy_1.3.7_all.deb Chris |
|
From: Tony H. <th...@pa...> - 2005-05-17 20:39:35
|
I have apt-proxy v 1.3.0 install on Debian woody. The install went fine, but when trying to run apt-get update from a client I get the following log entries. /var/log/apt-proxy.log /usr/sbin/apt-proxy: cannot create /var/cache/apt-proxy/debian///dists.log: permission denied [14230 16:24:22] Bad URL /dists directory does not exist on any server [14230 16:24:22] Bad URL /dists directory does not exist on any server /var/log/syslog May 17 16:24:17 scallop_vm apt-proxy[13614]: connect from 192.168.1.11 I tried to search the mailing list, but it appears to be down. Tony |
|
From: Bill M. <mo...@ha...> - 2005-05-17 02:22:27
|
apt-proxy version: 1.9.28
apt-proxy has its own cache of packages. Also,
/var/cache/apt/archives is still used on each of the client machines.
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?
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?
Next, I can't see to import my existing .deb into the apt-proxy
cache. This seems to happen for every package:
2005/05/16 09:32 PDT [-] [import] m4_1.4.3-1_i386.deb skipped - no suitable backend found
2005/05/16 09:32 PDT [-] [import] libxml2-dev_2.6.16-7_i386.deb skipped - no suitable backend found
I just installed apt-proxy and ran apt-get "update" on the machine
and then tried
apt-proxy-import -i /var/cache/apt/archive
and receive the above.
Here's my backends:
[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
--
Bill Moseley
mo...@ha...
|
|
From: Jonathan K. <jk...@cs...> - 2005-05-13 18:55:15
|
On Fri, 13 May 2005, Micha wrote: > sorry i disturb the silence, but...:) i have a question. > > How can i add the content of one ap2 cache to another 'compatible' ap2 > (both holding the same release of debian under equal alias titles ) ? I always just untarred one into the same directory as the other one. > Related, but not the same: How can i point one ap to suck another one ? > I tried myhost:9999 but the port number does not seem to work in the > config, it was not resolved correctly. Why couldn't you just set the sucker's apt-proxy.conf to simply contain the normal address of the suckee? You know, whatever you whatever you would put int /etc/sources.list if you wanted to fetch from the suckee machine directly. -- Jonathan Koren World domination? I'll leave that to the jk...@cs... religious nuts and Republicans, thank you. http://www.cs.siu.edu/~jkoren/ -- The Monarch, "Venture Brothers" |
|
From: Micha <ear...@gm...> - 2005-05-13 06:32:11
|
Hi, sorry i disturb the silence, but...:) i have a question. How can i add the content of one ap2 cache to another 'compatible' ap2 (bot= h holding the same release of debian under equal alias titles ) ? Related, but not the same: How can i point one ap to suck another one ? I tried myhost:9999 but the port number does not seem to work in the config= , it was not resolved correctly. Any comments appreciated ! (And well, silence at least means no major problems, right) =B0 /\/ |
|
From: Zarita S. <Sm...@gb...> - 2005-05-03 17:09:54
|
Hello, overwrought by the suspense, mademoiselle flung herself upon her Ye mean that ye haven't the strength of character to resist the the huts of the slaves together with the big white house of the night agog, Mr. Blood closed his ears to the sounds of it, and we from us, and that I shall begin by leaving a heap of ashes where Blake and Mrs. Musgrove, who - as the ballad runs - had ripped op even seeing her again, yet the memory of her was to abide in his You are quite certain of that, M. le Baron - that you cannot? Captain Blood! he cried. Are you Captain Blood? detestable; and this for the very reason that made him concerned The Cinco Llagas it is. found himself oddly constrained before this frank and unsophistic Have a nice day. |
|
From: Bram M. <bra...@li...> - 2005-04-28 09:56:49
|
On Thu, 2005-04-28 at 11:45 +0200, Olivier Bornet wrote: > Hi, > > > > I have this for marillat: > > > > > > [marillat] > > > backends = > > > ftp://ftp.nerim.net/debian-marillat > > > > > > So, it seems it's OK with your config when you uncomment it. > > > > And what is in your /etc/apt/sources.list for marillat? > > something like: > > # > # marillat stuff > # > deb http://aptproxy:9999/marillat stable main > deb http://aptproxy:9999/marillat testing main > deb http://aptproxy:9999/marillat unstable main > deb-src http://aptproxy:9999/marillat unstable main > > Warning: I see you have: > > ##deb ftp://localhost:9999/marillat testing main > > As you use apt-proxy for getting the stuff, use http and not ftp. Thanks that combined with restarting apt-proxy did the trick! Regards Bram -- # Mertens Bram "M8ram" <bra...@li...> Linux User #349737 # # debian testing kernel 2.6.8-1-686 i686 512MB RAM # # 11:55:26 up 33 days, 18:09, 14 users, load average: 0.49, 0.40, 0.31 # |
|
From: Olivier B. <Oli...@pu...> - 2005-04-28 09:45:43
|
Hi, > > I have this for marillat: > >=20 > > [marillat] > > backends =3D > > ftp://ftp.nerim.net/debian-marillat > >=20 > > So, it seems it's OK with your config when you uncomment it. >=20 > And what is in your /etc/apt/sources.list for marillat? something like: # # marillat stuff # deb http://aptproxy:9999/marillat stable main deb http://aptproxy:9999/marillat testing main deb http://aptproxy:9999/marillat unstable main deb-src http://aptproxy:9999/marillat unstable main Warning: I see you have: ##deb ftp://localhost:9999/marillat testing main = =20 As you use apt-proxy for getting the stuff, use http and not ftp. > > do you have restarted apt-proxy ? You need to restart it to have the > > config reloaded. >=20 > No I hvaen't but when I uncomment the above and rerun apt-get update it > does looks for these packages so I thought restarting apt-proxy wasn't > necessary? Has far has I know, this is necessary. > Err ftp://localhost testing/main Packages > Connection timeout > Err ftp://localhost testing/main Release > Connection timeout > Failed to fetch ftp://localhost:9999/marillat/dists/testing/main/binary-i= 386/Packages.gz Connection timeout > Failed to fetch ftp://localhost:9999/marillat/dists/testing/main/binary-i= 386/Release Connection timeout Ftp is the problem. Put http instead. HTH. 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: Bram M. <bra...@li...> - 2005-04-28 09:13:10
|
On Thu, 2005-04-28 at 10:36 +0200, Olivier Bornet wrote: [...] > I have this for marillat: > > [marillat] > backends = > ftp://ftp.nerim.net/debian-marillat > > So, it seems it's OK with your config when you uncomment it. And what is in your /etc/apt/sources.list for marillat? > do you have restarted apt-proxy ? You need to restart it to have the > config reloaded. No I hvaen't but when I uncomment the above and rerun apt-get update it does looks for these packages so I thought restarting apt-proxy wasn't necessary? But running /etc/init.d/apt-proxy restart doesn't help... However no I get a connection timeout for marillat (also before restarting apt-proxy) imladris:~# /etc/init.d/apt-proxy restart Stopping apt-proxy. Starting apt-proxy imladris:~# apt-get update Hit http://localhost testing/main Packages Hit http://localhost testing/main Release Hit http://localhost testing/non-free Packages Hit http://localhost testing/non-free Release Hit http://localhost testing/main Sources Hit http://localhost testing/main Release Hit http://localhost testing/non-free Sources Hit http://localhost testing/non-free Release Hit http://localhost stable/updates/main Packages Hit http://localhost stable/updates/main Release Hit http://localhost stable/updates/non-free Packages Hit http://localhost stable/updates/non-free Release Err ftp://localhost testing/main Packages Connection timeout Err ftp://localhost testing/main Release Connection timeout Failed to fetch ftp://localhost:9999/marillat/dists/testing/main/binary-i386/Packages.gz Connection timeout Failed to fetch ftp://localhost:9999/marillat/dists/testing/main/binary-i386/Release Connection timeout Reading Package Lists... Done W: Couldn't stat source package list ftp://localhost testing/main Packages (/var/lib/apt/lists/localhost:9999_marillat_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. Thanks Bram -- # Mertens Bram "M8ram" <bra...@li...> Linux User #349737 # # debian testing kernel 2.6.8-1-686 i686 512MB RAM # # 11:07:11 up 33 days, 17:21, 14 users, load average: 0.24, 0.23, 0.14 # |
|
From: Olivier B. <Oli...@pu...> - 2005-04-28 08:36:27
|
Hello, > I installed apt-proxy and configured the main archives but I can't find > how to add some additional archives. > ... > At the moment /etc/apt-proxy/apt-proxy-v2.conf looks like: > ... > ;[marillat] > ;; mplayer etc > ;backends =3D ftp://ftp.nerim.net/debian-marillat >=20 > Up untill blackdown everything works fine but when I uncomment one of > the other backends (gnome2.2/clamassassin/marillat) I get "503 Service > Unavailable" errors. I have this for marillat: [marillat] backends =3D ftp://ftp.nerim.net/debian-marillat So, it seems it's OK with your config when you uncomment it. do you have restarted apt-proxy ? You need to restart it to have the config reloaded. 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: Bram M. <bra...@li...> - 2005-04-28 08:10:35
|
Hi I installed apt-proxy and configured the main archives but I can't find how to add some additional archives. My sources.list before installing apt-proxy looked like: deb http://debian.mines.inpl-nancy.fr/debian/ testing main non-free deb-src http://debian.mines.inpl-nancy.fr/debian/ testing main non-free deb http://security.debian.org/ stable/updates main non-free deb http://ftp.acc.umu.se/mirror/mirrors.evilgeniuses.org.uk/debian/backports/woody gnome2.2/ # get java deb ftp://ftp.easynet.be/blackdown/debian testing main non-free # get clamassassin deb http://debian.wgdd.de/debian testing main contrib non-free deb-src http://debian.wgdd.de/debian testing main contrib non-free # get mplayer etc. deb ftp://ftp.nerim.net/debian-marillat testing main At the moment /etc/apt-proxy/apt-proxy-v2.conf looks like: [DEFAULT] ;; Server IP to listen on ;address = 192.168.0.254 ;; Server port to listen on port = 9999 [snip all default values here] ;; Backend servers [debian] backends = http://debian.mines.inpl-nancy.fr/debian/ http://ftp.us.debian.org/debian http://ftp.de.debian.org/debian http://ftp2.de.debian.org/debian ftp://ftp.uk.debian.org/debian [security] ;; Debian security archive backends = http://security.debian.org/debian-security http://ftp2.de.debian.org/debian-security [blackdown] ;; Blackdown Java ;backends = http://ftp.gwdg.de/pub/languages/java/linux/debian backends = ftp://ftp.easynet.be/blackdown/debian ;[gnome2.2] ;; Gnome 2.2 ;backends = http://ftp.acc.umu.se/mirror/mirrors.evilgeniuses.org.uk/debian/backports/woody ;[clamassassin] ;; clamassassin ;backends = http://debian.wgdd.de ;[marillat] ;; mplayer etc ;backends = ftp://ftp.nerim.net/debian-marillat Up untill blackdown everything works fine but when I uncomment one of the other backends (gnome2.2/clamassassin/marillat) I get "503 Service Unavailable" errors. A quick search through the archives didn't lead me to relevant posts. My /etc/apt/sources.list on the same machine looks like: #deb http://debian.mines.inpl-nancy.fr/debian/ testing main non-free #deb-src http://debian.mines.inpl-nancy.fr/debian/ testing main non-free deb http://localhost:9999/debian/ testing main non-free deb-src http://localhost:9999/debian/ testing main non-free #deb http://security.debian.org/ stable/updates main non-free deb http://localhost:9999/security stable/updates main non-free #deb http://ftp.acc.umu.se/mirror/mirrors.evilgeniuses.org.uk/debian/backports/woody gnome2.2/ ##deb http://localhost:9999/gnome2.2/ gnome2.2/ # get java #deb ftp://ftp.easynet.be/blackdown/debian testing main non-free # deb ftp://ftp.skynet.be/pub/ftp.blackdown.org/debian testing main non-free ##deb ftp://localhost:9999/blackdown testing main non-free # get clamassassin #deb http://debian.wgdd.de/debian testing main contrib non-free #deb-src http://debian.wgdd.de/debian testing main contrib non-free ##deb http://localhost:9999/clamassassin/ testing main contrib non-free ##deb-src http://localhost:9999/clamassassin/ testing main contrib non-free # get mplayer etc. #deb ftp://ftp.nerim.net/debian-marillat testing main ##deb ftp://localhost:9999/marillat testing main Any idea what I'm doing wrong? TIA Bram -- # Mertens Bram "M8ram" <bra...@li...> Linux User #349737 # # debian testing kernel 2.6.8-1-686 i686 512MB RAM # # 10:01:09 up 33 days, 16:14, 14 users, load average: 0.41, 0.42, 0.28 # |
|
From: Gomes, R. <Ric...@gt...> - 2005-04-20 19:42:33
|
Hello all,=0D=0A I am hoping someone here can help me with some question I = have=0D=0Aregarding apt proxy=2E =0D=0AI have a deliverable here at work fo= r a centralized 'nix update server=2E=0D=0AOur main flavors Redhat, free BS= D, Solaris and hp=2E I have been looking=0D=0Afor software that could distr= ibute updates to all version of 'nix that=0D=0Awe run=2E Even if there was = some modification required across those=0D=0Adifferent version, it would be= ok=2E So my questions are:=0D=0A=0D=0AIs apt proxy able to distribute to a= ny version of 'nix that can run=0D=0Aapt-get?=0D=0AIf not can something be = done thru some perl scripting?=0D=0ADoes apt proxy have to be run on Debian= or can it be run on a Redhat or=0D=0AFree BSD machine?=0D=0AIf apt proxy d= oes not meet these requirements, is there something else=0D=0Athat would wo= rk similarly?=0D=0A=0D=0A=0D=0AThank You!=0D=0A=0D=0A=0D=0A=0D=0A=0D=0AThe = best way to predict your future is to create it=2E=0D=0A=0D=0A=0D=0A=0D=0A= =0D=0A-----------------------------------------=0D=0AThis email may contain= confidential and privileged material for the sole=0D=0Ause of the intended= recipient(s)=2E Any review, use, retention, distribution=0D=0Aor disclosur= e by others is strictly prohibited=2E If you are not the intended=0D=0Areci= pient (or authorized to receive for the recipient), please contact the=0D= =0Asender by reply email and delete all copies of this message=2E Also, ema= il is=0D=0Asusceptible to data corruption, interception, tampering, unautho= rized=0D=0Aamendment and viruses=2E We only send and receive emails on the = basis that we=0D=0Aare not liable for any such corruption, interception, ta= mpering, amendment=0D=0Aor viruses or any consequence thereof=2E=0D=0A |
|
From: Olivier B. <Oli...@pu...> - 2005-04-20 10:28:06
|
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
--
Olivier Bornet | français : 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: Olivier B. <Oli...@pu...> - 2005-04-19 16:05:32
|
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 /debia=
n/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: /va=
r/cache/apt-proxy/debian/dists/testing/Release
2005/04/19 17:43 CEST [Channel,3,192.33.221.75] [fetch_real] Consulting ser=
ver 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=
=2Eapt_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 - N=
one
2005/04/19 17:44 CEST [FetcherHttp,client] [debug] Received: Content-Type t=
ext/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 CEST [FetcherHttp,client] [Fetcher] Finished receiving dat=
a, status:504 saveData:1
2005/04/19 17:44 CEST [FetcherHttp,client] [Fetcher] Last request 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 clientConnecti=
onLost
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 c=
losed
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=20
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
=20
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.
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: Dely N. <Nic...@th...> - 2005-04-15 09:59:27
|
Hi all, I used to configure apt-proxy-v1, I've run apt-proxy-v1-to-v2, but I've behind a firewall and I need to config http_proxy var. The problem is that with apt-proxy-v2.conf, configuration file style change. My password contains non alpha numeric characters '%' '#', What are the rules to set non alpha numeric characters in this config file? Thanks Regards Nanouck |
|
From: Christian K. <ch...@ck...> - 2005-04-09 12:21:26
|
Hello, [please CC: me, I'm not on this list] I started using 1.9.17 on Debian Sarge and later have updated to version 1.9.28. I used apt-proxy-import to include 5 GB of deb files. Apt-proxy works so far and saves me traffic. Thanks! But cache cleaning does not work. In my config I have --->--->--- cleanup_freq = 2h max_age = off max_versions = 2 dynamic_backends = off ---<---<--- and in my log: 2005/04/09 13:52 CEST [-] [debug] Doing periodic cleaning up 2005/04/09 13:52 CEST [-] [debug] Periodic cleaning done There are a lot multiple package versions in the cache, but from du I can say, it does not delete any of them. For instance: karl:/var/cache/apt-proxy# ls -l debian/pool/main/e/exim/ total 2994 -rw-r--r-- 1 aptproxy root 758074 May 6 2004 exim_3.36-11_i386.deb -rw-r--r-- 1 aptproxy root 757532 Jan 9 13:32 exim_3.36-13_i386.deb -rw-r--r-- 1 aptproxy root 758742 Mar 3 23:02 exim_3.36-14_i386.deb -rw-r--r-- 1 aptproxy root 781630 Dec 11 2003 exim_3.36-9.1_i386.deb karl:/var/cache/apt-proxy# ls -l --time=atime debian/pool/main/e/exim/ total 2994 -rw-r--r-- 1 aptproxy root 758074 May 6 2004 exim_3.36-11_i386.deb -rw-r--r-- 1 aptproxy root 757532 Jan 9 13:32 exim_3.36-13_i386.deb -rw-r--r-- 1 aptproxy root 758742 Mar 3 23:02 exim_3.36-14_i386.deb -rw-r--r-- 1 aptproxy root 781630 Dec 11 2003 exim_3.36-9.1_i386.deb (Rem: I had to use a backup at some point and correct the atimes manually) From my understanding, it should only keep 2 versions of them and delete the others. What's wrong here? Christian -- Christian Knoke * * * http://cknoke.de * * * * * * * * * Ceterum censeo Microsoft esse dividendum. |
|
From: Chris H. <ha...@de...> - 2005-03-30 12:32:41
|
On Monday 28 Mar 2005 01:48, jason weir wrote: > when do i get my first proxy list? man apt-proxy |
|
From: Viktor B. <Et...@ja...> - 2005-03-12 01:50:48
|
Hello, slender gentleman of about Don Diego's own height and shape. See city. She was attended by two negroes who trotted after her at a into the treasury opened by the Baron in the name of the King of grew steadily between those two in the little time remaining, unt ships but that he preferred to keep it what it was. The three chance to discuss the matter with his chosen partner. As a resul PLANS OF ESCAPE because she resisted, and kissed her whilst she writhed in his some five miles away. Why do you run, then? she asked him coolly, standing slim and Have a good day. |
|
From: Chris H. <ha...@de...> - 2005-03-03 14:55:31
|
On Thursday 03 Mar 2005 11:57, Julien Antille wrote: > I cant seem to get apt-proxy-v2 working. > apt-proxy.log contains, after an "apt-get update" on the clients : > > 2005/03/03 13:23 CET [Channel,48,192.168.1.2] [debug] Headers: Host: > 192.168.1.3:9999, Connection: keep-alive, User-Agent: Debian APT-HTTP/1.3 > 2005/03/03 13:23 CET [Channel,48,192.168.1.2] [debug] Request: > GET /dists/unstable/non-free/binary-i386/Release > 2005/03/03 13:23 CET [Channel,48,192.168.1.2] [debug] Adding dists backend > dynamicaly I'd already fixed that bug on my local copy - thanks for reminding me to upload it :) You have triggered a bug in the dynamic backend creation logic, but I think you have the wrong entry in your sources.list. You need to add 'debian' after the :9999 of your deb line. You probably have something like this: deb http://your-apt-proxy:9999 unstable main contrib non-free Change it to: deb http://your-apt-proxy:9999/debian unstable main contrib non-free Chris |
|
From: Julien A. <jul...@kd...> - 2005-03-03 12:22:07
|
I cant seem to get apt-proxy-v2 working.=20
apt-proxy.log contains, after an "apt-get update" on the clients :
2005/03/03 13:23 CET [Channel,48,192.168.1.2] [debug] Headers: Host:=20
192.168.1.3:9999, Connection: keep-alive, User-Agent: Debian APT-HTTP/1.3
2005/03/03 13:23 CET [Channel,48,192.168.1.2] [debug] Request:=20
GET /dists/unstable/non-free/binary-i386/Release
2005/03/03 13:23 CET [Channel,48,192.168.1.2] [debug] Adding dists backend=
=20
dynamicaly
2005/03/03 13:23 CET [Channel,48,192.168.1.2] Traceback (most recent call=20
last):
=A0 =A0 =A0 =A0 =A0 File "/usr/lib/python2.3/site-packages/twisted/internet=
/default.py",=20
line 526, in doSelect
=A0 =A0 =A0 =A0 =A0 =A0 _logrun(selectable, _drdw, selectable, method, dict)
=A0 =A0 =A0 =A0 =A0 File "/usr/lib/python2.3/site-packages/twisted/python/l=
og.py", line=20
65, in callWithLogger
=A0 =A0 =A0 =A0 =A0 =A0 callWithContext({"system": lp}, func, *args, **kw)
=A0 =A0 =A0 =A0 =A0 File "/usr/lib/python2.3/site-packages/twisted/python/l=
og.py", line=20
52, in callWithContext
=A0 =A0 =A0 =A0 =A0 =A0 return context.call({ILogContext: newCtx}, func, *a=
rgs, **kw)
=A0 =A0 =A0 =A0 =A0 File "/usr/lib/python2.3/site-packages/twisted/python/c=
ontext.py",=20
line 43, in callWithContext
=A0 =A0 =A0 =A0 =A0 =A0 return func(*args,**kw)
=A0 =A0 =A0 =A0 --- <exception caught here> ---
=A0 =A0 =A0 =A0 =A0 File "/usr/lib/python2.3/site-packages/twisted/internet=
/default.py",=20
line 535, in _doReadOrWrite
=A0 =A0 =A0 =A0 =A0 =A0 why =3D getattr(selectable, method)()
=A0 =A0 =A0 =A0 =A0 File "/usr/lib/python2.3/site-packages/twisted/internet=
/tcp.py",=20
line 255, in doRead
=A0 =A0 =A0 =A0 =A0 =A0 return self.protocol.dataReceived(data)
=A0 =A0 =A0 =A0 =A0 File "/usr/lib/python2.3/site-packages/twisted/protocol=
s/basic.py",=20
line 223, in dataReceived
=A0 =A0 =A0 =A0 =A0 =A0 why =3D self.lineReceived(line)
=A0 =A0 =A0 =A0 =A0 File "/usr/lib/python2.3/site-packages/twisted/protocol=
s/http.py",=20
line 965, in lineReceived
=A0 =A0 =A0 =A0 =A0 =A0 self.allContentReceived()
=A0 =A0 =A0 =A0 =A0 File "/usr/lib/python2.3/site-packages/apt_proxy/apt_pr=
oxy.py", line=20
1628, in allContentReceived
=A0 =A0 =A0 =A0 =A0 =A0 http.HTTPChannel.allContentReceived(self)
=A0 =A0 =A0 =A0 =A0 File "/usr/lib/python2.3/site-packages/twisted/protocol=
s/http.py",=20
line 1006, in allContentReceived
=A0 =A0 =A0 =A0 =A0 =A0 req.requestReceived(command, path, version)
=A0 =A0 =A0 =A0 =A0 File "/usr/lib/python2.3/site-packages/twisted/protocol=
s/http.py",=20
line 557, in requestReceived
=A0 =A0 =A0 =A0 =A0 =A0 self.process()
=A0 =A0 =A0 =A0 =A0 File "/usr/lib/python2.3/site-packages/apt_proxy/apt_pr=
oxy.py", line=20
1349, in process
=A0 =A0 =A0 =A0 =A0 =A0 self.backend =3D Backend(self.uri[1:].split('/')[0]=
, self.factory
=A0 =A0 =A0 =A0 exceptions.AttributeError: Factory instance has no __call__=
method
any clue ?? (Debian SID system)
Julien Antille
|
|
From: Julien A. <jul...@kd...> - 2005-03-03 11:57:06
|
I cant seem to get apt-proxy-v2 working.
apt-proxy.log contains, after an "apt-get update" on the clients :
2005/03/03 13:23 CET [Channel,48,192.168.1.2] [debug] Headers: Host:
192.168.1.3:9999, Connection: keep-alive, User-Agent: Debian APT-HTTP/1.3
2005/03/03 13:23 CET [Channel,48,192.168.1.2] [debug] Request:
GET /dists/unstable/non-free/binary-i386/Release
2005/03/03 13:23 CET [Channel,48,192.168.1.2] [debug] Adding dists backend
dynamicaly
2005/03/03 13:23 CET [Channel,48,192.168.1.2] Traceback (most recent call
last):
File "/usr/lib/python2.3/site-packages/twisted/internet/default.py",
line 526, in doSelect
_logrun(selectable, _drdw, selectable, method, dict)
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)
--- <exception caught here> ---
File "/usr/lib/python2.3/site-packages/twisted/internet/default.py",
line 535, in _doReadOrWrite
why = getattr(selectable, method)()
File "/usr/lib/python2.3/site-packages/twisted/internet/tcp.py",
line 255, in doRead
return self.protocol.dataReceived(data)
File "/usr/lib/python2.3/site-packages/twisted/protocols/basic.py",
line 223, in dataReceived
why = self.lineReceived(line)
File "/usr/lib/python2.3/site-packages/twisted/protocols/http.py",
line 965, in lineReceived
self.allContentReceived()
File "/usr/lib/python2.3/site-packages/apt_proxy/apt_proxy.py", line
1628, in allContentReceived
http.HTTPChannel.allContentReceived(self)
File "/usr/lib/python2.3/site-packages/twisted/protocols/http.py",
line 1006, in allContentReceived
req.requestReceived(command, path, version)
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
1349, in process
self.backend = Backend(self.uri[1:].split('/')[0], self.factory
exceptions.AttributeError: Factory instance has no __call__ method
any clue ?? (Debian SID system)
Julien Antille
|
|
From: David B. <da...@ba...> - 2005-02-26 09:54:48
|
Chris Halls wrote: > On Tuesday 22 Feb 2005 23:04, David Balch wrote: > >>AttributeError: DummyFactory instance has no attribute 'addBackend' > > I've uploaded 1.9.27 which fixes this among other bugs. Excellent! Thanks Chris. > I noticed there is > still a bug which is making a-p-i not work immediately. If your databases > were recreated for some reason, and then you run apt-get update yet there are > no new Packages file, they will not get registered in the database and a-p-i > will not be able to search them to find out where to place the packages. You > will get the message 'No suitable backend found'. > > Solutions: > > 1. Wait for a day until an apt-get update gets new Packages > or 2. Delete all the Packages files: > sudo rm -rf /var/cache/apt-proxy/debian/dists > ..and then rerun apt-get update > (not tested) I tried 2 and it didn't work, so I'll leave it and try again tommorrow. Cheers, Dave. > > Chris > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > Apt-proxy-users mailing list > Apt...@li... > https://lists.sourceforge.net/lists/listinfo/apt-proxy-users > |
|
From: Chris H. <ha...@de...> - 2005-02-25 23:21:34
|
On Tuesday 22 Feb 2005 23:04, David Balch wrote: > AttributeError: DummyFactory instance has no attribute 'addBackend' > > What would be the best way of getting a-p running? > 1) Some fix for a-p 1.9.x (I don't know any Python but should be able > to have a stab at it) I've uploaded 1.9.27 which fixes this among other bugs. I noticed there is still a bug which is making a-p-i not work immediately. If your databases were recreated for some reason, and then you run apt-get update yet there are no new Packages file, they will not get registered in the database and a-p-i will not be able to search them to find out where to place the packages. You will get the message 'No suitable backend found'. Solutions: 1. Wait for a day until an apt-get update gets new Packages or 2. Delete all the Packages files: sudo rm -rf /var/cache/apt-proxy/debian/dists ..and then rerun apt-get update (not tested) Chris |
|
From: Chris H. <ha...@de...> - 2005-02-25 23:21:34
|
also available from=20 http://apt-proxy.sourceforge.net/apt-proxy/unstable/apt-proxy_1.9.27_all.deb Chris =46ormat: 1.7 Date: Fri, 25 Feb 2005 20:53:20 +0000 Source: apt-proxy Binary: apt-proxy Architecture: source all Version: 1.9.27 Distribution: unstable Urgency: low Maintainer: Otavio Salvador <ot...@de...> Changed-By: Chris Halls <ha...@de...> Description: apt-proxy - Debian archive proxy and partial mirror builder development Closes: 288829 288905 292818 296574 296710 296875 Changes: apt-proxy (1.9.27) unstable; urgency=3Dlow . * Delay database directory creation until after uid change. Older installations are fixed by chmoding directory in postinst. Closes: #288829 * Fix exception in apt-proxy-import. Closes: #296574 * Close connection where necessary after sending complete file. Closes: #288905 * Pipe file verification output to /dev/null for UML speedups, thanks Paul Wagland for the patch. Closes: #292818 * init script: - Fix bashism in init script. Closes: #296710 - Improve output and remove first sleep, thanks again Herbert Thielen. Closes: #296875 =46iles: 3eaf56eb9b69d7d145a4bcbe932e1ac6 638 admin extra apt-proxy_1.9.27.dsc 1bc2683ab4e7462948d518a66ab6832c 64161 admin extra apt-proxy_1.9.27.tar.gz a8b249915ad0702b237b98fad00fb577 59914 admin extra apt-proxy_1.9.27_all.deb Accepted: apt-proxy_1.9.27.dsc to pool/main/a/apt-proxy/apt-proxy_1.9.27.dsc apt-proxy_1.9.27.tar.gz to pool/main/a/apt-proxy/apt-proxy_1.9.27.tar.gz apt-proxy_1.9.27_all.deb to pool/main/a/apt-proxy/apt-proxy_1.9.27_all.deb |
