September 2011 - openSUSE Build Service

Re: [opensuse-buildservice] Cannot lock group file: already locked error during build
by Darin Perusich 29 Sep '11

29 Sep '11

Hi Robert, On Thu, Sep 29, 2011 at 10:06 AM, Robert Xu <robxu9(a)gmail.com> wrote: > On Sep 29, 2011, at 9:21, Darin Perusich <darin(a)darins.net> wrote: > >> Hello, >> >> I'm adding a group during the %prep stage of a package and the >> groupadd fails with the error "Cannot lock group file: already >> locked." when a building on OBS. This is something special I need to >> do to create the group during %prep? >> > > You can't do it during %prep. Do you mean %pre? > Doing it during prep is kinda unsanitary... > I'm creating it in %prep because the group is need as part of the build process...maybe I need to move it to %build. Incidentally, I'm creating the group and performing a usermod in %pre. -- 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] Fedora builds and rpmlint
by Nelson Marques 29 Sep '11

29 Sep '11

Hi all, How and where can I configure a project that does Fedora builds to use Fedora rpmlint in the end (pretty much like openSUSE does, except the one from Fedora). Is there docs available? Any links? All the best, NM -- 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] qemu(-arm) version
by Janne Karhunen 29 Sep '11

29 Sep '11

Hi, I'm experimenting with ARM builds with OBS and instantly run into issues with libc build under vanilla (ubuntu) qemu. Any pointers how could I feed osc new version of qemu (just for local builds for experiments)? -- // Janne -- 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] obs repos broken....
by Mathias Homann 29 Sep '11

29 Sep '11

Hi there... K:R:46 is broken: since the new qtwebkit package came in, kde 4.6.5 crashes on login with a segfault in libQTWebKit. K:R:47 is broken: it's not signed anymore, and from what I hear it has the same issues with webkit as K:R:46; I can't try since I can't update to K:R:47 OSS14/Updates is broken: zypper ref fails with a "file not found". "sent using thunderbird 7 on windows 7 under great pain" -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

4 10

[opensuse-buildservice] build error
by Damian Ivanov 29 Sep '11

29 Sep '11

