May 2012 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] Expired OBS Keys?
by King Thorin 02 Jul '13

02 Jul '13

It seems the OBS Security key (keyid 79EAFD54) on keys.gnupg.net has expired (2011-Apr-2). Would it be possible for someone to update it? I know an updated key has been generated (which expires 2013) as it can be found here: http://download.opensuse.org/repositories/security:/OpenVAS:/STABLE:/v4/xUb… Further details can be found via: http://lists.wald.intevation.org/pipermail/openvas-distro/2011-April/thread… Basically the issue came to light when following instructions: http://www.openvas.org/install-packages.html#openvas4_ubuntu_obs -- 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] New project openSUSE:Current?
by Cristian Morales Vega 18 Mar '13

18 Mar '13

Sometimes you have appA in your repo building for both old and new openSUSE versions. appA depends on libA > X, but only the latest openSUSE version provides it. openSUSE <latest-1> came with libA <X-1>. The solution is to package libA > X for the old distributions and usually you do that linking to the devel project. I would like an openSUSE:Current project that would always contains the latest supported version of the packages. Right now the packages from openSUSE:12.1:Update, but once 12.2 is released it should be changed to openSUSE:12.2:Update. This way I could link to those packages instead of linking to the devel project. It would let me compile appA in old distros while giving to the users a libA package that is not soooooo unsupported (this would be officially unsupported anyway, but...). I would like this since it's a single place to change when a new openSUSE version is released (If needed I can do it). Looking at the openSUSE:12.1:Update project metadata I guess it would just need be something like <project name="openSUSE:Current"> <title>Current version of openSUSE</title> <description></description> <link project="openSUSE:12.1:Update"/> <debuginfo> <enable/> </debuginfo> </project> But I'm not sure since I never really saw a doc explaining the meaning of <link> in the *project metadata*, only in _link files. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 8

[opensuse-buildservice] Problem building Perl packages for SLES11SP2 with certain build requirements
by Joschi Brauchle 21 Nov '12

21 Nov '12

Hello everyone, I have a question/problem with Perl packages and BuildRequires when building for SLES(SP2). The problem comes up with multiple packages when trying to build them for SLES, let's look at perl-HTTP-BrowserDetect from devel:languages:perl for example. The spec files includes: --- BuildRequires: perl(Module::Build) >= 0.3601 --- and the build log clearly states (see https://build.opensuse.org/package/rawlog?arch=x86_64&package=perl-HTTP-Bro…) that it is being installed: --- installing perl-Module-Build-0.36.07-4.1 --- but still, the build fails with: --- Module::Build version 0.3601 required--this is only version 0.280801 at Build.PL line 5. --- As far as I understand, "Module::Build" v0.280801 is already installed by default under SLES11SP2 and the newer required version 0.3607 is not found OR the older version is found first by the script "Build.pl". A second example would be "perl-POE-Test-Loops" which requires a version of Test::More/Test::Simple >=0.94, but this is not found although installed (i.e. only an older version is found), see log here: https://build.opensuse.org/package/live_build_log?arch=x86_64&package=perl-… How do I circumvent this problem? Thanks for your help!

4 7

[opensuse-buildservice] Use solid state disks [ssd] to improve obs build times.
by doiggl＠velocitynet.com.au 30 Jul '12

30 Jul '12

Hello With the opensuse build service [obs] getting more usage every day I wonder if this would make a diffence :- 1. Use solid state disks [ssd] to improve build times of package rpms on, perhaps point the BuildRoot or _tmppath to the ssd's Reason for asking. Improve the packaging times during busy times on obs. Cheers Glenn. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

8 17

[opensuse-buildservice] OBS 1.3 Privately signed certificate and osc
by Dominig ar Foll (Intel OTC) 19 Jun '12

19 Jun '12

Hello, having just updated to OBS 1.3, my API is now running under https (not a bad idea). I have created a PRIVATE certificate following the README. --------------- mkdir /srv/obs/certs openssl genrsa -out /srv/obs/certs/server.key 1024 openssl req -new -key /srv/obs/certs/server.key \ -out /srv/obs/certs/server.csr openssl x509 -req -days 365 -in /srv/obs/certs/server.csr \ -signkey /srv/obs/certs/server.key -out /srv/obs/certs/server.crt cat /srv/obs/certs/server.key /srv/obs/certs/server.crt \ > /srv/obs/certs/server.pem ---------------------- I see that with osc (version 0.134.1) if the privately signed certificate is create with a Common Name (CN) which is not the server name, osc refuses to chat with the API. That is bit strick as : - CN name is normally free of use - In that mode access via IP address is not possible any more - auto recovery system with shadow server configuration cannot be done. That is very strange as it seems that when the certificate with an official root, the common name is not critical. Any clue how to overcome that issue ? Regards -- Dominig -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

5 7

[opensuse-buildservice] Fedora repo fails when installing portaudio
by Ruediger Meier 07 Jun '12

07 Jun '12

Hi, On Fedora (15/16) BuildRequires: portaudio-devel gives me this: [...] installing portaudio-19-12.fc15 warning: .init_b_cache/portaudio.rpm: Header V3 RSA/SHA256 Signature, key ID 069c8460: NOKEY error: unpacking of archive failed on file /usr/lib64/libportaudio.so.2.0.0;4f24be4b: cpio: read failed - Bad file descriptor error: portaudio-19-12.fc15.x86_64: install failed [...] Local build works. This is the package where is happens https://build.opensuse.org/package/show?package=FreeMat&project=home%3Arudi… but I'll work around it so the logs may be gone. cu, Rudi -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 1

[opensuse-buildservice] MonoOSC?
by Roger Luedecke 03 Jun '12

03 Jun '12

ANy plans to get this working again? I'm at a loss as to how to get it going though I had branched the project etc. Frankly, I'm figuring out the build service, and think monoosc would go a long way to fostering a quicker understanding. -- Roger Luedecke openSUSE Ambassador Ind. Repairs and Consulting **Looking for a C++ etc. mentor*** -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

5 25

[opensuse-buildservice] Open Build Service version 2.3 released
by Adrian Schröter 01 Jun '12

01 Jun '12

