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