You are not logged in.
Why the extra effort in this case? One could pacman -Sd or pacman -Sud, no?
It depends on whether you care about having a slightly broken db or not (use testdb to find out).
It's probably not that bad, especially if you're aware of it.
pacman roulette : pacman -S $(pacman -Slq | LANG=C sort -R | head -n $((RANDOM % 10)))
Offline
Yeah that's the thing..I for one, am one of those that don't care much about what's on the surface. After all, real dependencies are satisfied by the files which are involved.
But for the rest of the crowd, it won't be too difficult to resolve either. Like you mentioned earlier, not many packages are affected. testdb shows about 10, so all's well
I need real, proper pen and paper for this.
Offline
First do a quick check:
$ pacman -Qi freetype2-ubuntu | grep Prov Provides : freetype2 2.3.5
And a sanity check:
$ grep prov /var/abs/local/freetype2-ubuntu/PKGBUILD provides=('freetype2 2.3.5')
Then do a reinstall:
pacman -Rd freetype2-ubuntu cd /var/abs/local/freetype2-ubuntu makepkg -fi --asroot
thanks for the help. but how should I actually edit the pkgbuilds?
Last edited by bionnaki (2008-01-20 20:57:17)
Offline
pacman 3.1.1 is in testing now. If all goes well, it will soon be in core, and then the packagers will be able to update their problematic packages.
Once you are on 3.1.1, use the following syntax for your own PKGBUILD :
provides=('freetype2=2.3.5')
pacman roulette : pacman -S $(pacman -Slq | LANG=C sort -R | head -n $((RANDOM % 10)))
Offline