The Open Build Service(OBS) version 2.3.0 brings new features esp. in the Maintenance and Release Management area and is the latest stable maintained version. It is recommended to update to this version to get improved security protections. It is also the first version which comes with official support offerings from our partner B1-Systems backed by SUSE. Please find the html version of this text here: http://www.open-build-service.org/2012/05/03/open-build-service-version-2-3… OBS 2.3 brings the functionality to maintain a released software product in an efficient and transparent way. This includes * Update coordination: One or more maintenance groups can decide if and when to start or release an update. This includes also the tracking of new, running and processed updates * QA and Review integration: The current state of an update is always visible and trackable. Review processes can be integrated * Release Management: Isolated build and tested updates can be released or revoked via OBS mechanism * Multiple code stream support: An issue can be handled for multiple code stream * Documentation support: The documentation of an update for the end-user is integrated This functionality is already used for doing the maintenance updates for the openSUSE distributions<. The features can be used all together or in parts for own products. In addition OBS 2.3 provides * A greatly improved web interface, including user management, syntax highlighted source editor and improved source diff review views * Improved Cross Build Support via Qemu * Functionality to hide entire projects * Issue tracking support, tracking documented fixes in external bugzilla, fate and CVE instances in packages. It is recommended to read the Release Notes before updating an instance. OBS packages can be found in the openSUSE Tools project or as an appliance which can be used on hardware or in VM. Your Open Build Service team Links ===== OBS home page: http://www.open-build-service.org Support: http://www.open-build-service.org/contact/ Release Notes: https://github.com/openSUSE/open-build-service/blob/2.3/ReleaseNotes-2.3 Download: https://build.opensuse.org/project/show?project=openSUSE%3ATools Appliance: http://en.opensuse.org/openSUSE:Build_Service_Appliance The Team: http://www.flickr.com/photos/adrianschroeter/7135213251/ About Open Build Service ======================== The Open Build Service (OBS) is an open and complete distribution development platform. It provides the infrastructure to easily create, release and maintain software for openSUSE and other Linux distributions on different hardware architectures. It is developed under the umbrella of the openSUSE project, but is licensed under GPL and used by other open source projects like MeeGo, Mer, Packman or Tizen. It is also used by universities, ISVs and companies like Intel, Dell, SGI. -- Adrian Schroeter SUSE Linux Products GmbH email: adrian(a)suse.de ------------------------------------------------------------- -- Adrian Schroeter SUSE Linux Products GmbH email: adrian(a)suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 5

[opensuse-buildservice] Fedora 17 added, new build package required
by Adrian Schröter 01 Jun '12

01 Jun '12

Fedora:17 project is added and can be used. However, for local builds you need to update the build package or some workarounds will not apply. (Doing the /bin > /usr/bin move only half way is a really bad idea, Fedora). You need build-2012.05.30 or later, for example from openSUSE:Tools project. bye adrian -- Adrian Schroeter SUSE Linux Products GmbH email: adrian(a)suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

5 19

[opensuse-buildservice] OCaml help
by Robert Schweikert 31 May '12

31 May '12

Hi, I have a couple of requests/questions in "cleaning up" OCaml related packages. 1.) Since we have top level devel:languages:ocaml project can we please move everything that is ocaml related and maintained devel:languages:misc into the ocaml project? 2.) Do we have anyone that is really interested in OCaml or do we just have what we have because other projects/packages depend on the few packages we do have? in d:l:ocaml the ocaml package is a link to the package in Factory. The devel project for factory is d:l:misc. Because of local mods in d:l:ocaml the link is busted due to merge conflicts. This breaks other packages in d:l:ocaml. I have no idea how to fix this as everytime I try to touch any of these packages to get something fixed I get a stupid: buildinfo is broken... it says: type of message. This is of course complete crap as it prevents a person trtying to fix something from fixing it. Right now things appear to be a bit of a mess and I feel I have step into a big pile..... 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 To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 1

[opensuse-buildservice] rpmlint documentation
by Isaac Hailperin 31 May '12

31 May '12

Hi, I know its kind of ot, but I was wondering if anybody has some documentation on what rpmlint does exactly. The man page just says its checking for common errors. Is there a way of understanding what rpmlint does without reading the sources? Isaac -- Isaac Hailperin -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 1

[opensuse-buildservice] expansion error for perl(FCGI) in devel:languages:perl
by Darin Perusich 31 May '12

31 May '12

Hello All, I was attempting to update devel:languages:perl/request-tracker this morning and when running a local build, before committing the changes, received an "expansion error" for the first time. The build services tips and tricks says to specify one of the packages as a BuildRequire and there is, perl(FCGI) which had been resolving to the perl-FCGI package. The tips and tricks page says to email the list for a long term fix so here's that email. What needs to be done to work around this? expansion error have choice for perl(FCGI) needed by perl-CGI: perl-FastCGI perl-FCGI have choice for perl(FCGI): perl-FastCGI perl-FCGI -- Later, Darin -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 7

[opensuse-buildservice] How do I resolve....
by Robert Schweikert 30 May '12

30 May '12

Hi, I am working on some CloudStack/Xen related stuff that happens to depend on OCaml. I've already added a bunch of dependencies to Virtualization:Cloud:CloudStack:Testing but am geeting stuck with a problem that I do not know how to resolve, and help is much appreciated. The current package I am trying to build is ocaml-ocamlnet (not submitted to OBS yet). The code has an option to build gtk2 bindings and I'd like to enable this. Enabling GTK2 requires lablgtk2 which I added as a BuildRequires to my spec file. I get the following error when I try to build for 12.1: buildinfo is broken... it says: unresolvable: nothing provides ocaml(runtime) = 3.12.0 needed by lablgtk2 The ocaml package in the project I am working on (Virtualization:Cloud:CloudStack:Testing) is linked to devel:languages:misc which is up to 3.12.1. When I look at https://build.opensuse.org/package/view_file?file=lablgtk2.spec&package=lab…, the spec file for lablgtk2 there is no explicit version requirement for ocaml, i.e. a Requires: ocaml = X.Y.Z, yet the package obviously requires this. I would prefer not build a different ocaml version than we have in the project. Obviously there is something going on that I do not understand. Thanks for any help, 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 To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 1

[opensuse-buildservice] OBS Light releases a solution to build locally your Tizen IVI image
by Dominig ar Foll (Intel OTC) 30 May '12

30 May '12

