Hi all,
build.o.o and api.o.o is up, but even after restarting my scheduler
I'm still getting:
retrying watcher for https://api.opensuse.org/public
setting up watcher for https://api.opensuse.org/public, start=22519717
2011-07-31 14:29:46: waiting for an event...
response from watcher for https://api.opensuse.org/public
400 remote error: remote error no socket attached
retrying in 60 seconds
which is breaking any builds that go through the 'openSUSE.org' remote project.
it's also preventing me from using osc build...
Is it something on my end?
--
later, Robert Xu + rxu AT lincomlinux DOT org
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi OBSers,
Last week I played with the current obs unstable version and used the
LXC build backend.
In this course I was stumbling over some problems, so to make it easier
for people, I document my findings in this OBS LXC HowTo
Hint: to build with LXC without all the OBS magic, you just run
osc build --vm-type=lxc
on any OBS checkout. Good for testing & debugging.
First, when you just install the obs-worker package or the
worker-appliance, it lacks the LXC user-space tools, complaing about not
finding lxc-create.
LXC also needs the special cgroup pseudo-fs mounted to work.
So you need to run once as root:
zypper -n install lxc
mkdir -p /var/lib/lxc /cgroup
echo none /cgroup cgroup defaults 2 0 >> /etc/fstab
mount /cgroup
echo mount /cgroup >> /etc/init.d/boot.local
# note: openSUSE's /etc/init.d/boot.cgroup did not help for me
To make OBS build with it, you then
edit /etc/sysconfig/obs-worker
OBS_VM_TYPE="lxc"
This allows to build most (>95%) packages alright and if it works for
you or if you are reading this after below fix went upstream, you can
stop here.
However I found some packages failing for two different reasons.
One reason is that packages like udev and mdadm contain device nodes and
the /usr/lib/build/lxc.conf forbids most operations on devices.
This results in failure messages like
Preparing packages for installation...
mdadm-3.0.3-0.22.4
error: unpacking of archive failed on file
/lib/udev/devices/md0;4e311c7f: cpio: mknod failed - Operation not permitted
The other problem I encountered is with packages like yast2-core and
perl-IO-Tty that run testsuites as part of their build script and
complain about openpty failing.
To fix both those problems, I needed to add these lines to
/usr/lib/build/lxc.conf :
# allow to create any device nodes - but not access
lxc.cgroup.devices.allow = c *:* m
lxc.cgroup.devices.allow = b *:* m
# /dev/pts/*
lxc.cgroup.devices.allow = c 136:* rw
lxc.tty = 1
but since this file would be replaced on next update of the "build" rpm,
those need to be added to the package by the maintainer.
I also added this line to lxc.conf:
# forbid dangerous operations
lxc.cap.drop = sys_module sys_boot sys_rawio sys_time net_raw
but I am not sure if all of them are needed.
Finally I want to thank Dinar for his work on LXC and to Adrian and all
the others making OBS as good as it already is.
Ciao
Bernhard M.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/
iEYEARECAAYFAk4xMI0ACgkQSTYLOx37oWTpVgCgh2UaE9gCjPt7Ysh8nWJiTtgm
L6QAoOAx1MrXMgogXHTZQwnG/AurYEJZ
=X9g/
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
they will pick up building in a few hours again.
darix
--
openSUSE - SUSE Linux is my linux
openSUSE is good for you
www.opensuse.org
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi all,
My local scheduler that was processing builds just started freaking
out with 404 errors...
Did something happen? (besides the fact that build.o.o and api.o.o
just went down from my end)
--
later, Robert Xu + rxu AT lincomlinux DOT org
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi all,
Can someone explain how this mechanism works?
I tried to do the following:
project A is linked to project B.
but then on project B I get all the packages of project A in "excluded".
/me is confuzzled.
--
later, Robert Xu + rxu AT lincomlinux DOT org
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi,
last week the MeeGo OBS went off (for quite while) without any warning
sent neither during the stop period or after the issue had been recovered.
I discovered a few day later that some of my project which where
building against remote repo sitting on MeeGo OBS were locked on a
strange status api.meego.com time out.
The only way to get out of that error is to trigger a rebuild which must
either be done for each packages in error (about 300) or for the full
project via osc (with the consequence of a large rebuilding ~1300 packages).
It would be nice that :
- in the monitor status report such connectivity error with linked OBS.
- get a smooth way to restart (ideally automatically)
Regards
--
Dominig ar Foll
MeeGo TV
Open Source Technology Centre
Intel SSG
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi,
last week the MeeGo OBS went off (for quite while) without any warning
sent neither during the stop period or after the issue had been recovered.
I discovered a few day later that some of my project which where
building against remote repo sitting on MeeGo OBS were locked on a
strange status api.meego.com time out.
The only way to get out of that error is to trigger a rebuild which must
either be done for each packages in error (about 300) or for the full
project via osc (with the consequence of a large rebuilding ~1300 packages).
It would be nice that :
- in the monitor status report such connectivity error with linked OBS.
- get a smooth way to restart (ideally automatically)
Regards
--
Dominig ar Foll
MeeGo TV
Open Source Technology Centre
Intel SSG
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
Hi,
We plan to split out the hermes database from the build service mysql during
the weekly maintenance window. If possible we will also move hermes to its
own instance, but this will be decided later today. Just so you can plan your
thursday morning :)
Greetings, Stephan
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
It seems like it takes a whole lot longer for a build to move from "finished"
to "succeeced" than it does for it to "finish".
--
Paul Elliott 1(512)837-1096
pelliott(a)BlackPatchPanel.com PMB 181, 11900 Metric Blvd Suite J
http://www.free.blackpatchpanel.com/pme/ Austin TX 78758-3117
Hello Mates,
today i tried to build local contour:
sascha@linux-uln9:~/osc/home:saigkill:branches:KDE:Active/contour> osc
build
Building contour.spec for openSUSE_Factory_KDE_Unstable_SC/x86_64
Getting buildinfo from server and store to
/home/sascha/osc/home:saigkill:branches:KDE:Active/contour/.osc/_buildinfo-
openSUSE_Factory_KDE_Unstable_SC-x86_64.xml
ERROR: Either wrong repo/arch as parameter or a parse error of
.spec/.dsc/.kiwi file due to syntax error
Maybe anyone knows what happend?
Greetings Sascha
--
Sincerely Yours
Sascha Manns
open-slx Community & Support Agent
openSUSE Membership Comitee
openSUSE Marketing Team
Web: http://saigkill.homelinux.net
German Community Portal: http://community.open-slx.de
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org