August 2011 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] Python program failed test suite in OBS
by Kyrill Detinov 16 Aug '11

16 Aug '11

Saturday 13 August 2011 Hello. I build a package locally and it is OK: ---------------------------------------------------------------------- Ran 134 tests in 5.768s OK + exit 0 In OBS test suite failed with errors: FAIL: tests.ipc.test_wait.test_wait_signal('SIGINT',) FAIL: tests.ipc.test_wait.test_wait_signal('SIGABRT',) FAIL: tests.ipc.test_wait.test_wait_signal('SIGSEGV',) https://build.opensuse.org/package/show?package=ocrodjvu&project=home%3ALaz… What is the problem? -- WBR Kyrill -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 2

[opensuse-buildservice] Exclude param in tar_scm
by Carlos Gonçalves 15 Aug '11

15 Aug '11

Hi, Can anyone confirm if the 'exclude' parameter in tar_scm source service works fine? For what I can tell, it isn't working or I'm missing something. Example of a generated tar command by tar_scm: $ tar cf /tmp/tmpARm7Lt/debian-2.6.tar '--exclude='\''docs'\''' debian-2.6 The tarball debian-2.6.tar still includes the unwanted 'docs' file. Applying this diff: --- /usr/lib/obs/service/tar_scm.orig 2011-08-11 23:30:47.592347273 +0100 +++ /usr/lib/obs/service/tar_scm 2011-08-11 23:31:07.603889711 +0100 @@ -48 +48 @@ - EXCLUDES="$EXCLUDES --exclude='${2#/}'" + EXCLUDES="$EXCLUDES --exclude=${2#/}" The generated tar command is now $ tar cf /tmp/tmpNdpxNR/debian-2.6.tar --exclude=docs debian-2.6 And as a result the tarball produced doesn't include the 'docs' file, as expected. Cheers, Carlos Gonçalves -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 3

[opensuse-buildservice] osc commandline options
by Togan Muftuoglu 13 Aug '11

13 Aug '11

Hi, When I do "osc bco PRJ PKG" the package is created "home:user:branches:prj/pkg" and this is the same format that is created in my disk. however if I just "osc branch PRJ PKG" in the build service I have the home:user:branches:prj/pkg format which is fine and I then have the option of doing "osc co home:user:branches:prj pkg -c" which enables me to create it under a directory of my wish. So the question is why does "osc bco" do not provide this option, or is it already there and I do not seem to find it ? I am using osc-0.132.5-56.1 Thanks Togan -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 0

[opensuse-buildservice] copy/move a package with history
by Praveen_Paladugu＠Dell.com 12 Aug '11

12 Aug '11

All, Is there a way to copy/move a package to a new project WITH the package's commit history on OBS? Thank you Praveen K Paladugu Dell Linux Engineering -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 2

[opensuse-buildservice] conflict in spec
by Togan Muftuoglu 12 Aug '11

12 Aug '11

Hi, I am maintaining shorewall in security:netfilter and the package was yesterdat accepted into factory. Now I have a problem, the package itself at security:netfilter has a broken spec hence it is broken and can't build. Mind you that I haven't done anything. Moreover, when I want to branch this package so I can update with a new version I just get an empty package in home:branches:security:netfilter/shorewall. Am I missing something obvious, or can someone explain me how can a valid spec and a building package without doing nothing becomes broken Thanks Togan -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

4 7

[opensuse-buildservice] How to add extra package rpm into OBS project repo but not deleted when project rebuid
by Wu, Yanping 11 Aug '11

11 Aug '11

I tried to add extra package(rpms) into my OBS project repo(E.g /srv/obs/repos/project/i586), When I run createrepo in OBS server, the repodata will change correctly, and I can use the repo to install this extra package. But when there is check-in to the project, and it begins to rebuild. The repo will republished. I found OBS automatically delete my extra package in i586 directory. And the repodata doesn't include it any more. How can I solve this issue? Hope for your help.

3 5

[opensuse-buildservice] zfs in OBS
by john doe 11 Aug '11

11 Aug '11

hello, i'm considering to create OBS package for zfs: http://susepaste.org/view/raw/31247566 Due to the bit of unclear licensing ( http://zfsonlinux.org/faq.html ) limitations i suppose, that zfs-wrapper.rpm package should be solution. Of course there's more ways to do it and i'd prefer that it satisfies a build deps and provides build scripts ... Maybe also considering DKMS could prove useful although it is not yet in stable version it seems like it's in factory. any comments or suggestions are welcome. regards by daniel ps. violating rights-to-use by making it available in PACKMAN is way i'd not like to follow. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 3

[opensuse-buildservice] Using the Open build service as part of the Debian Mentors process
by Asheesh Laroia 11 Aug '11

11 Aug '11

Hi Open Build Service folks, I'm working on setting up some new web software for Debian packaging contributors. I heard about the Open Build Service here at the Desktop Summit, and I wondered: Can we programmatically upload prospective Debian contributors' source packages to the Open Build Service, have OBS do a package build, and then run package quality tests on the resulting *.deb files? Right now, we don't actually *compile* Debian contributors' source packages -- they just upload them to http://expo.debian.net/. It would be really great to add some code to that website that would use OBS to build the packages -- by doing that, we can show the package contributors if their packages build properly! So this has two parts: First, is it technically posssible? And second, is this a use that would be okay? Thanks, -- Asheesh. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 4

[opensuse-buildservice] Projects self-contained?
by Esztermann, Ansgar 10 Aug '11

10 Aug '11

Hello List, until recently, I had thought that projects within OBS are supposed to be self-contained, i.e. packages must declare dependencies only on other packages in the same project (or in the standard openSUSE repos). However, I've now found a package in the science project that contains an outside dependency. Have I been mistaken? Thanks, A. -- Ansgar Esztermann DV-Systemadministration Max-Planck-Institut für biophysikalische Chemie, Abteilung 105 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 2

[opensuse-buildservice] Chromium
by Carl Fletcher 10 Aug '11

10 Aug '11

Has anyone noticed the recent Chromium updates have Jeffed things up? -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

4 4

Re: [opensuse-buildservice] link or aggregate?
by Darin Perusich 10 Aug '11

10 Aug '11

Hi Greg, On Sun, Aug 7, 2011 at 8:03 PM, Greg Freemyer <greg.freemyer(a)gmail.com> wrote: > > You'll likely need to post a link to your project before anyone can help. > Here's a link to the package I'm trying to build. https://build.opensuse.org/package/show?package=rt&project=home%3Adeadpoint -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 2

[opensuse-buildservice] service format_spec_file failed
by Sascha Manns 09 Aug '11

09 Aug '11

Hello mates, is this a already known bug? service format_spec_file failed: lxc-start: cgroup is not mounted lxc-start: failed to spawn 'obs.service.jail.20041' lxc-start: cgroup is not mounted rm: Entfernen von „/opt/obs/SourceServiceSystem.mounts//20041//lxc.tmp.20041/inner.sh.command“ nicht möglich: Datei oder Verzeichnis nicht gefunden rm: Entfernen von „/opt/obs/SourceServiceSystem.mounts//20041//lxc.tmp.20041/inner.sh“ nicht möglich: Datei oder Verzeichnis nicht gefunden rmdir: konnte „/opt/obs/SourceServiceSystem.mounts//20041//lxc.tmp.20041“ nicht entfernen: Datei oder Verzeichnis nicht gefunden -- 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

3 4

[opensuse-buildservice] [gsoc] osc code cleanup - summary of week 11
by Marcus Hüwe 08 Aug '11

08 Aug '11

Hi, here's a small summary of the 11th (coding) week. This week I spent most of my time with working on the wc code. DONE: * project wc: added commit and update methods * lots of wc code refactoring TODO: * project wc: commit only specific files for a package instead of the complete package (the package wc class already supports this) (use case: osc ci pkg1/file pkg1/foo pkg2/bar pkg3) * convert old working copies to the new format * package wc: update: add support to specify stuff like "expand", "linkrev" etc. * project wc: add a revert method (to restore a package wc with state '!') * project/package wc: support diff * package wc: implement a pull method (does the same as "osc pull") Marcus -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 0

[opensuse-buildservice] [PATCH] use pigz with kiwi if it is available in buildroot
by Dinar Valeev 08 Aug '11

08 Aug '11

Attached patch defines kiwi option --gzip-cmd to pigz if package available in buildroot. Otherwise gzip will be used (by default). pigz, which stands for parallel implementation of gzip, is a fully functional replacement for gzip that exploits multiple processors and multiple cores to the hilt when compressing data. My experience with pigz is ~6Min (gzip) vs ~2Min with pigz. Comments are welcome.

1 1

[opensuse-buildservice] link or aggregate?
by Darin Perusich 08 Aug '11

08 Aug '11

Hello, I have a package I'm building that has a ton of dependencies from the devel:/languages:/perl repository and from reading the build service tips and tricks it would appear that using either _link or _aggregate is the solution for handling the dependencies. Is there any example documentation on how to accomplish this or can someone point at a package which do this so I can review it? Thanks! -- Later, Darin -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

5 5

[opensuse-buildservice] cross building not working in chroot with 2.3
by Nashif, Anas 07 Aug '11

07 Aug '11

Any idea what is going wrong here? VM builds just work fine. preinstalling libfile-x86-arm... running bzip2-x86-arm postinstall script chroot: failed to run command `sh': No such file or directory running tar-x86-arm postinstall script chroot: failed to run command `sh': No such file or directory running coreutils-x86-arm postinstall script .. ..

2 3

[opensuse-buildservice] a few repo questions
by Jon Nelson 06 Aug '11

06 Aug '11

If I wanted to be using the "latest stable OBS software" for openSUSE 11.4, what repo should I be using? What purpose does openSUSE:Tools: serve? Also, the versions of rubygem-* in openSUSE:Tools are *older* than those that are available with openSUSE 11.4's update. Which should I be using? -- Jon -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 1

[opensuse-buildservice] [GSoC] OBS Mobile: New Features Added to Requests
by Justine Leng 05 Aug '11

05 Aug '11

Hi all, I would like to share with you some exciting progress on the OBS Mobile Project: 1. Request state has been added to each request; 2. Sorting functions have been implemented for Requests. 3. A search filter has been added to the Request page. Now, when the user logs into the list of requests, the user will not only be able to see the state of each request, but also sort requests based on 4 criteria: - request date - requester's name - target project/package - request state Please see screenshots: http://susepaste.org/59733925 http://susepaste.org/18374131 http://susepaste.org/40594474 http://susepaste.org/61762342 The user can also filter requests by typing in a keyword: http://susepaste.org/38303182 These new features have been tested in my desktop browsers and on my Android device, and they seem to be working fine. Please feel free to check out the new features as soon as they are merged to the master. Feedback and comments are always welcome & appreciated. Cheers, Justine Leng -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 0

[opensuse-buildservice] Authentication issues
by Robert Schweikert 05 Aug '11

05 Aug '11

Hi, I recently switched from GNOME to Xfce as my desktop (fleeing from GNOME3). Since the switch I end up getting Server returned an error: HTTP Error 401: basic auth failed errors when I try to use osc commands, build, up, etc. I can remedy the authentication error by placing my password into ~/.oscrc. However, not having needed to store my password in .oscrc prior to the switch I'd like to avoid having my password in ~/.oscrc. How do I accomplish this? What mechanism did osc use to authenticate when I was using GNOME? gnome-keyring-daemon process is running on my machine. Help is appreciated. Thanks, Robert -- Robert Schweikert MAY THE SOURCE BE WITH YOU SUSE-IBM Software Integration Center LINUX Tech Lead rjschwei(a)suse.com rschweik(a)ca.ibm.com 781-464-8147 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 0

[opensuse-buildservice] Missing macro on CentOS 6 VM?
by Cantor, Scott E. 04 Aug '11

04 Aug '11

Doing some test builds with the CentOS 6 platform, there appears to be an RPM macro missing, specifically %{rhel} set to 6. This is present on Red Hat 6 and in my testing is present on default installs of CentOS 6 as well, but it's apparently missing on the VM image the build service spins up. I have some packages that do straightforwardly different things if the value is >= 6, and they work on RH6, but not CentOS. I haven't tried to dump the macro in an RPM scriptlet or anything that detailed yet, but it's apparently not present. -- Scott -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 5

[opensuse-buildservice] sending notifs without hermes?
by Robert Xu 04 Aug '11

04 Aug '11

Hi all, I was wondering if it is possible that the OBS can send notifications to a certain mailing list whenever something is checked in a project, like opensuse-commits, but without hermes. Is that possible? Like writing a plugin or a plugin already available (that would be really great) to send the system a mail command or something... -- 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

2 1

[opensuse-buildservice] can't link?
by Robert Xu 03 Aug '11

03 Aug '11

Hi all, I wanted to link to openSUSE:Factory/bash, but I've been getting this error: Files could not be expanded: openSUSE.org:openSUSE:Factory/bash: srcmd5 mismatch I noticed there were _service:* files but no '_service' file. Can someone help me? -- 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

2 2

[opensuse-buildservice] adding a package to a repository
by Darin Perusich 01 Aug '11

01 Aug '11

Hello, How does on have a package added to a top-level repository? Say I built a perl module and would like it to be added to http://download.opensuse.org/repositories/devel:/languages:/perl/. I haven't been able to figure out how to do this from reading the documentation, or maybe I've missed something. Thanks! -- Later, Darin -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 1

[opensuse-buildservice] driving my scheduler crazy
by Robert Xu 01 Aug '11

01 Aug '11

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

2 2

[opensuse-buildservice] [gsoc] osc code cleanup - summary of week 10
by Marcus Hüwe 01 Aug '11

01 Aug '11

Hi, here's a small summary of the 10th (coding) week. This week I spent most of my time with working on the package working copy class' commit method. This also involved some code refactoring. Basically commit and update are handled as "transactions" and all relevant transaction data is stored in a single xml file (pkg/.osc/_transaction/state). This way an update/commit is more or less an atomic operation. For more information have a look at [1] (class XMLTransactionState + subclasses and commit/update method). TODO: - add update and commit methods for the project class Marcus [1] https://gitorious.org/osc2/osc2/blobs/master/osc/wc/package.py -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 0

[opensuse-buildservice] HowTo build with LXC for OBS
by Bernhard M. Wiedemann 01 Aug '11

01 Aug '11

-----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

3 5

[opensuse-buildservice] Project Repo broken causes OBS hunt down
by Wu, Yanping 01 Aug '11

01 Aug '11

When build my project in locale OBS against a remote project, something unknown broke the build and the project repo status appears broken, then other project also cannot build now whatever I restart the host or restart OBS service. Can anyone help on this, thanks. Best Regards Karen

1 0