-
Notifications
You must be signed in to change notification settings - Fork 669
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
master/edge: Linux builds would break without intrusive patching #5957
Comments
@jnweiger Since when does this fail btw? Is it indirectly related to your NSIS changes? (even though it's Linux not Windows) |
I don't see any changes on my side. The relevant files debian.control, *.dsc, *.spec are identical in the 2.3.3 and 2.4.0 templates. Hard to tell since when it is broken. OBS does not archive any build logs. Manual bisecting needed to find out. This is where the log between nightly and edge differs:
edge:
The former is non-fatal, the later is fatal. |
Seems some remainders of QT4 compatibility got removed in master:
AFAIK we have to build nautilus and nemo plugins and friends with system QT. |
@jnweiger But that BUILD_WITH_QT4 was already in April in 9aeb587 by @ogoffart .. are you sure those master nightlies did not work since April?
I don't know how this works in the OBS magic, should be @dschmidt or maybe @ogoffart that could know |
nautilous and nemo plugin don't depend on Qt. |
error in Leap 42.2 (system libQt5Core5-5.6.1-2.1 installed at build time) :
|
error in Ubuntu 16.04 (no system qt installed at build time):
|
error in Ubuntu 16.04 (system libqt5core5a-5.5.1 enforced at build time):
|
@jnweiger I thought we should always use our own oc-qt562 package? |
@guruz yes, 9aeb587 killed the overlays. cmake .. -DBUILD_CLIENT=OFF -DBUILD_SHELL_INTEGRATION=ON ... cannot survive with the current QtVersionAbstraction.cmake |
Yes, that sounds sensible |
Workaround with a packaging.diff Nightly master happily builds: @guruz & team: please review the packaging.diff here. |
Even though it might work, the https://gitea.int.owncloud.com/ownbrander/scripting/src/master/client/linux/templates/client/2.4.0/@LINUX_PACKAGE_SHORTNAME@-client/packaging.diff looks quite ugly :( So there is two build modes now? Is this really what you intended like this @ogoffart ? Why is executableVersionOutput moved? Can we "upstream" this... |
One question I can answer: executableVersionOutput() generates the blurb text for the gui client. We also want to have the same blurb text printed with owncloudcmd --version The method is originally found in src/gui/application.cpp which is not part of owncloudcmd. @dschmidt first moved it to src/libsync/utility.cpp which is easily accessible in both gui and cmd client. A much saner version was https://gitea.int.owncloud.com/ownbrander/scripting/src/d9a95f80fb9c3a217042638e6fd06e535353074f/client/linux/templates/client/2.4.0/@LINUX_PACKAGE_SHORTNAME@-client-overlays-dolphin/packaging.diff |
Maybe this answers the 'Mode' question: We use the same CMakeList.txt files for multiple build targets
|
@dschmidt why is our GIT_SHA specfied as "HACK FIXME" ? |
I'm looking at upstreaming the patches. |
@jnweiger Looking at packaging.diff I'm wondering whether the admin subdirectory was removed from cmake intentionally |
I answered the admin/ thing on the PR, @jnweiger pls comment. |
Merged! |
https://build.opensuse.org/public/build/isv:ownCloud:testpilot:edge/xUbuntu_16.10/i586/testpilotcloud-client-overlays/_log
I don't see any obvious changes in the client sources so it must have been from the OBS templates? Or the underlying OBS Qt or?
Detected first as QtWebKit problem in #5945 (comment)
The text was updated successfully, but these errors were encountered: