Hello, Am Donnerstag, 27. Februar 2014 schrieb Christian Boltz: > this patch fixes test-aa-decode.py - it failed all tests because the > path to aa-decode was wrong. > > > === modified file 'utils/test/test-aa-decode.py' > --- utils/test/test-aa-decode.py 2012-11-06 01:27:20 +0000 > +++ utils/test/test-aa-decode.py 2014-02-27 20:10:20 +0000 > @@ -18,7 +18,7 @@ > # The locationg of the aa-decode utility can be overridden by setting > # the APPARMOR_DECODE environment variable; this is useful for > running # these tests in an installed environment > -aadecode_bin = "./aa-decode" > +aadecode_bin = "../aa-decode"
Hmm, that was too easy :-/ test-aa-decode.py is also called by "make check" (utils/Makefile), but as "test/test-aa-decode.py" - and if called this way, ./aa-decode is right because it has a different pwd. Looks like we should find a solution that works with make check _and_ a manual call ("./test-aa-decode.py"). Any ideas? Regards, Christian Boltz -- "Praktische Erfahrung ist viel Wert. Nur mal davon gehört zu haben, daß etwas nicht funktioniert, ist eine Sache - den GNOME Dateidialog selbst benutzt haben zu müssen, eine ganz andere." -- Steffen Winterfeldt -- AppArmor mailing list AppArmor@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/apparmor