Hello, The OBS Light team http://wiki.meego.com/OBS_Light has just released the Beta version off the OBSLight-fakeobs addon. FakeOBS has been originally created by the MER project and we have modified it for our needs. Our goal is to ease the import of a pre-boot strapped full distribution such as MeeGo TV or Tizen IVI in a private OBS instance. What has been released ======================= OBSLight-fakeobs enables to deliver pre-boot strapped complete OBS project(s) as a simple tar file (might be big!) which can be added to an OBSLight-server by a simple command. The added new project(s) is accessible through obslight server via the fakeobs project link. Branching off any packages from the fake OBS in your local OBS is possible and building against the added project is availble by a simple click on an icon. Note: As the tools to create the tar file are not yet well documented, we have created a set of three projects tar file for easy import as a demo. We have used the recently published Tizen IVI. Tizen_1.0_Base-1.0.tar.gz, Tizen_1.0_IVI-1.0.tar.gz, Tizen_1.0_Main-1.0.tar.gz They can be found on test hosting http://tizen.fridu.net/ .That link will likely be removed in few weeks. Depending of your internet access speed expect 1 to 2 hours to complete that Howto. In practice outside of the download time, 30mn should be more than adequate. For my appliance, I use Virtual box because it's easy to setup and delivered as default on most distro. It should also work on other virtualisation system (thanks to Suse Studio). Howto ===== Server side ----------- The server can be a simple good developer desktop. It will need 8GB or RAM (16GB is better, 4GB is only OK for an evaluation). Install OBSLightServer appliance. It is preconfigured for MeeGo and Tizen. http://susestudio.com/a/e0uuBG/meego-obs I advise you to allocate to the appliance 8GB and 4 CPUs if you want to compile big packages such as Webkit, For smaller packages 4GB and 2 CPUs will do (the more is the best). Connect as root on the obslightserver appliance (default passwd is opensuse) Install the obslight-fakeobs package zypper ar http://download.opensuse.org/repositories/devel\ :/languages:/python/openSUSE_11.4/devel:languages:python.repo zypper install obslight-fakeobs (following commands are needed due to a bug under correction) rcfake obsstatus -> if status is non active after a reboot insserv /etc/init.d/fakeobs rcfakeobs restart Download the Tizen project needed to work on IVI (Base->1.8GB, Main->2.8GB, IVI->5.1GB) wget http://tizen.fridu.net/Tizen_1.0_Base-1.0.tar.gz;\ wget http://tizen.fridu.net/Tizen_1.0_IVI-1.0.tar.gz;\ http://tizen.fridu.net/Tizen_1.0_Main-1.0.tar.gz;\ Depending of your internet access performance, you may have a coffee or a 4 courses lunch :-) Create the link to the fakeobs in your obs appliance obslight-fakeobs createlink Import your project and create an icon to build against it obslight-fakeobs import Tizen_1.0_Base-1.0.tar.gz "Tizen:1.0:Base" obslight-fakeobs import Tizen_1.0_Main-1.0.tar.gz "Tizen:1.0:Main" obslight-fakeobs import Tizen_1.0_IVI-1.0.tar.gz "Tizen:1.0:IVI" Your obslightserver is now fully available Client side ----------- Install obslight (these 1st phases only use osc mic but many dependencies issues are fixed in the obslight repo and we will use the GUI in this HowTo :-) http://wiki.meego.com/OBS_Light_Installation If you are a Mac or Windows user (or have a non supported distro) an OBSLight appliance is also available. http://susestudio.com/a/e0uuBG/obs-light Check which packages are available on your obslightserver appliance osc -A http://obslightserver:444 ls osc ls fakeobs:Tizen:1.0:Base (first time you will be asked your userID and passwd) osc -A http://obslightserver:444 ls osc ls fakeobs:Tizen:1.0:Main osc -A http://obslightserver:444 ls osc ls fakeobs:Tizen:1.0:IVI Branch a package from the fakeobs downloaded projects Connect on the API of your OBS appliance which by default is at https://obslightserver:444 Create one or more user(s) Connect on the WebUI of obslightserver https://obslightserver (next step is due to a 'special' obs feature) log as Admin (default passwd opensuse) create a home project to Admin logout Log in with your newly created user name Create your home page Create a subproject named "test" (from the top menu bar) (you will be moved in that new sub project) Select from the top menu the "Packages" actions Click "Branch Package from other project" Enter 'fakeobs':Tizen:1.0:Main as "Name of original project:" Enter 'sensor' as "Name of package in original project:" (note auto completion does not work very well, do not enter the "'" you can use osc to list existing packages) Build your newly branched package Add a build target Click on "build target" (on the right of the screen) Select near the OBSLight icon (blue penguin) "Tizen 1.0 Main" Click on "Overview" menu item You see "package is building" After about 1mn click on the refresh build status (2 arrows in a circle) You see Succeeded:1 Create an image with Tizen and your branched package Download your kickstart file (.ks) (Note you cannot use groups on your live private repo) You have an ivi version without groups here http://tizen.fridu.net/kickstarts/tizen-ivi-min-pc.ks save it with a .ks extension Launch obslightgui Activate the "MIC Project" (2nd) tabulation Click on the button "New" on the bottom left Enter a name (e.g. Test) The new Mic project appears in the list of Mic projects Select the newly create project Activate the "Project Option" (1st) tabulation Import the kickstart file Activate the Repositories (3rd) tabulation Exclude sensor from both base and main repos Enter 'sensor' in the (9th) column "Excluded packages" Change the host name if needed. Retrieve the url of your local branch (from the WebUI) https://obslightserver/project/show?project=home%3AUSER%3Atest Select the menu "Overview" Click on "Tizen_1.0_Main" Click on "Go to download repository" Copy the URL (from the obslightgui-> Mic Project-> Repositories tab) Enter the copied URL Create an alias (e.g MyBranch) Activate the "Project Option" (1st) tabulation Click "Create Image" Click on view log to see progress (wait about 2mn) Click on "Open project directory" Check the status in the log file Export your image by tftp and nfs and run a test. For further test on the same package you can run zypper directly from the target after adding your test branch as an extra repo with a zypper command. Building on your local PC ------------------------- Due to the change in the package structure from MeeGo to Tizen , the direct work on packages from obslightgui present some problem (it is not possible on Base), we will come back to this mailing list with a HowTo as soon as a reliable model will have been found (I hope this week) Known Limits and bugs ----------------------------- - the Python devel repo lust be added manually to the appliance zypper ar http://download.opensuse.org/repositories/devel\ :/languages:/python/openSUSE_11.4/devel:languages:python.repo - after installation of the package obslight-fakeobs you still to activate the service for reboot with the command insserv /etc/init.d/fakeobs; rcfakeobs restart (should be corrected soon and might have gone before that you test) - you cannot walk the available project pointed by the fakeobs link project from the WebUI (that limit is there to stay for a while) - we do our test only with obslightserver appliance. It should work with any OBS but that is out of our focus. - when creating a branch the project name auto completion is not available you need to enter it (e.g. fakeobs:Tizen:1.0:Base) - when creating a branch the package name auto completion is not reliable. You actually might need to enter the package name in total. - OBS Light GUI does not work yet with Tizen:Base (we work on it) Feedback is welcomed. Our buzilla is here https://bugs.meego.com/buglist.cgi?product=Development%20Tools&component=OB… <https://bugs.meego.com/buglist.cgi?product=Development%20Tools&component=OB…> -- Dominig ar Foll Senior Software Architect Open Source Technology Centre Intel SSG -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0

[opensuse-buildservice] remote error: connect to api.opensuse.org 443 Connection timed out
by Magnus Lewis-Smith 30 May '12

