[arch-dev-public] [Bug] db-scripts fail to remove split package
aaronmgriffin at gmail.com
Mon Jun 21 14:39:12 EDT 2010
On Sat, Jun 19, 2010 at 7:27 AM, Pierre Schmitz <pierre at archlinux.de> wrote:
> On Sat, 19 Jun 2010 14:09:40 +0200, Thomas Bächler <thomas at archlinux.org>
>> I made this change to the kernel26 PKGBUILD:
>> However, db-testing fails to remove the kernel26-firmware package. I
>> need to remove it manually.
> At first: Please use the bug tracker.
> db-update cannot know about this change. It only adds packages to the
> repo. And I don't think it would be the right place to implement this as it
> would need to scan all packages on every update for the same pkgbase and
> see if it is still present in the PKGBUILD.
> The ftpdir-cleanup cron only removes packages that are no longer in the
> package db; but it does not remove packages from the db itself. It could be
> implemented here, but it would increase the already quite long runtime of
> that cron.
> So if you remove split packages in the PKGBUILD you also have to remove it
> from the db. Maybe someone could write a patch for check_packages.py to
> detect such orphaned packages.
> My suggestion: Packages should be removed only manually from the DB. But
> the check-script could be enhanced to detect such packages.
This is how it was intended: removing packages requires db-remove.
In order to do it any other way, we would need to scan all PKGBUILDs
(we do this in the cleanup script already, I think), grab the split
names + versions, and then remove those items from a list of
everything in the dir. Anything remaining gets db-removed.
It sounds tedious and messy though
More information about the arch-dev-public