Hi :) I try to compile the media player clemetine with a patch, making clementine to support vlc/xine and phonon backend, as it now only supports gstreamer :( When applying the patch it hangs with I: Program returns random data in a function E: clementine no-return-in-nonvoid-function /usr/src/packages/BUILD/clementine-0.7.1/3rdparty/libxrme/connection.cpp:487 I am not a developer so I can not fix it... Can I package it somehow skipping this build check or whatever... See package https://build.opensuse.org/package/show?package=clementine&project=home%3Ad… Thanks for helping and Best regards, Damian -- 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] An OBS appliance ready to work for MeeGo
by Dominig ar Foll (Intel OTC) 29 Sep '11

29 Sep '11

Hello, this was posted on the development tool mailing list that mainly of you likely do not follow, but that specific post should interest any one who need/want his own OBS to mix private and public code. Discussion will occurs in the Meego-distribution-tools mailing list -- Dominig ar Foll MeeGo TV / IVI Open Source Technology Centre Intel SSG -------- Message original -------- Sujet: [Meego-distribution-tools] An OBS appliance ready to work for meego Date : Thu, 29 Sep 2011 09:17:40 +0200 De : ronan <ronan(a)fridu.net> Pour : meego-distribution-tools(a)lists.meego.com Hello, as part of the delivery of the OBS Light project which aims at simplifying access to OBS for people who needs to run project with mixed private and public repositories, we are happy to release the first version a OBS for MeeGO appliance. Our prepackaged version is delivered as a OpenSUSE appliance and is available from Suse Studio. You will find it here : http://susegallery.com/a/e0uuBG/meego-obs -You have 2 Remote OBS projects (meego.com, public.meego.com). -you have 3 repository targets (meego:1.2.0, MeeGo:Trunk, MeeGo:1.2). -OBS setup is already done for you. -Architectures (i586, armv8el) are configured. -You can use, obstag - obs2obscopy - obsextractgroups, to work with an other OBS. http://wiki.meego.com/Obstag The appliance is available under various native and ready to run virtual machines. We assume that you know how to run a VM on your system. The User manual for a private OBS appliance is hosted on the MeeGo Wiki here : http://en.opensuse.org/openSUSE:Build_Service_private_instance For more information about OBS : http://en.opensuse.org//openSUSE:Build_Service_Appliance Your feedback is welcome. Ronan. _______________________________________________ MeeGo-distribution-tools mailing list MeeGo-distribution-tools(a)lists.meego.com http://lists.meego.com/listinfo/meego-distribution-tools -- 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] Are builds stopped or stuck on build07 (x86_64) on Open Build Service all are showing red
by doiggl＠velocitynet.com.au 28 Sep '11

28 Sep '11

Hello Some questions - are builds stopped or stuck on build07 (x86_64) ? [1] all are showing red. [1] https://build.opensuse.org/monitor Thanks Glenn -- 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] Failed to setup an OBS private instance from 2.2.90 Appliance
by JAFFREZIC Xavier 28 Sep '11

28 Sep '11

Hi everybody I've tried to start from scratch an OBS Private instance from the 2.2.90 appliance (64 bits) . Preparing the Raid1 Disk Array and Writing the Appliance to a dedicated Disk were fine. The Appliance boot successfully and recognize my Raid Array a LVM . Then I have updated the 2 following files - /etc/sysconfig/proxy - /usr/lib/obs/server/BSConfig.pm In order to match my firewall settings Then I reboot the appliance and everything were still fine So I tried to my OBS instance to be Remotely linked to another using the WebUI Whatever the target (opensuse or Meego) this failed . An I get : OBS Web Interface Error: Error Details: Errorcode: unknown Message: xpath for delete did not give exactly one node!" Because, I have setup a Private instance with the 2.2.84 (32bits), I have a copy of a working configuration file for this. So, I decided to create manually the raw config File (using my backup): <project name="Linked_Build"> <title>Remote access to OBS MeeGo Server </title> <description></description> <remoteurl>https://api.meego.com/public</remoteurl> <person userid="Admin" role="maintainer"/> <person userid="Admin" role="bugowner"/> </project> This config was accepted by the WebUI. Then I have created another project which id pointing to this one. <project name="Applications"> <title>User applications with HMI</title> <description></description> <person userid="Admin" role="maintainer"/> <person userid="Admin" role="bugowner"/> <repository name="Builds"> <path project="Linked_Build:MeeGo:1.2:oss" repository="standard"/> <arch>armv8el</arch> <arch>i586</arch> </repository> </project> This was well accepted from the UI. Then I upload a package in this project . This Package was successfully building on my previous instance . After uploading , nothing occurs (No Start building.) then I walk in the UI and in the repository page, I found the "trigger rebuild" button . When cliking the UI says : remote error: access denied To check my OBS connectivity, I've used osc from another computer with the following .oscrc [general] apiurl = https://10.220.95.219:444 su-wrapper = sudo no_verify = 1 [https://10.220.95.219:444] keyring=1 Where 10.220.95.219 is the IP of my OBS server When I'am launching the following command : osc ls Linked_Build:MeeGo:1.2:oss I can see the full listing for the MeeGo:1.2:oss packages. So the connectivity of my OBS looks right (Correct firewall configuration) What I'am missing in the configuration ? Do I need to some tweaking ? Should I switch back to 2.2.84 (oups . Is there still some image online ?) -- Disclaimer ------------------------------------ Ce message ainsi que les eventuelles pieces jointes constituent une correspondance privee et confidentielle a l'attention exclusive du destinataire designe ci-dessus. Si vous n'etes pas le destinataire du present message ou une personne susceptible de pouvoir le lui delivrer, il vous est signifie que toute divulgation, distribution ou copie de cette transmission est strictement interdite. Si vous avez recu ce message par erreur, nous vous remercions d'en informer l'expediteur par telephone ou de lui retourner le present message, puis d'effacer immediatement ce message de votre systeme. *** This e-mail and any attachments is a confidential correspondence intended only for use of the individual or entity named above. If you are not the intended recipient or the agent responsible for delivering the message to the intended recipient, you are hereby notified that any disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender by phone or by replying this message, and then delete this message from your system. -- 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] osc: how to checkout package into current directory?
by Bartosh, Eduard 27 Sep '11

27 Sep '11

Hi, Is it possible to checkout package into already existing or current directory without creating PACKAGE directory? Let me explain why I need it. My package directory structure looks like this: package src/ rpm/ .... Quite common project structure, I'd say. It's under git control. What I want is to be able to use osc when in rpm/ subdirectory. For that I need osc to be able to create package structure right in the current directory, without creating PACKAGE subdirectory. So, the workflow of creating and working with packaging would be something like this: git clone git_url_of_mypackage create empty package mypackage in WebUI or better using osc mkpac, but that's another story cd mypackage mkdir rpm git archive --prefix mypackage-version/ HEAD | gzip > rpm/mypackage-version.tar.gz cd rpm osc co -o. myproject mypackage vi mypackage.spec git add mypackage.spec git commit -m 'Added spec' osc add mypackage.spec mypackage-version.tar.gz osc commit ... .... I'm able to work around it by moving .osc directory from rpm/PACKAGE/.osc to rpm/. However, from my point of view it would be better to have one more option for osc to do it. What do you think? If it doesn't sound bad or totally incorrect would you accept patch implementing it? Regards, -- Ed --------------------------------------------------------------------- Intel Finland Oy Registered Address: PL 281, 00181 Helsinki Business Identity Code: 0357606 - 4 Domiciled in Helsinki This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. -- 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] Buildservice
by Joop Boonen 26 Sep '11

26 Sep '11

Hi, I've been testing OBS for a while. I like it a lot. I think one thing isn't correct in /usr/share/doc/packages/obs-api/README.SETUP under "4.2 import base distributions into the backend". Run the api import script: # cd /srv/www/obs/api/script # RAILS_ENV="production" ruby import I have a feeling this is not valid any more, otherwise it's broken in both stable (2.1) as unstable (2.3). During the install I have to add api.<domain_name> and build.<domain_name> in /etc/hosts. This is not mentioned in /usr/share/doc/packages/obs-api/README.SETUP The line in /usr/share/doc/packages/obs-api/README.SETUP should be: Enable SSL in /etc/sysconfig/apache2 via APACHE_SERVER_FLAGS="SSL" In stead of: Enable SSL in /etc/sysconfig/apache2 via APACHE_SERVER_FLAGS="-DSSL" One thing is also not correct in /etc/apache2/vhosts.d/obs.conf, the directory isn't correct. This is for OBS unstable i.e. 2.3. --- /etc/apache2/vhosts.d/obs.conf 2011-09-22 23:26:54.405237593 +0200 +++ /etc/apache2/vhosts.d/obs.conf.orig 2011-09-21 12:57:26.000000000 +0200 @@ -26,9 +26,9 @@ # Build Results <VirtualHost *:82> # The resulting repositories - DocumentRoot "/srv/obs/repos" + DocumentRoot "/obs/repos" - <Directory /srv/obs/repos> + <Directory /obs/repos> Options Indexes Allow from all </Directory> Regards, Joop. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 0