30 May '12

Since Tue May 29 17:20:23 UTC 2012 the error message remote error: connect to api.opensuse.org 443 Connection timed out (or similar) is appearing throughout the log files of my local OBS install. No server builds are happening. In addition, local builds (osc build) of packages from my OBS and any osc communication (osc up etc) with the openSUSE one are also timing out. Is this likely to be related to the ongoing server storage problems? Regards Magnus Lewis-Smith -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 2

[opensuse-buildservice] OBS Light releases the Alpha version of the FakeOBS addon.
by Dominig ar Foll (Intel OTC) 30 May '12

30 May '12

Hello, The OBS Light team http://wiki.meego.com/OBS_Light has just released the Beta version off the OBSLight-fakeobs addon. FakeOBS has been originally created by the MER project and we have modified it for our needs. Our goal was to ease the import of a pre-boot strapped full distribution such as MeeGo TV or Tizen IVI in a private OBS instance. OBSLight-fakeobs enable to deliver pre-boot strapped complete OBS project(s) as a simple tar file (might be big!) which can be added to an OBSLight-server by a simple command. The added new project(s) is accessible through obslight server via the fakeobs project link. Branching of any packages is possible and building against the added project is availble by a simple click on an icon. As the tools to create the tar file are not yet well documented, we have created a set of three projects tar file for easy import as a demo. We have used the recently published Tizen IVI. Tizen_1.0_Base-1.0.tar.gz, Tizen_1.0_IVI-1.0.tar.gz, Tizen_1.0_Main-1.0.tar.gz They can be found on test hosting http://tizen.fridu.net/ .It will likely be removed in few weeks. Known Limits and bugs ----------------------------- - after installation of the package obslight-fakeobs you still to activate the service for reboot with the command insserv /etc/init.d/fakeobs (should be corrected soon and might have gone before that you test) - you cannot walk the available project pointed by the fakeobs link project from the WebUI (that limit is there to sati for a while) fakeobs:Tizen:1.0:Main:Main fakeobs:Tizen:1.0:Base fakeobs:Tizen:1.0:IVI - we do our test only with obslightserver appliance. It should work with any OBS but that is out of our focus. - when creating a branch the project name auto completion is not available you need to enter it (e.g. fakeobs:Tizen:1.0:Base) - when creating a branch the package name auto completion is not reliable. You might need to enter the package name in total. - OBS Light GUI does not work yet with Tizen:Base (we work on it) Feedback is welcomed. Our buzilla is here https://bugs.meego.com/buglist.cgi?product=Development%20Tools&component=OB… <https://bugs.meego.com/buglist.cgi?product=Development%20Tools&component=OB…> -- Dominig ar Foll Senior Software Architect Open Source Technology Centre Intel SSG -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0

[opensuse-buildservice] JFYI, > 800 repos were broken
by Adrian Schröter 29 May '12

29 May '12

JFYI, OBS is currently triggered to re-generate about 800 repositories. These repositories contained rpm package files, which were not part of the metadata due to broken cache files. So, when your user reported not working installations, because of missing packages in the last 5 days, this was maybe the reason. Should be processed until tomorrow. bye adrian -- Adrian Schroeter SUSE Linux Products GmbH email: adrian(a)suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 2

[opensuse-buildservice] Fedora, Mandriva and debuginfo packages
by Claudio Freire 27 May '12

27 May '12

Hi list. I've been having some issues for a while with Mandriva and debuginfo package generation. I've worked around the issue disabling debuginfo generation on them, but now Fedora jhas just started acting up in the same way: + exec rpmbuild -ba --define '_srcdefattr (-,root,root)' --nosignature --define 'disturl obs://build.opensuse.org/home:klaussfreire/Fedora_15/0065a286c8acac10270100…' --eval %suse_insert_debug_package /home/abuild/rpmbuild/SOURCES/vegastrike.spec error: Package already exists: %package debuginfo I wonder if there's a way to fix it without disabling debuginfo - debuginfo is a great tool for debugging when someone reports a bug, so I'd prefer not to disabe it everywhere. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 2

[opensuse-buildservice] OBS Team looks for a new member
by Adrian Schröter 25 May '12

25 May '12

You think you could let run the OBS better? Fix more obvious bugs we do not see? Implement great new stuff if you just would have the time? And Nuernberg or Prag are anyway nice cities to live? (They are, most of us were not born here). So, you may want to read about our new open position: http://www.open-build-service.org/2012/05/25/the-open-build-service-team-at… Feel free to ask any questions about the job either on this list or private. adrian -- Adrian Schroeter SUSE Linux Products GmbH email: adrian(a)suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0

[opensuse-buildservice] regression in API request handling by commit 6fd139a1dbc2dfff9cbce7f6555c4c63e11f6a65
by Robert Schiele 25 May '12

25 May '12

Hi Adrian and all, I found a regression in OBS code that was introduced with commit: commit 6fd139a1dbc2dfff9cbce7f6555c4c63e11f6a65 Author: Adrian Schröter <adrian(a)suse.de> Date: Fri Mar 9 10:34:23 2012 +0100 [api] mass-assignment is needed for xml object handover. Disallow hashed parameter values instead to ensure that we have no undetected leak yet. The problematic behavior seems to occur with specific text patterns like this: $ cat test.xml <request><description>;T[]</description></request> $ osc api -X POST /request?cmd=create -f test.xml Server returned an error: HTTP Error 400: Bad Request Parameter T has non String class Array $ As you can see OBS API seems to try to interpret the content of the description field. (???) Obviously this request is incomplete and also not very useful but the problem also occurs with reasonable requests as long as this specific text pattern is contained. Anyone with an explanation what goes wrong here or even a fix? I am personally quite confused since I don't even understand at the moment what exactly this change is trying to achieve. Was that checking probably applied to the wrong content in this XML file? Robert -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 2

[opensuse-buildservice] Update to 2.3 from 2.1 : problems
by Jon Nelson 24 May '12

24 May '12

First, the upgrade is nice, but I'm having some trouble. The first problem was a missing dependency on rubygem-rdoc. The second problem was that I hit a few database issues with migrate, and script/database_check. I did not know *how* to run that, but I eventually figured it out. Some docs there would be nice. I ended up learning that it only outputs SQL, but does not run that sql, so I ran the sql by hand. After that, and an apparently successful migrate, script/database_check output more errors. I'm using MySQL. Lastly, once I got it all up again, the webui gacks when I try to view any project. Ultimately, node.rb complains that _data is nil (line 197, it tries to use .xpath on _data which is nil at that point). So now I'm stuck. osc seems to work fine. -- Jon -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 2

[opensuse-buildservice] OBS 2.3.0-Build1.12 private installation problem
by Eric Richards 24 May '12

