openSUSE Build Service August 2012

buildservice@lists.opensuse.org

48 participants
53 discussions

by Adrian Schröter

Open Build Service(OBS) 2.3.4 just got released =============================================== This is a bugfix release in first place. But also the distribuition default target list has been updated. This release is most important for cross build support. Building against openSUSE 12.2 and Factory for ARM architecture works now out-of-the-box. OBS 2.3.4 is published in "openSUSE:Tools" project: http://download.opensuse.org/repositories/openSUSE:Tools/ Appliances can be used as usual: http://en.opensuse.org/openSUSE:Build_Service_Appliance Release Notes: ============== Feature backports: ================== * Added "Hostarch" in _buildinfo for osc local builds of cross builds Changes: ======== * package meta creation of package copy command is not copying relationships and devel definitions anymore. * Added openSUSE 12.2 to default target list * Removed openSUSE 11.4 from default target list (EOL soon) * Fedora 15 is EOL, removed from default list Bugfixes: ========= * backend: allow access to access protected project repositories when users are in both projects. * backend: increase vrev on package source copy * webui: fixed underscores in code listings * webui: Do not expose user email address in anonymous mode * obsworker: do not fail when no /etc/sysconfig/proxy exists * build: fixed cross architecture initilisation for chroot builds -- 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 years, 9 months

Expired OBS Keys?

by King Thorin

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

7 years, 4 months

New project openSUSE:Current?

by Cristian Morales Vega

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

7 years, 8 months

Problem building Perl packages for SLES11SP2 with certain build requirements

by Joschi Brauchle

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!

8 years

openSUSE 11.4 ... do not disable repos on EOL?

by Marcus Meissner

Hi, Given the large amounts of negative feedback we get when we disable the build repositories of just EOLed openSUSE distributions ... and as 11.4 is targeted to be a Evergreen target again... How about NOT removing the openSUSE 11.4 repositories this time? We could still remove the openSUSE 11.4 repos below home:* but perhaps not for the rest of the namespace. Ciao, Marcus -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

8 years, 2 months

Re: unity for openSUSE

by Adrian Schröter

Am Donnerstag, 23. August 2012, 13:24:15 schrieb Damian Ivanov: ... > Dear guys from OBS, dear Adrian: > I would ask you for a favor: > Could you please make it possible that we can add Fedora Updates and > Fedora Update-testing repo (if Fedora Rawhide would be supported too, > that would be brilliant) , we really need this (at the moment we use > some ugly hacks > having rpms from fedora updates in our source in OBS, which puts load > on your servers > and we can spend less time on the openSUSE port of unity) Since fedora updates are not static repos and our download on demand feature is not supporting non-static repositories atm, I do not want to add these repos, because I would need always manually to update it. If it is just one or two packages you need, I can once import them manually though. > Also please drop me a private message too (in case I am not on the > mailing list) when the OBS arch backend is arrived. It should be active already on build.opensuse.org. It is complete, but officially still experimental and not yet released :) > Xiao-Long Chen is also the maintainer of the successful port of unity > to arch (though he moved to Fedora as main distro) and we'd love to > just add the PKGBUILD > files to the packages in GNOME:Ayatana and these packages would > provide unity for SuSE, Fedora and Arch! Try it and tell ... > If someone wants to join us for a port of unity to other OBS supported > architectures feel free to contact us. > > Cheers, > Damian > -- 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

8 years, 2 months

obs-worker cleanup chroot build environment / after build script

by Florian Kabus

Hello, related to the "obs-worker - restarting services in chroot env at build time" mailing we still have some problems to get a more or less "clean" chroot build environment on a dedicated obs-worker machine. Therefore the question: Is there an (scripting) entry point to cleanup the obs-worker chroot build environment after _every_ build of a package even if the build has failed? In our case we have to kill some services like mysql or apache2 to ensure that they aren't running accidently after a (failed) build on the obs-worker. Your help is again very much appreciated. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

8 years, 2 months

archlinux with ARM Architecture

by Florian Kellmer

Hi, Will it be possible to build ArchLinux for the ARM Architecture in the near future? At the moment one can add ARM to the repositories but it seems that there aren't any packages inside of it because even gcc is unresolvable. Best Regards Florian -- -- () ascii ribbon campaign | Florian Kellmer /\ - against HTML e-mail | http://www.asciiribbon.org | GPG ID: 0x6C6E3C0C --

8 years, 2 months

Build loop with Arch backend

by Florian Kellmer

Hey @ all, I noticed that there is a problem with building hsolink. https://build.opensuse.org/package/show?package=hsolink&project=home%3Afloy… Everytime when the build process was succesfully the build is started again. Could someone please take a look to determine where the problem is? I tied to build it for Arch_Core_standard x86_64. greets florian -- -- () ascii ribbon campaign | Florian Kellmer /\ - against HTML e-mail | http://www.asciiribbon.org | GPG ID: 0x6C6E3C0C --

8 years, 2 months

create groups on OBS instance

by Aaron Yung

Hi All Is there any way to create groups in my own OBS instance( Version 2.3) ? Any body can help me ? Thanks a lot ----- Go OBS -- View this message in context: http://opensuse.14.n6.nabble.com/create-groups-on-OBS-instance-tp4972640.ht… Sent from the opensuse-buildservice mailing list archive at Nabble.com. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

8 years, 2 months

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Build Service August 2012