On 18.03.2015 08:58 AM, Mihai Moldovan wrote:
Since we provide openSUSE/SLE builds the situation has slightly changed. The obs-build scripts runs rpmlint at end of build and IIRC that required a change in build-deps, pulling in other X2Go components at build time.
Please go ahead and add X2Go's own builds into the build process as available dependencies. OK, will do. Thanks.
I have added the functionality and put it into production.
With quite some nasty workarounds for mock...
I have also created /home/_x2go_shared_ with x2go-admin being the owner and this directory being world-readable. It contains another directory mock-config.
I have created symlinks $HOME/mock-config to /home/_x2go_shared_/mock-config for users x2go-admin and jenkins.
I have added (empty) "extras" repositories for fedora 20, 21 and rawhide, because they are now referenced for everything.
I will still need to write up automatic mock config file creation stuff (and probably remove /home/_x2go_shared_ and replace $HOME/mock-config with real directories, to which the automatically generated configs are written), because manually creating 4 config files for each arch and distribution and version (so 4 * #distros * #arches files) is a huge waste of time.
It's also more complicated to implement, so I leave that "for a later date".
At the same time, I have fixed x2gomatebindings and used this as a test of the deployed changes. It generally seems to work fine, but has sparked a bug in x2goserver, discovered while building OpenSUSE 13.2 packages:
[ 40s] Preparing...
########################################
[ 40s] file /etc/sudoers.d conflicts between attempted installs of
x2goserver-4.1.0.0-0.0x2go1.0.git20150316.1268.heuler.x86_64 and
sudo-1.8.10p3-2.1.6.x86_64
[ 41s] exit ...
This is why one should *never* own files or directories that are owned by other packages, even if it is convenient, "happens to work" and mock is less strict about it.
Luckily, the fix is easy and I'll implement it "tomorrow".
All this said, the changes are still pretty new and untested for all the other packages. Please note that build failures due to this are to be expected - both real ones as well as false positives (i.e., bugs in packages, but not the build script.) I'll fix those along the way.
Mihai