24 May '12

Greetings, Still learning how to setup OBS. Call me a slow learner. So, I create a project and select "Add Repositories to Project." I click on openSUSE 12.1, add selected repositories, and I get the error Failed to add project or repository: openSUSE.org:openSUSE:12.1 Likewise, if I try to add CentOS-6, I get Failed to add project or repository: openSUSE.org:CentOS:CentOS-6 OBS is looking in /srv/www/obs/api/files/distributions.xml for this information, but no documentation I've seen suggests that anything special needs to be done for this to work. Once again, I feel like I'm missing something obvious, but I could use a pointer. Regards, Eric -- Eric Richards Kernel Software Engineer SGI logo 1900 Pike Road Longmont, CO 80501 Phone: 303-532-0233 E-Mail: ERichards(a)sgi.com <mailto:ERichards@sgi.com> Website: www.sgi.com <http://www.sgi.com> -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 1

[opensuse-buildservice] build.opensuse.org downtime
by Adrian Schröter 24 May '12

24 May '12

Due to ongoing problems with our binary storage server we will not enable server side builds for today. Access to api.o.o and build.o.o is possible, so source modifications and local builds are working. sorry for that adrian -- Adrian Schroeter SUSE Linux Products GmbH email: adrian(a)suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 5

[opensuse-buildservice] build.opensuse.org down?
by Magnus Lewis-Smith 24 May '12

24 May '12

https://build.opensuse.org/ is returning 503 "Down for Maintenance" and hence my local OBS install is also down. Did I miss an announcement on this list? Magnus Lewis-Smith -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 5

RE: [opensuse-buildservice] OBS2.3 arm cross-build missing "copying qemu" step
by Rick Liu 24 May '12

24 May '12

> The release notes contain some comments about this IIRC. > [Rick Liu] In release notes: --------------------------------- * cross compile: copying installed qemu binaries into the worker is still supported but deprecated. It is suggested to install qemu instead. --------------------------------- Where are qemu binaries copied from? from obs server into the worker or from obs worker host into the worker chroot environment? Where is suggested to install qemu? install qemu package on obs server or on obs worker? Rick -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 1

Re: [opensuse-buildservice] Branch doesn't update after updating of original project
by Dmitriy Perlow 23 May '12

23 May '12

I run the service and it used old version of spec. _______ Dmitriy Perlow / Sony Ericsson ---- Original message ---- From: Adrian Schröter <adrian(a)suse.de> Sent: ‎23-May‎-2012 14:05 To: opensuse-buildservice(a)opensuse.org Cc: Dmitriy Perlow <dap(a)open.by> Subject: Re: [opensuse-buildservice] Branch doesn't update after updating of original project Am Mittwoch, 23. Mai 2012, 09:53:17 schrieb Dmitriy Perlow: > So should I just run the service in my project? yes

1 0

Re: [opensuse-buildservice] Branch doesn't update after updating of original project
by Dmitriy Perlow 23 May '12

23 May '12

So should I just run the service in my project? _______ Dmitriy Perlow / Sony Ericsson ---- Original message ---- From: Adrian Schröter <adrian(a)suse.de> Sent: ‎23-May‎-2012 08:51 To: opensuse-buildservice(a)opensuse.org Cc: Dmitriy Perlow <dap(a)open.by> Subject: Re: [opensuse-buildservice] Branch doesn't update after updating of original project No, it is by design currently. changes in linked packages do not trigger services atm. -- Adrian Schroeter SUSE Linux Products GmbH email: adrian(a)suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 1

[opensuse-buildservice] rpm depends: packageA OR packageB?
by Isaac Hailperin 23 May '12

23 May '12

Hi, I would like to specify that a package needs either packageA OR packageB. E.g. I want a Database, but don't care if its mysql or postgresql. For debs there is the "|", but I could not find something like this for rpms. Is it just like that? Isaac -- Isaac Hailperin -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

5 4

[opensuse-buildservice] OBS private installation
by Eric Richards 22 May '12

22 May '12

Hello, I'm brand new to OBS and am trying to set up a private instance of OBS. I'm following the directions at: http://en.opensuse.org/openSUSE:Build_Service_private_installation But the system I'm installing doesn't have the required files for portmap, and therefore NFS. a zypper what-provides portmap Tells me that rpcbind is the source. Now uninstalling and reinstalling all of rpcbind fails. You see, /sbin/portmap is not present. Now, my SUSE experience is very very dated, so I'm wondering: What am I doing wrong? (A full zypper up doesn't help...) Regards, Eric -- Eric Richards Kernel Software Engineer SGI logo 1900 Pike Road Longmont, CO 80501 Phone: 303-532-0233 E-Mail: ERichards(a)sgi.com <mailto:ERichards@sgi.com> Website: www.sgi.com <http://www.sgi.com> -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

4 5

[opensuse-buildservice] check-buildroot now executed on Fedora?
by Ruediger Meier 22 May '12

22 May '12

Hi, my build fails now on Fedora: + /usr/lib/rpm/check-buildroot Found '/home/abuild/rpmbuild/BUILDROOT/sxemacs-22.1.15.beta3.ccd4-0.x86_64' in installed files; aborting I see in old build logs that check-buildroot was not executed on Fedora some days/weeks ago. Has this been changed lately? cu, Rudi -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 1

[opensuse-buildservice] apache_sysconfdir macro confusion
by Isaac Hailperin 22 May '12

22 May '12

Hi, I have a spec file that defines apache_sysconfdir like %define apache_sysconfdir /etc/apache2 Later on I try to use that macro, but it appears that it does not get expanded. Just changing the name of the macro solved the problem. Which leads me to the conclusion that this special name is reserved and defined somewhere else. So if I just don't define it but still use it later on, its not expanded either. /usr/lib/rpm/macros does not specify any apache specific macro, I am a bit confused. Can someone enlighten me on this? Isaac -- Isaac Hailperin Heinlein Professional Linux Support GmbH Linux: Akademie - Support - Hosting http://www.heinlein-support.de Tel: 030-405051-45 Fax: 030-405051-19 Zwangsangaben lt. §35a GmbHG: HRB 93818 B / Amtsgericht Berlin-Charlottenburg, Geschäftsführer: Peer Heinlein -- Sitz: Berlin -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 4

[opensuse-buildservice] OBS can't recognize symbol "+" in project name or S.O.O can't transfer it properly.
by Marguerite Su 22 May '12

22 May '12

Hi, all, When I'm packaging linphone updates, I need to search package "tunnel". and found this "bug"? http://software.opensuse.org/package/stunnel click openSUSE_Factory. then show unstable packages we'll see the first project is devel:libraries:c_c++, click into it. OBS will return you an error messge "devel:libraries:c_c" not found, seems it can't recognize the last two "+". Marguerite. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

