Yes, I have some published packages. The problem is that /srv/obs is a symlink to /obs. /etc/init.d/obsstoragesetup:128 seems to be the reason: echo "Looking for OBS Server LVM Volume" if [ -e /dev/OBS/server ]; then [ -L /obs ] && rm /obs [ -d /obs ] || { rm -f /obs; mkdir /obs ; } # this fails on a configuration with OBS-server lvm on sdb # [ -e /obs/repos ] || { ln -sf /obs/repos /srv/obs/repos ; } # using instead: [ -d $backenddir -a ! -L $backenddir ] && { rm -rf $backenddir ; } 128: [ -L $backenddir ] || { ln -sf /obs $backenddir ; } On 04/10/2012 03:30 PM, Adrian Schröter wrote:
Am Dienstag, 10. April 2012, 15:25:52 schrieb Gregor Dschung:
Hi.
The file dist/obs-apache2.conf from obs-server-2.2.131.tar.bz2, package obs-server, project openSUSE:Tools:Unstable is configured to use /srv/obs/repos for the repository vhost. In the appliance, this leads to the error "[Tue Apr 10 12:29:43 2012] [error] [client 10.136.17.142] Symbolic link not allowed or link target not accessible: /srv/obs" as /srv/obs is a symlink to /obs.
I guess, in the appliance this config file should be patched to use /obs/repos, so the appliance works out of the box?
Are you sure that you have already published a package ? or /src/obs/repos does not exist at all ...
Regards, Gregor
-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org