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.
>
>> 2. Many installed packages that I have under
>> /var/abs/{base,daemon,system,etc} are no longer in pacman's database.
>> For example:
>> $ pacman -Q acpi
>> acpi 0.09-1
>> but
>> $ pacman -Ss ^acpi$
>> yields nothing!
>> Same thing for a bunch of other basic packages: acpid, apache, alsa-lib,
>> alsa-oss, alsa-utils, etc etc
>>
>
> All those packages are in the extra repository now. Make sure you use
> the same mirror for both core and extra, and maybe wait another day for
> your mirror to sync.
>
You're right, I had a different mirror for extra. Should have thought
about it...
Now everything is "in sync" again!
>> 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?
_______________________________________________
arch mailing list
[email protected]
http://archlinux.org/mailman/listinfo/arch