4 4

Re: [opensuse-buildservice] OBS private installation
by Eric Richards 21 May '12

21 May '12

Mauro, One disaster at a time, please! :-) Regards, Eric On 05/21/2012 10:54 AM, Mauro Parra wrote: > Hello, > If you think is broken, either create a bug report or just fix it. > It's free software, after all. > > Best, > Mauro > > On Monday, May 21, 2012, Eric Richards <erichards(a)sgi.com > <mailto:erichards@sgi.com>> wrote: > > Andrzej, > > > > I'm not setting the requirements on this, but I get what you're > saying. It just seems "broken" as opposed to not configured. > > > > Regards, > > > > Eric > > > > On 05/21/2012 09:58 AM, Andrzej Lisowski wrote: > >> > >> Hi Eric, > >> > >> If you are new to OBS than you might consider skipping the NFS part > for the time being as it's not crucial to get the OBS running. You can > come back to that part once you get more confidence with OBS. I don't > use this feature in my private OBS instance for the time being either. > >> > >> Best regards, > >> Andrzej. > >> > >> -----Original Message----- > >> From: Eric Richards [mailto:erichards@sgi.com > <mailto:erichards@sgi.com>] > >> Sent: Monday, 21 May, 2012 16:16 > >> To: opensuse-buildservice(a)opensuse.org > <mailto:opensuse-buildservice@opensuse.org> > >> Subject: [opensuse-buildservice] OBS private installation > >> > >> Hello, > >> > >> I'm brand new to OBS and am trying to set up a private instance of OBS. > >> I'm following the directions at: > >> > >> http://en.opensuse.org/openSUSE:Build_Service_private_installation > >> > >> But the system I'm installing doesn't have the required files for > portmap, and therefore NFS. a > >> > >> zypper what-provides portmap > >> > >> Tells me that rpcbind is the source. Now uninstalling and > reinstalling all of rpcbind fails. You see, /sbin/portmap is not present. > >> > >> Now, my SUSE experience is very very dated, so I'm wondering: What > am I doing wrong? (A full zypper up doesn't help...) > >> > >> Regards, > >> > >> Eric > > > > -- > > > > Eric Richards > > Kernel Software Engineer > > SGI logo > > 1900 Pike Road > > Longmont, CO 80501 > > Phone: 303-532-0233 > > E-Mail: ERichards(a)sgi.com <mailto:ERichards@sgi.com> > <mailto:ERichards@sgi.com <mailto:ERichards@sgi.com>> > > Website: www.sgi.com <http://www.sgi.com> <http://www.sgi.com> > > > > -- > > To unsubscribe, e-mail: > opensuse-buildservice+unsubscribe(a)opensuse.org > <mailto:opensuse-buildservice%2Bunsubscribe@opensuse.org> > > To contact the owner, e-mail: > opensuse-buildservice+owner(a)opensuse.org > <mailto:opensuse-buildservice%2Bowner@opensuse.org> > > > > > > -- > Saludos, > > Mauro Parra-Miranda > CTO @ NegoApps > Titanium Certified App Developer > Titan @ Appcelerator > MobileCamp MX Founder - http://mobilecamp.mx > IronHacker Founder - http://ironhacker.com > ☎ +52 1 (55) 2306 8865 Mobile > -- Eric Richards Kernel Software Engineer SGI logo 1900 Pike Road Longmont, CO 80501 Phone: 303-532-0233 E-Mail: ERichards(a)sgi.com <mailto:ERichards@sgi.com> Website: www.sgi.com <http://www.sgi.com> -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0

[opensuse-buildservice] working past "excluded" status when trying to build a package.
by .. ink .. 21 May '12

21 May '12

Hi everyone, first time here so my advance apologies if i am breaking any rules i am currently not aware of in posting to the list. I have a project named zuluCrypt at https://build.opensuse.org/project/show?project=home%3Amhogomchungu and i cant seem to get it to build. The repository i have selected have "excluded" mark to them and its been weeks now i have tried to work past them to no avail.I must be doing something wrong but i cant seem to see what is it. Any assistance will be appreciated. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 2

[opensuse-buildservice] High-level architecture diagram of the open build service
by Sankar P 21 May '12

21 May '12

Hi, Is there a high-level architecture/design diagram or a mindmap of what components of OBS does what ? Like for eg, a schematic representation that answers questions like, where ruby-on-rails is used, how are distributed builds done, how the distro images are stored and used etc. ? Is there any such design diagram or a wiki page that explains this ? On a related note, the page at http://www.open-build-service.org/documentation/ is very unfriendly in terms of screen space and the document seems to be incomplete. Please CC me in the replies. Thanks. -- Sankar P http://psankar.blogspot.com -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 2

[opensuse-buildservice] opensuse "Package Search" is confused by the package peless.
by Paul Elliott 21 May '12

21 May '12

Projects > home:pelliott11:peless > Packages > peless exists: https://build.opensuse.org/package/show?package=peless&project=home%3Apelli… The truck for xUbuntu_12.04 shows "Repository has been published" The results of opensuse package search http://software.opensuse.org/121/en Does not seem to depend at all on the "Show distribution" field. But when you do a search for "peless", it does not show any results for xUbuntu_12.04. In addition it shows this wierd entry for "home pelliott11 autoconf-archive". The project autoconf-archive does not contain any "peless" packages, although peless does build-depend on it. If one takes the link for "32bit" for Ubuntu 11.04 which reads: http://download.opensuse.org/repositories/home:/pelliott11:/peless/xUbuntu_… and extrapolate it to Ubuntu 12.04 it would read http://download.opensuse.org/repositories/home:/pelliott11:/peless/xUbuntu_… If one looks therefore in http://download.opensuse.org/repositories/home:/pelliott11:/peless/xUbuntu_… one finds, sure enough, a file named peless_1.259-1_i386.deb So the repository is there, it is just not listed by "Package Search". What is happening here? Could it be that my browser, both firefox and rekonq from ubuntu is not showing the continued page links? What is happening with the autoconf-archive entry? Thank You. -- 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

1 0

[opensuse-buildservice] signing server hanging?
by Joop Boonen 20 May '12

20 May '12

It looks like the signing server is hanging. Quite a few packages are hanging in the signing stage. Regards, Joop. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 3

[opensuse-buildservice] What createrepo is the OBS using?
by Cristian Morales Vega 19 May '12

19 May '12

Related to this Packman bug: https://bugs.links2linux.org/browse/PM-4 https://gitorious.org/opensuse/build-service/blobs/2.3/src/backend/bs_publi… has a nice comment about 0.4.10... I think it's outdated ;-) The thing is that I can see these two versions: https://build.opensuse.org/package/files?package=createrepo&project=DISCONT… and https://build.opensuse.org/package/files?package=createrepo&project=system%… The important part is createrepo-0.4.11-missing-tags.patch, which adds support for soft dependencies (to the best of my knowledge still a suse specific RPM patch), that doesn't seems to be available for createrepo 0.9.9. So, since I don't see createrepo 0.4.11 built for any recent openSUSE version. What version of create repo are you using in the main OBS instance? -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 3

[opensuse-buildservice] optional / recommends buildrequires
by Brian K. White 19 May '12

19 May '12

Is there a way to tell the build service to include package libfoo-devel in the build environment for a given package without making it a buildrequires in the spec? Or is there a BuildRecommends or use-if-available-but-no-error-if-not-available? -- bkw -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

6 8

[opensuse-buildservice] obs services idle
by doiggl＠velocitynet.com.au 18 May '12

18 May '12

Hello, Today I noticed many obs services idle https://build.opensuse.org/monitor Glenn -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0

[opensuse-buildservice] multiple sources in .deb?
by Isaac Hailperin 16 May '12

16 May '12

Hi, in rpms I can define multiple sources. For debs I could not find a way to do it. Is there a way? Isaac -- Isaac Hailperin Heinlein Professional Linux Support GmbH Linux: Akademie - Support - Hosting http://www.heinlein-support.de Tel: 030-405051-45 Fax: 030-405051-19 Zwangsangaben lt. §35a GmbHG: HRB 93818 B / Amtsgericht Berlin-Charlottenburg, Geschäftsführer: Peer Heinlein -- Sitz: Berlin -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

4 3

[opensuse-buildservice] Mirroring base distributions to private OBS instance
by Andrzej Lisowski 16 May '12

16 May '12

Hi, I'm busy with piloting private OBS instance at our company. So far the results are promising and we received positive feedback from the first users. I have been requested though to make sure that our private OBS instance will be able to run independent from public one at https://build.opensuse.org/ I understood that in order to achieve that I need to mirror so called base distributions from https://build.opensuse.org/ I tried initially to mirror the RedHat:RHEL-6 and SUSE:SLE-11:SP2 to my local instance but unfortunately without success. I followed the instruction that is provided with OBS RPMs i.e. /usr/share/doc/packages/obs-server/README.SETUP and I tried to follow the WiKi http://en.opensuse.org/openSUSE:Build_Service_private_instance_boot_strappi… Unfortunately none of these procedures provided expected results. My basic problem is that the imported SLES and RHEL projects are not recognized by OBS backend after import those project using the obs_mirror_project command. I tried various tricks like for example restarting OBS scheduler or rescanning repository using command /usr/lib/obs/server/bs_admin --rescan-repository $PROJECT $REPO $ARCH but without any luck. I can see that SLES and RH RPM packages are properly imported to the /srv/obs/build directory and the project files the xml and conf files appear in the /srv/obs/projects. They don't appear in the mySQL DB though as other projects that are created manually. The base distributions do not appear in my private instance in the list of the projects in a way as you can see it on the public OBS instance either. I received advice that I should run /srv/www/obs/api/script/import to finalize the import but I was not able to find any further information about how to apply this command. I would appreciate if someone could please provide me with hints on how can I mirror the base distribution from the public OBS instance to our private one. I'm running OBS 2.3 RC on top of SLES 11 SP2 64 bit. Thanks in advance, Andrzej.-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0

[opensuse-buildservice] Avoiding the rpm signing warnings for Fedora
by Frank Lichtenheld 16 May '12

16 May '12

Hi. All builds against Fedora_16 on OBS currently throw a lot of warnings during chroot setup due to missing key for checking the package signatures. This does not seem to cause any problems but it irritated me (since it makes this part of the log very hard to read) and so I did investigate how this happens. The problem is as follows: - "build" usually uses --nosignature - But it wants to do so only for rpm v4, not v3 (probably v3 didn't have the option?) - It checks the rpm version not by checking the rpm version but by checking for the existence of the program "rpmsign" in the chroot - In Fedora (at least 15 and 16, i.e. the OBS-supported versions) the program "rpmsign" is not in the "rpm" rpm, but in the "rpm-sign" rpm - The "rpm-sign" rpm is not installed by the current Fedora:16 project config Possible solutions: 1) add "Preinstall: rpm-sign", "Required: rpm-sign" to Fedora:16 project config (I tested it and it indeed does avoid the warnings) 2) just remove the check from "build", does anyone still use ancient rpm? 3) change the check to something that doesn't require the presence of the rpmsign binary 1 is clearly the easy way out, but if you would prefer 2 or 3 I would be happy to make a patch for build. Gruesse, -- Frank Lichtenheld Lead Engineer email: frank.lichtenheld(a)sophos.com tel: +49 721 25516-362 cell: +49 174 1748211 SOPHOS You're safer in our world Unified | Web | Email | Endpoint | Mobile | Network | Data -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 3

[opensuse-buildservice] configure logrotate - best practice
by Isaac Hailperin 16 May '12

16 May '12

Hi, I am building a package that needs to configure logrotate. Now two possiblities come to my mind: a) Put /etc/logrotate.d/mypackage in the rpm and install it just like any other file from the package b) Create /etc/logrotate.d/mypackage with a postinstall script I was wondering which way is the "best" or most common way to do things like this for rpms. But also in the light of the build service, where I want to create rpms and debs alike. Best, Isaac -- Isaac Hailperin Heinlein Professional Linux Support GmbH Linux: Akademie - Support - Hosting http://www.heinlein-support.de Tel: 030-405051-45 Fax: 030-405051-19 Zwangsangaben lt. §35a GmbHG: HRB 93818 B / Amtsgericht Berlin-Charlottenburg, Geschäftsführer: Peer Heinlein -- Sitz: Berlin -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 4

