Re: [Apt-proxy-users] Keeping cache clean under various circumstances

[mi <mic...@gm...>]

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.