On Mon, Mar 9, 2009 at 6:44 PM, Tobias Powalowski <t.powa@gmx.de> wrote:
Am Montag 09 März 2009 schrieb Andreas Radke:
Am Mon, 09 Mar 2009 10:00:16 +1000
schrieb Allan McRae <allan@archlinux.org>:
Dan McGee wrote:
On Sun, Mar 8, 2009 at 4:44 AM, Tobias Powalowski <t.powa@gmx.de>
wrote:
Am Sonntag 08 März 2009 schrieb Andreas Radke:
This is a minor update to 1.12.2 - the major change I've done is the switch to --with-ipc=tcp communication way that should solve some issues that have come up with recent kde builds. please test if you can still build all your other stuff with it.
Attention: Please also take care off all packages that install files with setuid bit set. Take a look at http://bugs.archlinux.org/task/13444 !
I could not track down where the issue is and the upstream Debian developer can't reproduce it while Tpowa and some other could. Only x86_64 is affected and sometimes files with setuid set don't get that permission when the pkg gets installed.
-Andy
upstream changelog:
fakeroot (1.12.2) unstable; urgency=low
* Replace and (hopefully) fix broken alpha stat version hack in fts_read.
-- Clint Adams <schizo@debian.org> Sun, 01 Mar 2009 15:17:31 -0500
no signoff, i can'T build kernel and syslog-ng anymore, somehow it creates zombie processes on my system, downgrading to core fakeroot solved the issue.
Completely broken. I can't even make it through a build without fakeroot hanging and having to kill -9 the makepkg process.
Me too. I guess it is best to wait for the next pacman release to fix this as building can then be done outside the fakeroot.
Allan
I reverted back to use sysv ipc and added the README file + install msg about sysv/tcp usage.
Please signoff -2 release.
-Andy signoff works again to compile things :D greetings tpowa
Just out of curiosity, none of the devs are affected by the issues with fakeroot sysv ipc, as described here : http://bugs.archlinux.org/task/13375 ?