Re: rpm package caching

Current should not cache any packages between database creates as of
1.0.2; it doesn't have enough intelligence to do so.  The top few things
that come to mind to check are:
        1) Make sure you turned the service off when you recreated the
DB.
        2) check for any stale / stray symlinks
        3) check to make sure you actually deleted the RPM - I often get
annoyed when I rm something, it asks me to confirm, and I just blindly
go on typing, and it never actually deletes that file.

        The only 'caching' Current does is creating symlinks somewhere
in the db_dir tree at DB creation time which reference the actual
packages, and writing out the gzipped header for each of the RPMS again
within the db_dir tree somewhere.

On Sat, 13 Apr 2002, Ray Kimsey wrote:

> I seem to be missing something.  I set up a current server a while back
> and it was working fine until I added a rpm package by mistake.  It was
> a non RH package that I did not want added.  I removed the package from
> the RPM directory (and from the whole system) but everytime I run the
> cadmin create command, the package shows up in the database directory.
> New servers then try to down load it.  I have remove the current db
> directory and it still shows up.  How do you get rid of it? Where is the
> info being cached?
> 
> Thanks for any ideas and thank you for the software!
> 
> Ray
> 
> _______________________________________________
> Current-server mailing list
> [email protected]
> http://lists.dulug.duke.edu/mailman/listinfo/current-server

-- 
Thank you,
John Berninger

Systems Administrator		[email protected]
Department of Mathematics	Box 8205, Harrelson Hall
NC State University		Raleigh, NC 27695
Phone:  (919)515-6315		Fax:	(919)515-3798

GPG Key ID: A8C1D45C
        Fingerprint: B1BB 90CB 5314 3113 CF22  66AE 822D 42A8 A8C1 D45C
--