On Thu, 2015-05-07 at 14:12 +0200, Dimstar / Dominique Leuenberger wrote:
Christian,
On Thu, 2015-05-07 at 13:59 +0200, Christian Boltz wrote:
Hello,
I received a notice that the AppArmor packages don't build anymore in Factory because ruby can't be found.
The failure is caused by configure no longer finding ruby, however there is an IMHO more interesting error at the start of the build:
[ 297s] ----- building apparmor.spec (user abuild) [ 297s] --------------------------------------------------------- -- ------ [ 297s] --------------------------------------------------------- -- ------ [ 297s] + exec rpmbuild -ba --define '_srcdefattr (-,root,root)' - -nosignature --define '_build_create_debug 1' --define 'disturl obs://build.opensuse.org/openSUSE:Factory/standard/fa789611d9fa83a15aa4ca7fa4939a85-
apparmor' /home/abuild/rpmbuild/SOURCES/apparmor.spec [ 298s] sh: /usr/bin/ruby: No such file or directory [ 298s] sh: /usr/bin/ruby: No such file or directory [ 298s] sh: /usr/bin/ruby: No such file or directory [ 298s] Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.lmuznN
Note that the build ignores those error messages (not sure if they are harmless or critical) and continues.
Full build log: https://build.opensuse.org/package/live_build_log/openSUSE:Factory/ ap parmor/standard/x86_64
Is this something I need to fix in the AppArmor package, or will it fix itsself?
This morning, we checked in Ruby 2.2 as the new default version. The openSUSE:Factory project is very much in flux for this at the moment and will take a while to settle.
At this moment, I'd argue that there is no work needed by you - this should all settle down in time again (it did in Stagings after all).
Just as a follow-up: openSUSE:Factory/apparmor has successfully built
again.
--
Dimstar / Dominique Leuenberger