Your message dated Tue, 13 Oct 2015 07:47:20 +0200
with message-id <561c9ae8.2040...@debian.org>
and subject line Re: [pkg-apparmor] Processed: severity of 799449 is serious
has caused the Debian Bug report #799449,
regarding apparmor: FTBFS: test suite segfaults on mips and mipsel
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
799449: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799449
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: apparmor
Version: 2.10-2
Severity: important
https://buildd.debian.org/status/fetch.php?pkg=apparmor&arch=mips&ver=2.10-2&stamp=1442250379
https://buildd.debian.org/status/fetch.php?pkg=apparmor&arch=mipsel&ver=2.10-2&stamp=1442250826
I've reproduced these segfaults on the minkus.debian.org (mips) and
eder.debian.org (mipsel) porterboxes.
Note that:
* 2.10-1 built just fine on those architectures' buildds when that
package was uploaded to experimental.
* I tried building 2.9.2-3 on these two porterboxes => I see the same
segfault and FTBFS, and running ./parser/tst_regex by hand indeed
tells me: "zsh: segmentation fault ./parser/tst_regex"
=> so this looks like the breakage was triggered by some change in the
build environment, rather than in the source package itself. (Which
doesn't necessarily mean that the source package is innocent,
though :)
Could it be that there's some inconsistency between the version of
libapparmor we're building/linking the test programs against, and the
version we're running them with? The system's libapparmor1 (2.9.2-3),
has been built before the GCC-5 transition.
Cheers,
--
intrigeri
--- End Message ---
--- Begin Message ---
On 06.10.2015 21:40, Felix Geyer wrote:
> Control: tags -1 - help
>
> This issue is most likely caused by g++ bug #799811.
AppArmor built fine now on mips*, closing.
Felix
--- End Message ---
