On 3/30/07, Travis Willard <travis@archlinux.org> wrote:
While harmless, I found this annoying after a while, so I whipped up a script to scan the DB for these discrepancies, collect a list of affected packages, then pacman -S them all to fix it up.
I've tested this script a few times on my own system, seems to do the job correctly, though one line is a bit of a hack. ;)
As always, "Use at your own risk!", although I think it's perfectly safe to use - the very worst I can imagine that can happen is that you'll reinstall a few packages you didn't need to.
As a side note. There was also an bug a while back that set all those lists to null (well, empty is a better word). I doubt anyone still has this problem, except for Roman (he did at one point) and myself. The packages fix themselves the same way, by reinstalling, but it's hard to detect.