On 9/19/07, François Charette <[EMAIL PROTECTED]> wrote:
> Thomas Bächler a écrit :
> > François Charette schrieb:
> >
> >> 1. "abs" creates new stuff under /var/abs/core/ for packages that also
> >> still exist under /var/abs/{base,daemon,system,etc} Why are the latter
> >> not deleted automatically?
> >> For example: I have both
> >> /var/abs/core/base/tar (ver 1.18-2)
> >> and /var/abs/base/tar (ver 1.18-1)
> >>
> >
> > abs never deleted anything, so this might have happened before, but you
> > didn't notice. You can delete them yourself to make it look clean again.
> >
>
> AFAIK it usually does delete outdated files and dirs at each checkout.The second comment here is correct. A lot of "half-answers" in this thread. The reason these extra files were not deleted in this case is because the supfile read by cvsup for these directories was deleted, so it doesn't know anything about them anymore. Obviously it would be bad news if it just deleted files it knew nothing about, so instead it leaves them. You can safely run "rm -rf /var/abs/*" if you want and get a fresh abs tree (if you have a local/ dir though, be sure to keep anything you need from that). > >> 3. Also the following command gives an error: > >> $ pacman -Sl current > >> error: repository "current" was not found. > >> even though there are still many entries under /var/lib/pacman/current > >> > > > > pacman doesn't delete the /var/lib/pacman/current directory on its own, > > even if you remove it from pacman.conf. It will simply ignore it, but > > you can delete it if you want. > > > > > > Perhaps a message during installation of next version of pacman would be > appropriate? This is such a minor detail that its not worth it. You can safely delete the entire /var/lib/pacman/* hierarchy WITH THE EXCEPTION OF THE 'local' DIRECTORY, as these are just sync DBs lying around. -Dan _______________________________________________ arch mailing list arch@archlinux.org http://archlinux.org/mailman/listinfo/arch
