Menu
▾
▴
apt-proxy-users
|
From: Bram M. <bra...@li...> - 2005-06-08 18:50:52
|
Hi I have been running apt-proxy for a while now without problems. Now I would like to add debian-volatile to my sources following the advice on http://www.clamav.net/binary.html. The instructions on this page are for apt but I can't find how I should adapt them for apt-proxy. In my /etc/apt-proxy/apt-proxy-v2.conf I had the following for ClamAV: [clamassassin] ;; clamassassin backends = http://debian.wgdd.de/debian And in my /etc/apt/sources.list: # get clamassassin deb http://localhost:9999/clamassassin/ testing main contrib non-free I have changed my apt-proxy-v2.conf to: [clamassassin] ;; clamassassin backends = ftp://ftp2.de.debian.org/debian-volatile ;http://debian.wgdd.de/debian But no matter what I put in my sources.list I get the following error when I run apt-get update: imladris:~# apt-get update [...] Err http://localhost testing/volatile/main Packages 404 Not Found Ign http://localhost testing/volatile/main Release Hit http://localhost testing/main Packages Hit http://localhost testing/main Release Failed to fetch http://localhost:9999/clamassassin/dists/testing/volatile/main/binary-i386/Packages.gz 404 Not Found Reading Package Lists... Done W: Couldn't stat source package list http://localhost testing/volatile/main Packages (/var/lib/apt/lists/localhost:9999_clamassassin_dists_testing_volatile_main_binary-i386_Packages) - stat (2 No such file or directory) W: You may want to run apt-get update to correct these problems E: Some index files failed to download, they have been ignored, or old ones used instead. I have tried several combinations etch/volatile, testing/volatile, testing, volatile, ... in my sources.list but none of them worked. Where can I find examples of such configuration? TIA Bram -- # Mertens Bram "M8ram" <bra...@li...> Linux User #349737 # # debian testing kernel 2.6.8-1-686 i686 512MB RAM # # 20:42:01 up 75 days, 2:56, 11 users, load average: 0.61, 0.34, 0.28 # |
|
From: Erik C.J. L. <el...@dd...> - 2005-06-08 20:45:34
|
Bram Mertens wrote: > Hi > > I have been running apt-proxy for a while now without problems. Now I > would like to add debian-volatile to my sources following the advice on > http://www.clamav.net/binary.html. > > The instructions on this page are for apt but I can't find how I should > adapt them for apt-proxy. > > In my /etc/apt-proxy/apt-proxy-v2.conf I had the following for ClamAV: > [clamassassin] > ;; clamassassin > backends = http://debian.wgdd.de/debian > > And in my /etc/apt/sources.list: > # get clamassassin > deb http://localhost:9999/clamassassin/ testing main contrib non-free Hi Bram, I have no experience with apt-proxy-v2 and its .conf, but this last line looks wierd to me. If I understand it right you are saying these packages in volatile can be found in testing. I think your sources.list should read: deb http://localhost:9999/clamassassin/ volatile main contrib non-free > > I have changed my apt-proxy-v2.conf to: > [clamassassin] > ;; clamassassin > backends = ftp://ftp2.de.debian.org/debian-volatile > ;http://debian.wgdd.de/debian > > But no matter what I put in my sources.list I get the following error > when I run apt-get update: > imladris:~# apt-get update > [...] > Err http://localhost testing/volatile/main Packages > 404 Not Found > Ign http://localhost testing/volatile/main Release > Hit http://localhost testing/main Packages > Hit http://localhost testing/main Release > Failed to fetch > http://localhost:9999/clamassassin/dists/testing/volatile/main/binary-i386/Packages.gz > 404 Not Found > Reading Package Lists... Done > W: Couldn't stat source package list http://localhost > testing/volatile/main Packages > (/var/lib/apt/lists/localhost:9999_clamassassin_dists_testing_volatile_main_binary-i386_Packages) > - stat (2 No such file or directory) > W: You may want to run apt-get update to correct these problems > E: Some index files failed to download, they have been ignored, or old > ones used instead. > > I have tried several combinations etch/volatile, testing/volatile, > testing, volatile, ... in my sources.list but none of them worked. > > Where can I find examples of such configuration? > > TIA > > Bram HTH, Erik. -- -------------------------------------------------------------------------- Erik C.J. Laan elaan at dds.nl Please reply below the message, please cut unrelevant pieces from a reply. -------------------------------------------------------------------------- |
|
From: Erik C.J. L. <el...@dd...> - 2005-06-08 20:49:34
|
Erik C.J. Laan wrote: > Bram Mertens wrote: [snip] > Hi Bram, > > I have no experience with apt-proxy-v2 and its .conf, but this last line > looks wierd to me. If I understand it right you are saying these > packages in volatile can be found in testing. I think your sources.list > should read: > > deb http://localhost:9999/clamassassin/ volatile main contrib non-free > >> >> I have changed my apt-proxy-v2.conf to: >> [clamassassin] >> ;; clamassassin >> backends = ftp://ftp2.de.debian.org/debian-volatile >> ;http://debian.wgdd.de/debian >> >> But no matter what I put in my sources.list I get the following error >> when I run apt-get update: >> imladris:~# apt-get update >> [...] >> Err http://localhost testing/volatile/main Packages >> 404 Not Found >> Ign http://localhost testing/volatile/main Release >> Hit http://localhost testing/main Packages >> Hit http://localhost testing/main Release >> Failed to fetch >> http://localhost:9999/clamassassin/dists/testing/volatile/main/binary-i386/Packages.gz >> 404 Not Found >> Reading Package Lists... Done >> W: Couldn't stat source package list http://localhost >> testing/volatile/main Packages >> (/var/lib/apt/lists/localhost:9999_clamassassin_dists_testing_volatile_main_binary-i386_Packages) >> - stat (2 No such file or directory) >> W: You may want to run apt-get update to correct these problems >> E: Some index files failed to download, they have been ignored, or old >> ones used instead. >> >> I have tried several combinations etch/volatile, testing/volatile, >> testing, volatile, ... in my sources.list but none of them worked. Sorry, I wasn't awake enough to realised you had already tried this. Erik -- -------------------------------------------------------------------------- Erik C.J. Laan elaan at dds.nl Please reply below the message, please cut unrelevant pieces from a reply. -------------------------------------------------------------------------- |
|
From: Chris H. <ha...@de...> - 2005-06-09 09:53:22
|
On Wednesday 08 Jun 2005 19:50, Bram Mertens wrote: > Hi > > I have been running apt-proxy for a while now without problems. Now I > would like to add debian-volatile to my sources following the advice on > http://www.clamav.net/binary.html. > > The instructions on this page are for apt but I can't find how I should > adapt them for apt-proxy. > > In my /etc/apt-proxy/apt-proxy-v2.conf I had the following for ClamAV: > [clamassassin] > ;; clamassassin > backends = http://debian.wgdd.de/debian > > And in my /etc/apt/sources.list: > # get clamassassin > deb http://localhost:9999/clamassassin/ testing main contrib non-free The clamav.net page says you should use this sources.list line: deb http://ftp2.de.debian.org/debian-volatile sarge/volatile main You need to replace the URL in that example with one that points to your apt-proxy: deb http://localhost:9999/clamassassin etch/volatile main So that should work. However: > I have changed my apt-proxy-v2.conf to: > [clamassassin] > ;; clamassassin > backends = ftp://ftp2.de.debian.org/debian-volatile I would recommend you rename your backend to debian-volatile, since it is not just clamassassin: [debian-volatile] backends = ftp://ftp2.de.debian.org/debian-volatile That way, your sources.list line is more obvious that you are pointing at debian-volatile, not a clamassassin repository: deb http://localhost:9999/debian-volatile etch/volatile main Chris |
|
From: Bram M. <bra...@li...> - 2005-06-09 20:35:20
|
Chris Halls wrote: [...] > I would recommend you rename your backend to debian-volatile, since it is not > just clamassassin: > > [debian-volatile] > backends = ftp://ftp2.de.debian.org/debian-volatile > > That way, your sources.list line is more obvious that you are pointing at > debian-volatile, not a clamassassin repository: > > deb http://localhost:9999/debian-volatile etch/volatile main Thanks for the suggestion, I followed your instructions: sources.list: deb http://localhost:9999/debian-volatile etch/volatile main I also tried: deb http://localhost:9999/debian-volatile testing/volatile main and deb http://localhost:9999/debian-volatile volatile main /etc/apt-proxy/apt-proxy-v2.conf: [debian-volatile] backends = ftp://ftp2.de.debian.org/debian-volatile I also tried: backends = http://ftp2.de.debian.org/debian-volatile But I keep getting 503 Service unavailable errors even though the file does exist: http://ftp2.de.debian.org/debian-volatile/dists/testing/volatile/main/binary-i386/Packages.gz wget http://ftp2.de.debian.org/debian-volatile/dists/testing/volatile/main/binary-i386/Packages.gz is succesfull I even tried to copy this file to /var/lib/apt/lists/locahost... but without succes. I have returned to my old config for now but I'd like to be able to get this working... Thanks again for the suggestions. Bram -- # Mertens Bram "M8ram" <bra...@li...> Linux User #349737 # # debian testing kernel 2.6.8-1-686 i686 512MB RAM # # 22:08:01 up 76 days, 4:22, 6 users, load average: 0.32, 0.29, 0.12 # |
|
From: Chris H. <ha...@de...> - 2005-06-16 11:38:19
|
On Thursday 09 Jun 2005 21:35, Bram Mertens wrote: > /etc/apt-proxy/apt-proxy-v2.conf: > [debian-volatile] > backends =3D ftp://ftp2.de.debian.org/debian-volatile > I also tried: > backends =3D http://ftp2.de.debian.org/debian-volatile > > > But I keep getting 503 Service unavailable errors even though the file > does exist: That sounds to me like you did not restart apt-proxy after making the=20 configuration file updates. =A0Could that be your problem? Chris |
|
From: Bram M. <bra...@li...> - 2005-06-18 08:44:21
|
Chris Halls wrote: [...] > That sounds to me like you did not restart apt-proxy after making the > configuration file updates. Could that be your problem? I did restart apt-proxy several times but apparantly not when I had made the correct adjustments... So here's the correct configuration: /etc/apt-proxy/apt-proxy-v2.conf: [debian-volatile] backends = ftp://volatile.debian.net/debian-volatile /etc/apt/sources.list: deb http://localhost:9999/debian-volatile testing/volatile main Followed by: /etc/init.d/apt-proxy restart Thanks for all the help! Bram -- # Mertens Bram "M8ram" <bra...@li...> Linux User #349737 # # debian testing kernel 2.6.8-1-686 i686 512MB RAM # # 10:40:03 up 84 days, 16:54, 6 users, load average: 0.23, 0.21, 0.11 # |
|
From: Bram M. <bra...@li...> - 2005-06-18 11:53:57
|
Chris Halls wrote: [...] > That sounds to me like you did not restart apt-proxy after making the > configuration file updates. Could that be your problem? I did restart apt-proxy several times but apparantly not when I had made the correct adjustments... So here's the correct configuration: /etc/apt-proxy/apt-proxy-v2.conf: [debian-volatile] backends = ftp://volatile.debian.net/debian-volatile /etc/apt/sources.list: deb http://localhost:9999/debian-volatile testing/volatile main Followed by: /etc/init.d/apt-proxy restart Thanks for all the help! Bram -- # Mertens Bram "M8ram" <bra...@li...> Linux User #349737 # # debian testing kernel 2.6.8-1-686 i686 512MB RAM # # 13:52:01 up 84 days, 20:06, 7 users, load average: 0.24, 0.11, 0.10 # |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X