Am Sonntag, 2. Juli 2017, 12:01:06 CEST schrieb Wolfgang Bauer:
> Am Sonntag, 2. Juli 2017, 11:06:23 CEST schrieb Mathias Homann:
> > ...actually... on KDE:Frameworks5 publishing is enabled for Leap 42.2.
> You are wrong, publishing is disabled:
> > Breaks installations on every 42.2 system that uses KDE:Frameworks5.
> It definitely didn't "break" mine... ;-)
> Actually, I saw no problem at all here.
> > Still, the general idea is right.
> Maybe it would also be good to disable *building* in KDE:Qt5 for Leap in
> such cases. I think that's how it was done in the past...
> This will prevent other repos already building against the new version (and
> publishing the packages) while KDE:Qt5 is not published yet.
Maybe it would be a good thing if the build service would look at the
"publish" setting of a repo to determine which version of the packages to use
for building against, in other repos?
There is an outstanding bug for 32-bit Tumbleweed (bsc#1046571) that prevents
the VirtualBox kernel modules from loading since the switch to gcc7. I have
fixed the code, built the packages locally using osc, and tested the new
versions. When I submit the build to OBS, it fails as follows:
[ 2585s] g++ -c -O2 -fPIC -g -pipe -Wshadow -Wall -Wextra
-Wno-missing-field-initializers -Wno-unused -Wno-trigraphs
-fdiagnostics-show-option -Wno-unused-parameter -Wlogical-op
-Wno-variadic-macros -Wno-long-long -Wunused-variable -Wunused-function
-Wunused-label -Wunused-parameter -Wno-overloaded-virtual -Wno-variadic-macros
-Wshadow -fshort-wchar -fpermissive -fexceptions -frtti -fomit-frame-pointer
-fmessage-length=0 -grecord-gcc-switches -O2 -Wall -D_FORTIFY_SOURCE=2
-fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables -g
-fno-omit-frame-pointer -fno-strict-aliasing -fvisibility-inlines-hidden
-fvisibility=hidden -DVBOX_HAVE_VISIBILITY_HIDDEN -DRT_USE_VISIBILITY_DEFAULT
-std=c++11 -fdollars-in-identifiers -m32
Job seems to be stuck here, killed. (after 28800 seconds of inactivity)
Until the switch to gcc7, these failures were disturbing, but now they prevent a
set of users from doing their work.
This issue has been filed as bsc#1046894.
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org