Bug#730846: gnupg2: FTBFS on mips, mipsel: gpg: Fatal: can't disable core dumps: Operation not permitted
* Salvatore Bonaccorso (car...@debian.org) wrote: > Hi Andreas, > > On Sat, Nov 30, 2013 at 08:04:22AM +0100, Andreas Beckmann wrote: > > Package: gnupg2 > > Version: 2.0.22-1 > > Severity: serious > > Justification: fails to build from source (but built successfully in the > > past) > > > > Hi, > > > > gnupg FTBFS on mips*: > > > > https://buildd.debian.org/status/fetch.php?pkg=gnupg2&arch=mips&ver=2.0.22-1&stamp=1381015396 > > > > [...] > > I'm not the maintainer, but just additional reference for this issues. > See also [1] for followups with wb-team with this issue on mips*. > > [1] http://lists.debian.org/debian-wb-team/2013/11/msg0.html Thanks Salvatore, I had not seen the two followups to this thread due to not being on debian-wb@. I think this is properly a buildd bug rather than a gnupg2 problem, so I'm going to reassign it. In the mean-time I'm going to disable the test-suite on mips and mipsel to temporarily work around the problem and get builds on those platforms going again. -- Eric Dorland ICQ: #61138586, Jabber: ho...@jabber.com signature.asc Description: Digital signature
Bug#730846: gnupg2: FTBFS on mips, mipsel: gpg: Fatal: can't disable core dumps: Operation not permitted
Control: reassign -1 buildd.debian.org
Control: severity -1 important
Control: retitle -1 mips, mipsel buildds: Unable to disable core dumps
As pointed out by Bastian Blank in <20131104203044.ga17...@mail.waldi.eu.org>:
> Turns out it does fail. There seems to be a kernel bug that makes it
> fails if anything tries to set a value of RLIM_INFINITY:
>
> | getrlimit(RLIMIT_CORE, {rlim_cur=0, rlim_max=RLIM_INFINITY}) = 0
> | setrlimit(RLIMIT_CORE, {rlim_cur=0, rlim_max=RLIM_INFINITY}) = -1
> | EPERM (Operation not permitted)
>
> Workaround is to also set the hard limit to a smaller value.
* Salvatore Bonaccorso (car...@debian.org) wrote:
> Hi Andreas,
>
> On Sat, Nov 30, 2013 at 08:04:22AM +0100, Andreas Beckmann wrote:
> > Package: gnupg2
> > Version: 2.0.22-1
> > Severity: serious
> > Justification: fails to build from source (but built successfully in the
> > past)
> >
> > Hi,
> >
> > gnupg FTBFS on mips*:
> >
> > https://buildd.debian.org/status/fetch.php?pkg=gnupg2&arch=mips&ver=2.0.22-1&stamp=1381015396
> >
> > [...]
>
> I'm not the maintainer, but just additional reference for this issues.
> See also [1] for followups with wb-team with this issue on mips*.
>
> [1] http://lists.debian.org/debian-wb-team/2013/11/msg0.html
>
> Regards,
> Salvatore
--
Eric Dorland
ICQ: #61138586, Jabber: ho...@jabber.com
signature.asc
Description: Digital signature
Bug#730846: gnupg2: FTBFS on mips, mipsel: gpg: Fatal: can't disable core dumps: Operation not permitted
On Sat, Nov 30, 2013 at 10:42:54PM -0500, Eric Dorland wrote:
> Control: reassign -1 buildd.debian.org
> Control: severity -1 important
> Control: retitle -1 mips, mipsel buildds: Unable to disable core dumps
>
> As pointed out by Bastian Blank in
> <20131104203044.ga17...@mail.waldi.eu.org>:
>
> > Turns out it does fail. There seems to be a kernel bug that makes it
> > fails if anything tries to set a value of RLIM_INFINITY:
> >
> > | getrlimit(RLIMIT_CORE, {rlim_cur=0, rlim_max=RLIM_INFINITY}) = 0
> > | setrlimit(RLIMIT_CORE, {rlim_cur=0, rlim_max=RLIM_INFINITY}) = -1
> > | EPERM (Operation not permitted)
> >
> > Workaround is to also set the hard limit to a smaller value.
>
All values equals or below 0x7ffe should work.
Note that this problem is being working on in the last few months, but
it involves a lot of people. The problem is an inconsistency in the
definition of RLIM64_INFINITY between kernel and userland. It has been
there for almost 7 years, but only really appeared when the prlimit64
syscall has been wired on the kernel side.
So far we have been able to agree that the problem should be fixed on
the glibc side. It has been fixed upstream, and the fix has been
backported in sid. However to get it fully fixed on the build daemons,
we also have to fix it in glibc/wheezy. An upload is currently being
prepared, then the step afterwards will be to get it installed on the
build daemons.
--
Aurelien Jarno GPG: 1024D/F1BCDB73
aurel...@aurel32.net http://www.aurel32.net
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#730846: gnupg2: FTBFS on mips, mipsel: gpg: Fatal: can't disable core dumps: Operation not permitted
Package: gnupg2 Version: 2.0.22-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Hi, gnupg FTBFS on mips*: https://buildd.debian.org/status/fetch.php?pkg=gnupg2&arch=mips&ver=2.0.22-1&stamp=1381015396 [...] Making all in tests make[3]: Entering directory `/«PKGBUILDDIR»/tests' Making all in openpgp make[4]: Entering directory `/«PKGBUILDDIR»/tests/openpgp' echo '#!/bin/sh' >./gpg_dearmor 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 make[4]: *** [pubring.gpg] Error 2 make[4]: Leaving directory `/«PKGBUILDDIR»/tests/openpgp' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/«PKGBUILDDIR»/tests' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/«PKGBUILDDIR»' make[1]: *** [all] Error 2 make[1]: Leaving directory `/«PKGBUILDDIR»' dh_auto_build: make -j1 returned exit code 2 make: *** [build-arch] Error 2 Cheers, Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#730846: gnupg2: FTBFS on mips, mipsel: gpg: Fatal: can't disable core dumps: Operation not permitted
Hi Andreas, On Sat, Nov 30, 2013 at 08:04:22AM +0100, Andreas Beckmann wrote: > Package: gnupg2 > Version: 2.0.22-1 > Severity: serious > Justification: fails to build from source (but built successfully in the past) > > Hi, > > gnupg FTBFS on mips*: > > https://buildd.debian.org/status/fetch.php?pkg=gnupg2&arch=mips&ver=2.0.22-1&stamp=1381015396 > > [...] I'm not the maintainer, but just additional reference for this issues. See also [1] for followups with wb-team with this issue on mips*. [1] http://lists.debian.org/debian-wb-team/2013/11/msg0.html Regards, Salvatore -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