[opensuse-buildservice] Translated descriptions of packages on software.opensuse.org
by Andrey Gankov 16 May '12

16 May '12

Hi, Please tell, are you have any plans to implement display translated package descriptions for the new software.opensuse.org I think that descriptions in native language would be a very demand feature for non-English speaking users. We have a lot of translations into Russian. Probably translations into other languages, too, is enough. Thanks. -- Andrey Gankov openSUSE Member Email:gankov@opensuse.org -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

5 14

[opensuse-buildservice] Old repo policy?
by Joop Boonen 16 May '12

16 May '12

Hi All, I wonder what the policy is related to outdated repos? I see for example that packages are still being build for openSUSE 11.3 < in for instance project server:mail, Application:Geo and probably quite few more. Should this be like this, isn't this a waste of resources? Regards, Joop. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 1

[opensuse-buildservice] 2.1 -> 2.3 upgrade problem
by Troy Telford 15 May '12

15 May '12

I've had a system in production for a few years now; I've upgraded from 2.1 -> 2.3, and have the following problem, and I figure I need to fix it to continue. (--trace added to increase verbosity) As a result, my OBS system is now down, and I kinda need to get it going again quickly: Change this error message for exceptions thrown outside of an action (like in Dispatcher setups or broken Ruby code) in public/500.html # RAILS_ENV="production" rake db:migrate --trace (in /srv/www/obs/api) ** Invoke db:migrate (first_time) ** Invoke environment (first_time) ** Execute environment ** Execute db:migrate == AddIndexForAttributes: migrating ========================================== -- add_index(:attrib_types, [:attrib_namespace_id, :name], {:unique=>true}) rake aborted! An error has occurred, all later migrations canceled: Mysql::Error: Duplicate entry '1-RequestCloned' for key 'index_attrib_types_on_attrib_namespace_id_and_name': CREATE UNIQUE INDEX `index_attrib_types_on_attrib_namespace_id_and_name` ON `attrib_types` (`attrib_namespace_id`, `name`) /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.14/lib/active_record/connection_adapters/abstract_adapter.rb:227:in `log' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.14/lib/active_record/connection_adapters/mysql_adapter.rb:324:in `execute' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.14/lib/active_record/connection_adapters/abstract/schema_statements.rb:292:in `add_index' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.14/lib/active_record/migration.rb:352:in `send' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.14/lib/active_record/migration.rb:352:in `method_missing' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.14/lib/active_record/migration.rb:328:in `say_with_time' /usr/lib64/ruby/1.8/benchmark.rb:293:in `measure' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.14/lib/active_record/migration.rb:328:in `say_with_time' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.14/lib/active_record/migration.rb:348:in `method_missing' ./db/migrate//20120223105426_add_index_for_attributes.rb:4:in `up_without_benchmarks' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.14/lib/active_record/migration.rb:282:in `send' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.14/lib/active_record/migration.rb:282:in `migrate' /usr/lib64/ruby/1.8/benchmark.rb:293:in `measure' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.14/lib/active_record/migration.rb:282:in `migrate' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.14/lib/active_record/migration.rb:365:in `__send__' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.14/lib/active_record/migration.rb:365:in `migrate' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.14/lib/active_record/migration.rb:491:in `migrate' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.14/lib/active_record/migration.rb:567:in `call' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.14/lib/active_record/migration.rb:567:in `ddl_transaction' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.14/lib/active_record/migration.rb:490:in `migrate' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.14/lib/active_record/migration.rb:477:in `each' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.14/lib/active_record/migration.rb:477:in `migrate' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.14/lib/active_record/migration.rb:401:in `up' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.14/lib/active_record/migration.rb:383:in `migrate' /usr/lib64/ruby/gems/1.8/gems/rails-2.3.14/lib/tasks/databases.rake:112 /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:636:in `call' /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:636:in `execute' /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:631:in `each' /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:631:in `execute' /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:597:in `invoke_with_call_chain' /usr/lib64/ruby/1.8/monitor.rb:242:in `synchronize' /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:590:in `invoke_with_call_chain' /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:583:in `invoke' /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2051:in `invoke_task' /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in `top_level' /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in `each' /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in `top_level' /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2068:in `standard_exception_handling' /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2023:in `top_level' /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2001:in `run' /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2068:in `standard_exception_handling' /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:1998:in `run' /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/bin/rake:31 /usr/bin/rake:19:in `load' /usr/bin/rake:19 -- Troy Telford -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 2

