Menu
▾
▴
apt-proxy-users
|
From: mi <mic...@gm...> - 2004-01-19 19:54:04
|
Hello. I'm new on this list, and i didn't even read any mails from you.I subscribed because i recently decided to test apt-proxy 1.3.6 on my little home network of one PC and several laptops; and i have some questions. My boxes are all Debian 3.0r2 GNULinux, connected via standard ether100mbit, but the apt-proxy server host is on a slow dial up modem (around 6KByte/s). * When ditching a whole section (e.g., changing 'security stable/updates' to 'security woody/updates') or upgrading to a new dist-release (e.g. from woody to sarge), can i delete all related files in the cache manually ? * Can i delete the dkg-name.links directory which apt-proxy-import creates (containing links to apt cache) manually ? * I suppose, it's doing 'update packages list' from a LAN client, when the proxy is _not_ online, which left stuff like this in the packages cache: ls -l /var/cache/apt-proxy/debian/dists/woody/main/binary-i386/ -rw-r--r-- 1 aptproxy nogroup 6,3M 2004-01-15 03:42 Packages -rw-r--r-- 1 aptproxy nogroup 1,7M 2003-11-20 19:17 Packages.gz -rw-r--r-- 1 aptproxy nogroup 0 2004-01-19 04:30 Packages.gz.fail -rw-r--r-- 1 aptproxy nogroup 95 2003-11-20 19:57 Release -rw-r--r-- 1 aptproxy nogroup 0 2004-01-19 04:30 Release.fail Is there any problem with this ? tia ! -- mi. |
|
From: Chris H. <ha...@de...> - 2004-01-20 09:03:27
|
Hi, On Mon, 2004-01-19 at 20:53, mi wrote: > * When ditching a whole section (e.g., changing 'security > stable/updates' to > 'security woody/updates') or upgrading to a new dist-release > (e.g. from woody to sarge), can i delete all related files in > the cache manually ? Yes, that's fine. a-p will happily reconstruct anything it needs, as long as you don't remove the /var/cache/apt-proxy directory itself (which it doesn't have permission to recreate). > * Can i delete the dkg-name.links directory which apt-proxy-import creates > (containing links to apt cache) manually ? Yes. Normally it would be deleted anyway (maybe it was interrupted)? > * I suppose, it's doing 'update packages list' from a LAN client, when > the proxy > is _not_ online, which left stuff like this in the packages cache: > > ls -l /var/cache/apt-proxy/debian/dists/woody/main/binary-i386/ > -rw-r--r-- 1 aptproxy nogroup 6,3M 2004-01-15 03:42 Packages > -rw-r--r-- 1 aptproxy nogroup 1,7M 2003-11-20 19:17 Packages.gz > -rw-r--r-- 1 aptproxy nogroup 0 2004-01-19 04:30 > Packages.gz.fail > -rw-r--r-- 1 aptproxy nogroup 95 2003-11-20 19:57 Release > -rw-r--r-- 1 aptproxy nogroup 0 2004-01-19 04:30 Release.fail > > Is there any problem with this ? Not really. It will eventually clean the files up, but you can clean them by hand too, if you want. If you're just starting out with apt-proxy, you might want to try the python rewrite, which is available from experimental and is much quicker than v1. Chris |
|
From: mi <mic...@gm...> - 2004-01-20 14:52:42
|
Chris Halls wrote: >>* Can i delete the dkg-name.links directory which apt-proxy-import creates >> (containing links to apt cache) manually ? > Yes. Normally it would be deleted anyway (maybe it was interrupted)? ok. I used a-p-import two times, one with 'debug' option and one without any option, and both times it created the link dir without removing it. Would there be a problem if unattached links pile up there, after cleaning the apt-cache ? It's a-p-import 1.16.2.2 2002/11/15, and i run Debian Woody 3.0r2. >>ls -l /var/cache/apt-proxy/debian/dists/woody/main/binary-i386/ >>-rw-r--r-- 1 aptproxy nogroup 6,3M 2004-01-15 03:42 Packages >>-rw-r--r-- 1 aptproxy nogroup 1,7M 2003-11-20 19:17 Packages.gz >>-rw-r--r-- 1 aptproxy nogroup 0 2004-01-19 04:30 >>Packages.gz.fail >>-rw-r--r-- 1 aptproxy nogroup 95 2003-11-20 19:57 Release >>-rw-r--r-- 1 aptproxy nogroup 0 2004-01-19 04:30 Release.fail >> Is there any problem with this ? > Not really. It will eventually clean the files up, but you can clean > them by hand too, if you want. ok. I just see a-p creates a 'packages.gz' as well as a 'packages' by default, when updating from the net. Why redundancy ? One more question, for gnome2.2 backport i got a 'Release.nonexist'. Is this a problem somehow ? I mean, there must be some good reason for a release file ? Package download to clients seem to work, though. > If you're just starting out with apt-proxy, you might want to try the > python rewrite, which is available from experimental and is much quicker > than v1. ok, but what do you mean with experimental ? Debian Sid ? I don't want to ditch woody/stable, hopefully a-p-2 runs under woody as well ? Will i have to do something for a smooth transfer ? I'll look for the a-p website, anyway. > Apt-proxy-users mailing list > Apt...@li... > https://lists.sourceforge.net/lists/listinfo/apt-proxy-users You should add the website here.... for now i have to google ;-) Thanks for reply. -- mi. |
|
From: Chris H. <ha...@de...> - 2004-01-20 15:08:58
|
On Tue, 2004-01-20 at 15:52, mi wrote:
> Chris Halls wrote:
> >>* Can i delete the dkg-name.links directory which apt-proxy-import creates
> >> (containing links to apt cache) manually ?
> > Yes. Normally it would be deleted anyway (maybe it was interrupted)?
> ok.
> I used a-p-import two times, one with 'debug' option and one without
> any option,
> and both times it created the link dir without removing it.
That's odd. The code only leaves the directory if the DEBUG variable is
set:
# remove directory if not debugging
[ -z "$DEBUG" ] && rm -rf "$APT_PROXY_CACHE/dpkg-name.links/"
> Would there be a problem if unattached links pile up there,
> after cleaning the apt-cache ?
No because that directory is only used by a-p-i
> > Not really. It will eventually clean the files up, but you can clean
> > them by hand too, if you want.
> ok.
> I just see a-p creates a 'packages.gz' as well as a 'packages' by
> default, when updating from the net.
> Why redundancy ?
If you are using an rsync backend, it is more efficient to rsync
'Packages', so it does that, and then uses gzip to make a Packages.gz to
send to clients.
> One more question, for gnome2.2 backport i got a 'Release.nonexist'.
> Is this a problem somehow ? I mean, there must be some good reason for
> a release file ?
> Package download to clients seem to work, though.
It's not a big problem - a Release file contains extra information about
a backend but is not essential. a-p cache's the fact that the Release
file does not exist so it does not have to try the backend too
frequently.
> > If you're just starting out with apt-proxy, you might want to try the
> > python rewrite, which is available from experimental and is much quicker
> > than v1.
> ok, but what do you mean with experimental ? Debian Sid ?
No, see:
http://www.de.debian.org/doc/developers-reference/ch-resources#s-experimental
> I don't want to ditch woody/stable, hopefully a-p-2 runs under woody
> as well ?
Oh, it needs twisted, which was not available in Woody, so no you can't
use it I'm afraid.
> Will i have to do something for a smooth transfer ?
ap2 does have upgrade scripts and should automatically update for you,
but it needs more testing.
> I'll look for the a-p website, anyway.
That's a little out of date at the moment.
> > Apt-proxy-users mailing list
> > Apt...@li...
> > https://lists.sourceforge.net/lists/listinfo/apt-proxy-users
> You should add the website here.... for now i have to google ;-)
http://apt-proxy.sf.net
I don't have control over the footer mails added by the sourceforge
mailing list software, sorry.
Chris
|
|
From: mi <mic...@gm...> - 2004-01-21 03:42:17
|
Chris Halls wrote: > That's odd. The code only leaves the directory if the DEBUG variable is > set: > # remove directory if not debugging > [ -z "$DEBUG" ] && rm -rf "$APT_PROXY_CACHE/dpkg-name.links/" I do much configurating these days, andI can't remember every detail. Maybe i made it 'DEBUG=false' instead of unsetting it correctly. I am not sure. > If you are using an rsync backend, it is more efficient to rsync > 'Packages', so it does that, and then uses gzip to make a Packages.gz to > send to clients. ok. It would be nicer though, to have no reminents. Not only a question of style. I discovered some problems with relicts on standard office apps in the past. At least, debugging becomes easier without them... > It's not a big problem - a Release file contains extra information about > a backend but is not essential. a-p cache's the fact that the Release > file does not exist so it does not have to try the backend too > frequently. What backend do you mean ? In debian main it says for my system: >> Archive: stable Version: 3.0r2 Component: main Origin: Debian Label: Debian Architecture: i386 << >>>If you're just starting out with apt-proxy, you might want to try the >>>python rewrite, which is available from experimental and is much quicker >>>than v1. I would like to. v1 seems to be significant slower than pure apt here. Approx. ø 4 K instead of 5,5. It's obvious when i download a large package. So it's probably not the rsync thing slowing it down ? But what's the difference. I use the same packet sources as before, of course. However, i cannot install the recommended 'stat' package. It breaks coreutils, which is left from a little excursion to sarge last year. Don't ask me how it is possible to have debianutils and coreutils installed the same time. It makes doing anything on either of both packages impossible, because they altogether include some same files, and both are essential, so won't remove the other. I'm clueless at the moment. >>I don't want to ditch woody/stable, hopefully a-p-2 runs under woody >>as well ? > Oh, it needs twisted, which was not available in Woody, so no you can't > use it I'm afraid. I just have found and installed twisted 0.15.5-1 on a 3.0r1 CD. It also installed the by now missing: python-tk 2.1.3-3.2 blt 2.4u-7 blt-common 2.4u-7 tix41 4.1.0.7-4.1 Do you think this is sufficient to run ap2 ? And if so, where would i download it ? I've no experience with cvs. I couldn't find any version 2.x -- or maybe it's still 1.x ? I found a tarball in a cvs branch. No version number. I think it wasn't the right one. The config template is full of rsync. And the README says: >> Sat Dec 8 23:37:40 CET 2001 Jan-Benedict Glaw <jb...@lu...> << He says he started ap2. I remember some people mentioned in the docs so far, Rusty Russel, Manuel Estrada Sainz, Chris Halls. But why isn't JB Glaw mentioned on the apt-proxy website ? No it's definteley very old. Can you give me the right URL ? I also became unsure about the official name. Is it 'apt-proxy' or 'ap2' or 'HEAD' ? Perhaps you can help me clear my 'personal cache' here ;-) > ap2 does have upgrade scripts and should automatically update for you, > but it needs more testing. Does it change the cache structure ? -- mi. |
|
From: Chris H. <ha...@de...> - 2004-01-26 08:55:32
|
On Wed, 2004-01-21 at 04:42, mi wrote: > Chris Halls wrote: > > If you are using an rsync backend, it is more efficient to rsync > > 'Packages', so it does that, and then uses gzip to make a Packages.gz t= o > > send to clients. > ok. It would be nicer though, to have no reminents. Not only a=20 > question of style. > I discovered some problems with relicts on standard office apps in the=20 > past. > At least, debugging becomes easier without them... Let me try again. You _need_ a 'Packages' file to rsync with the backend. You _need_ a 'Packages.gz' file to send to clients that request it. If you delete one of them you have to waste CPU recreating it later and apt-proxy becomes even slower than it already is. It's a CPU/disk space tradeoff and since this is supposed to be a package cache, you are more likely have a few MB disk space to spare than CPU cycles to waste. > > It's not a big problem - a Release file contains extra information abou= t > > a backend but is not essential. a-p cache's the fact that the Release > > file does not exist so it does not have to try the backend too > > frequently. > What backend do you mean ? Whichever backend you were talking about in the first place. > In debian main it says for my system: Great, now it is available. At the time the Release.fail was created, it was not reachable for whatever reason. > >>>If you're just starting out with apt-proxy, you might want to try the > >>>python rewrite, which is available from experimental and is much quick= er > >>>than v1. > I would like to. v1 seems to be significant slower than pure apt here.=20 > Approx. =F8 4 K instead of 5,5. > It's obvious when i download a large package. So it's probably not the=20 > rsync thing slowing it down ? You will get better throughput if you don't use the rsync protocol.=20 Actually, apt-proxy is the most efficient for large packages normally, since it just lets the slave program (wget or rsync) transfer the file from the internet to disk, and forwards it on to the clients. > But what's the difference. I use the same packet sources as before, of=20 > course. > However, i cannot install the recommended 'stat' package. You only need to worry about 'stat' on a plain woody system - it is part of later versions of the coreutils package. > >>I don't want to ditch woody/stable, hopefully a-p-2 runs under woody=20 > >>as well ? > > Oh, it needs twisted, which was not available in Woody, so no you can't > > use it I'm afraid. > I just have found and installed twisted 0.15.5-1 on a 3.0r1 CD. > It also installed the by now missing: > python-tk 2.1.3-3.2 > blt 2.4u-7 > blt-common 2.4u-7 > tix41 4.1.0.7-4.1 > Do you think this is sufficient to run ap2 ? I'm afraid twisted had too many bugs until about version 0.99, so you need to satisfy the dependency of twisted >=3D 1.0.0, which is very difficult on Woody. > And if so, where would i download it ? The same as all other experimental packages. You can find it by going to http://packages.debian.org/apt-proxy and choosing the experimental version. > I've no experience with cvs. I couldn't find any version 2.x -- or=20 > maybe it's still 1.x ? It is numbered 1.9.7 since 2.0 will be the first official stable release. > I found a tarball in a cvs branch. No version number. I think it=20 > wasn't the right one. > The config template is full of rsync. And the README says: > >> > Sat Dec 8 23:37:40 CET 2001 > Jan-Benedict Glaw <jb...@lu...> > << > He says he started ap2. I remember some people mentioned in the docs=20 > so far, > Rusty Russel, Manuel Estrada Sainz, Chris Halls. > But why isn't JB Glaw mentioned on the apt-proxy website ? That is not directly related to apt-proxy. He started a rewrite a long time ago but it did not get very far feature wise and I think he might have abandoned it. > I also became unsure about the official name. Is it 'apt-proxy' or=20 > 'ap2' or 'HEAD' ? It is version 2 of apt-proxy, which Manuel & I often abreviate to ap2.=20 It isn't in CVS HEAD at the moment - that is still version 1. > > ap2 does have upgrade scripts and should automatically update for you, > > but it needs more testing. > Does it change the cache structure ? No, you should be able to run the older and the newer version using the same cache. It adds some extra database files, but these are ignored by version 1. Chris |
|
From: mi <mic...@gm...> - 2004-01-27 08:58:02
|
Chris Halls wrote: > No, you should be able to run the older and the newer version using the > same cache. It adds some extra database files, but these are ignored by > version 1. that's good to hear. > twisted >=1.0 upgrading is no minor task for me. but it should be done someday anyway. thank you for reply -- mi. |
×
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