May 2012 - openSUSE Build Service - openSUSE Mailing Lists

[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