On Sat, Aug 02, 2014 at 08:47:54AM +0200, Andreas Henriksson wrote: > There has been discussions about the use of mlock(all) and we have > over the past year not been able to reach a consensus. I don't > feel comfortable making the descision to rip out security features > on my own as proposed by porters and noone has been willing to take > the discussion upstream.
Why do you think this is related to the use of mlock? A quick check in the source shows that an error in mlock is not fatal. Also building on Linux with a locked memory limit of 0 does not trigger this error. But several lines below this warning in the build-log is the simple statement: | Build killed with signal TERM after 150 minutes of inactivity So you found yourself a dead lock. Did you ever try to run this on a kfreebsd-* porter machine? You completely forgot to actually mention what you tried and what you observed yourself. > If for some reason (a) is not possible, please tell me and I'll implement > (b). I would propose (c): understand the problem. Anyway, I did that for you. The problem lies within build/tap-driver, aka the tool that executes the tests. In some cases it misses EOF on stderr of the executed test program, I'm however not sure why. > For more background, see: > https://packages.qa.debian.org/libg/libgnome-keyring.html > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=628383 > https://packages.qa.debian.org/g/gnome-keyring.html > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750883 This misses a link to the build-log: https://buildd.debian.org/status/fetch.php?pkg=gnome-keyring&arch=kfreebsd-i386&ver=3.12.0-2&stamp=1398611094 As this is a simple bug, this is off-topic on debian-release. Bastian -- Earth -- mother of the most beautiful women in the universe. -- Apollo, "Who Mourns for Adonais?" stardate 3468.1 -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140802111814.ga29...@mail.waldi.eu.org
