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 |