* Bastian Blank (waldi@debian.org) wrote: > On Sun, Nov 03, 2013 at 04:53:39PM +0100, Thijs Kinkhorst wrote: > > >> > echo "../../g10/gpg2 --homedir . --no-options --no-greeting \ > > >> > --no-secmem-warning --batch --dearmor" >>./gpg_dearmor > > >> > chmod 755 ./gpg_dearmor > > >> > ./gpg_dearmor > ./pubring.gpg < ./pubring.asc > > >> > gpg: Fatal: can't disable core dumps: Operation not permitted > > >> > It did build fine for stable-security, by the way. > > >> > Can you check this out? > > - What does the maintainer of gnupg2 have to say about this error? The > kernel disallows this operation, why does gnupg2 don't want to live > after that? gpg unconditionally disables core dumps (presumably to protect against key material showing up in one). This doesn't really matter for the purposes of tests but there's no flag to disable this behavior and none of the other archs buildds have this restriction. > - What version of the gnupg2 package is this anyway? 2.0.22-1 > - Does it fail the same way on the developer machine? Nope. And it built on all the other architectures except for mips. > - Is any version built with LFS? buildd.d.o does not have any logs > available for any of the versions. What is LFS in this context? I see logs here: https://buildd.debian.org/status/package.php?p=gnupg2 > > > It seems to be at least a problem on lucatelli and rem. It worked on > > > corelli and eysler for the wheezy-security builds. > > > > > > For given back both squeeze-security missing builds, on mips it was > > > rescheduled on ball, but for mipsel again on rem. So don't know if we > > > will get at least one successfull build. > > What was the result? > > Bastian > -- Eric Dorland <eric@kuroneko.ca> ICQ: #61138586, Jabber: hooty@jabber.com
Attachment:
signature.asc
Description: Digital signature