On Sun, Aug 1, 2010 at 11:14 AM, b1 <forum@b1online.de> wrote:
On Sat, 2010-07-31 at 11:06 -0700, b1 wrote:
On Sat, 2010-07-31 at 01:50 +0200, Sven-Hendrik Haase wrote:
On 30.07.2010 22:27, b1 wrote:
~~~~~~~~~~~~~~~~~~ Any help is greatly appreciated.
Thanks
Benedikt
Use the Arch install medium and its working pacman and set the install dir to your system. Assume your pacman database is corrupt as well so discard it. Reinstall at least base and base-devel into your mounted system from the live medium and copy the resulting db. This will only make pacman recognize packages contained in base and base-devel when you're booting back into your system but at least pacman will be working again.
-- Sven-Hendrik
Hello Sven
Thanks for your reply. I did what you suggested. I bootet the Arch linux live cd, removed the old databse, installed base and base-devel, copied the resulting db and rebooting. After readding users, adapting rc.conf and another reboot, I was able to log in. Now pacman -Syu works without errors (However has nothing to update at the moment, so I cant really tell).
However I also saved a complete list of packages before doing the live-cd thing, in order to restore them now. Unfortunatelly I once again ran into the problem. Many packages work just fine, however a
pacman -S pulseaudio
segfaults again, with the already known error message. Therefore I assumed it had something to do with my package cache. I did a
pacman -Scc
However no success. Still getting the segfault. Is there any other place pacman keeps information about packages like pulseaudio? Any ideas what I could do?
Anyone having any idea, what the problem might be? Again every hint is very appreciated.
Thanks
Benedikt
Ok, I nearly managed to restore all packages, however the following packages cause the segfault:
gstreamer0.10-pulse lib32-pulseaudio libquicktime pavucontrol pavumeter pulseaudio ttf-liberation
Interestingly the installation via pacman -fU URL succeeds and with pacman -fS PACKAGE fails.
Is there some debugging version of pacman? For use with gdb to track down the problem. Or do I have to compile it from source and if so, what flags do I have to set?
Compiling it from source is the easiest way. For flags, I'd use the PKGBUILD as an example of what you should pass to configure. Once built you can run it from the source tree (./src/pacman/pacman). -Dan