On Tue, Aug 4, 2009 at 5:04 PM, Tobias Powalowski<[email protected]> wrote: > Am Dienstag 04 August 2009 schrieb Allan McRae: >> Dan McGee wrote: >> > On Sun, Aug 2, 2009 at 9:34 PM, Gerardo Exequiel >> > >> > Pozzi<[email protected]> wrote: >> >> Dan McGee wrote: >> >>> Signoff for pacman/makepkg 3.3.0. Notable things: >> >>> >> >>> * once this goes in, we can officially start doing split packaging and >> >>> build()/package() usage in our PKGBUILDs. >> >>> * this is basically a signoff for libfetch too, and you can remove >> >>> libdownload from your system. >> >>> >> >>> Allan (and others)- I added a carbon copy version of makepkg.conf to >> >>> SVN. Do we want to establish (1) Arch LDFLAGS or (2) Arch integrity >> >>> check policy? >> >>> >> >>> -Dan >> >> >> >> oops! >> >> >> >> pacman-3.3.0-1-i686 : makepkg.conf looks bad >> >> >> >> CARCH="x86_64" >> >> CHOST="x86_64-unknown-linux-gnu" >> >> >> >> CFLAGS="-march=x86-64 -mtune=generic -O2 -pipe" >> >> CXXFLAGS="-march=x86-64 -mtune=generic -O2 -pipe" >> > >> > Whoops! I'll see if I can't fix that here and repackage... >> >> Signoff 3.3.0-2 for both. Upgrade went fine and I can still build and >> install packages... >> >> Allan > Hrm got a segfault while updateting to kde 4.3 was a large amount of > packages, after rerunning pacman -Syu all went fine, don't know it this is a > serious thing.
You don't happen to have a core dump, do you? :P Any indication when it failed? During download, during install, etc. We have seen some segfault behavior in the past during download, but it has been a long time since pacman died during the actual package install process. -Dan
