[Bug 1135751] New: [Staging] apparmor fails to build against swig 4.0
http://bugzilla.opensuse.org/show_bug.cgi?id=1135751 Bug ID: 1135751 Summary: [Staging] apparmor fails to build against swig 4.0 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: AppArmor Assignee: suse-beta@cboltz.de Reporter: dimstar@opensuse.org QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- See bug 1135746: swig is being updated to version 4.0 apparmor is one of the packages failing to build in this setup https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:M... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1135751 Dominique Leuenberger <dimstar@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kkaempf@suse.com Blocks| |1135746 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1135751 http://bugzilla.opensuse.org/show_bug.cgi?id=1135751#c1 --- Comment #1 from Christian Boltz <suse-beta@cboltz.de> --- After (locally) patching apparmor.spec to display the content of test-suite.log -make check -C libraries/libapparmor +make check -C libraries/libapparmor || { cat libraries/libapparmor/swig/python/test/test-suite.log ; exit 42 ; } I see lots of errors similar to this one: [ 68s] ====================================================================== [ 68s] ERROR: test_testcase_syslog_truncate (__main__.AAPythonBindingsTests) [ 68s] test testcase_syslog_truncate [ 68s] ---------------------------------------------------------------------- [ 68s] Traceback (most recent call last): [ 68s] File "./test_python.py", line 141, in stub_test [ 68s] self._runtest(testname) [ 68s] File "./test_python.py", line 72, in _runtest [ 68s] record = self.create_record_dict(swig_record) [ 68s] File "./test_python.py", line 112, in create_record_dict [ 68s] value = record.__getattr__(key) [ 68s] AttributeError: 'aa_log_record' object has no attribute '__getattr__' -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1135751 http://bugzilla.opensuse.org/show_bug.cgi?id=1135751#c2 --- Comment #2 from Klaus Kämpf <kkaempf@suse.com> --- Hmm, I tried to build openSUSE:Factory:Staging:M/apparmor build failed, since it somehow requires kvm. Tried with kvm but ran into OOM (with 8G free !). Weird. Can someone attach full logs ? The build.log just shows the final error :-/ -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1135751 http://bugzilla.opensuse.org/show_bug.cgi?id=1135751#c3 --- Comment #3 from Christian Boltz <suse-beta@cboltz.de> --- Created attachment 806401 --> http://bugzilla.opensuse.org/attachment.cgi?id=806401&action=edit build log (In reply to Klaus Kämpf from comment #2)
Hmm, I tried to build openSUSE:Factory:Staging:M/apparmor build failed, since it somehow requires kvm. Tried with kvm but ran into OOM (with 8G free !). Weird.
Right, kvm is needed for building the precompiled cache files. I also hit the memory issue :-/ You'll need --vm-memory 512 and/or someone who fixes bug 1136803 (the current default seems to be 10 MB - maybe the oSC maintainer took your IoT talk too serious? ;-)
Can someone attach full logs ? The build.log just shows the final error :-/
Yes, of course. The attached file contains the build log including the content of libraries/libapparmor/swig/python/test/test-suite.log logfile (using the slightly modified spec from comment 1). -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1135751 http://bugzilla.opensuse.org/show_bug.cgi?id=1135751#c4 Christian Boltz <suse-beta@cboltz.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #4 from Christian Boltz <suse-beta@cboltz.de> --- Upstream bugreport (including some technical details): https://gitlab.com/apparmor/apparmor/issues/33 Upstream fix: https://gitlab.com/apparmor/apparmor/merge_requests/384 SR 707833 sent. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com