[opensuse-buildservice] Project request
by Schlomo Schapiro 15 May '12

15 May '12

Hi, I need a project work space and submitted a bug for this: https://bugzilla.novell.com/show_bug.cgi?id=761640 When can we expect any action on this? We really would like to meet the LinuxTag next week with our "new" package build space for the Relax and Recover project. It would be really great if this would work out. Thanks a lot, Schlomo -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 1

[opensuse-buildservice] To %make_install or to %makeinstall (spec-cleaner)
by Joop Boonen 15 May '12

15 May '12

Hi all, I have been using spec cleaner for while. What I notice it that it uses macro %make_install instead of %makeinstall. Both macros are OK for openSUSE but the first one breaks the build for SLE. <quote> + %make_install /var/tmp/rpm-tmp.59594: line 45: fg: no job control </quote> I wonder if this should be fixed, in either spec-cleaner (use%makeinstall in stead of %make_install) or in the buildserver (add macro %make_install for SLE)? Regards, Joop. See also: https://bugzilla.novell.com/show_bug.cgi?id=712171 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

7 11

[opensuse-buildservice] Solution for compiling kernel modules for openSUSE:Tumbleweed (and Kernel:stable)
by Paolo Pantò 13 May '12

13 May '12

Originally posted in http://forums.opensuse.org/english/get-technical-help-here/tumbleweed/47452… Hi, I don't know if this is the right place to post. The "problem" concerns various scopes - Tumbleweed - Kernel(:stable) - Open Build Service (OBS) Currently it is not possible to compile kernel modules for openSUSE:Tumbleweed (and Kernel:stable) for the i586 arch on OBS. Have a look eg. at - https://build.opensuse.org/project/show?project=multimedia%3Aaudio%3AKMP - https://build.opensuse.org/project/show?project=Virtualization%3AVirtualBox… For now the entry for i586 reads "unresolvable": nothing provides kernel-desktop-devel = 3.3.2-20 needed by kernel-syms, nothing provides kernel-pae-devel = 3.3.2-20 needed by kernel-syms, nothing provides kernel-xen-devel = 3.3.2-20 needed by kernel-syms The reason is that the project configs for openSUSE:11.4/standard, on which Kernel:stable depends, and openSUSE:12.1/standard, on which openSUSE:Tumbleweed depends, includes the line ExportFilter: \.i686\.rpm$ i686 New kernels are built with "BuildArch: i686" on %ix86, the ExportFilter config makes it impossible for other packages to find the proper devel-packages - kernel-default is still build for i586. I've created a sample environment on OBS with - https://build.opensuse.org/project/show?project=home%3Amunix9%3AKernel%3A11… - https://build.opensuse.org/project/show?project=home%3Amunix9%3AKernel%3ATu… This projects aggregates the problematic packages and contains the project config line ExportFilter: \.i686\.rpm$ i586 Now kernel modules are built fine, eg. for virtualbox https://build.opensuse.org/project/monitor?project=home%3Amunix9%3AVirtuali… On openSUSE:Factory (on which eg. Kernel:HEAD depends) it works already fine, because the appropriate line "ExportFilter: \.i686\.rpm$ i686" is missing. If I'm right, then a global solution would make sense, to allow also other projects to build proper kernel modules. Ciao, Paolo -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

4 4