openSUSE Build Service September 2012

buildservice@lists.opensuse.org

56 participants
50 discussions

[opensuse-buildservice] Open Build Service(OBS) 2.3.4 released

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

6 years, 4 months

[opensuse-buildservice] 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, 11 months

[opensuse-buildservice] 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

8 years, 3 months

[opensuse-buildservice] 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, 7 months

[opensuse-buildservice] Use Macro with source service?

by Ann Davis

Hi all, I have a package that uses the download_files source service to get a file that is listed as Source0 in the spec file. This works fine if Source0 lists the exact filename, but not if Source0 contains a macro. This works with the source service: ... Source0: http://www.kernel.org/pub/linux/kernel/projects/backports/2012/09/18/compat… ... This doesn't work with the source service: ... Source0: http://www.kernel.org/pub/linux/kernel/projects/backports/2012/09/18/compat… -d '1 day ago' +%Y-%m-%d).tar.bz2 ... Using a macro in the Source0 filename works ok if there's no source service. So any ideas on how to make it work w/ a source service? Thanks very much in advance, Ann -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

8 years, 8 months

[opensuse-buildservice] Please add 'redhat-rpm-config' to global config for Centos/RHEL 6 to fix the naming issue of debuginfo package

by Gris Ge

Hi OBS Admin Team, Please add rpm package 'redhat-rpm-config' to fix naming issue of debuginfo package in Centos/RHEL 6. This issue has been reported to this list before: http://lists.opensuse.org/opensuse-buildservice/2012-08/msg00042.html I verified this in my repo home:cathay4t:misc-rhel6 for cmake package by add this line to spec file: BuildRequires: redhat-rpm-config Adding 'redhat-rpm-config' to Centos 6 global config would enough as RHEL 6 of OBS seems missing optional repo which contain devel pacakges. Thanks. Best regards. -- Gris Ge -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

8 years, 8 months

[opensuse-buildservice] new osc 0.136.0 release

by Marcus Hüwe

Hi, we are happy to announce the osc 0.136.0 release. This release is mostly a bugfix release and contains the following changes: * prefer TLS v1.1 or v1.2 if available * declined is considered to be an open state (that is "osc rq list" also shows declined requests) * added support to move files across packages via "osc mv" (fixes issue "#10") * various bugfixes: - show source package name when running "osc se --binary ..." - fixed encoding detection - fixed build result listing for arch packages (affects "osc build") - "osc ci --noservice" also works for "external"/flat packages Thanks to everyone who contributed to osc! 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, 8 months

[opensuse-buildservice] debian conversion fail

by Klaas Freitag

Hi, I am seeing this problem in my builds on OBS, while local builds work nicely: [ 86s] now finalizing build dir... [ 87s] running debian transformer... [ 87s] converting //usr/src/packages/SOURCES/owncloud-4.5.0.RC1.tar.bz2 to owncloud-4.5.0.RC1.tar.gz [ 94s] tar: owncloud-4.5.0.RC1.tar.gz: Cannot open: No such file or directory [ 94s] tar: Error is not recoverable: exiting now What is the problem? Thanks, Klaas -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

8 years, 8 months

[opensuse-buildservice] debian transformer complains about symlinks

by Nico Kruber

Recently, the debian transformer complains about symlinks in archives and thus fails the build. Relative symlinks should not be a problem though as long as they point to a location still inside the archive. This should be ignored and not transform into a failure imho. see https://build.opensuse.org/package/live_build_log?arch=x86_64&package=scala… svn&project=home%3Ascalaris%3Asvn&repository=Debian_5.0 Nico -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

8 years, 9 months

[opensuse-buildservice] build error for sles10

by Michael Behrisch

Hi, can anyone help me with this error: [ 85s] [70/197] installing liblapack3-3.4.1-7.2 [ 87s] [71/197] installing fontconfig-2.3.94-18.16 [ 87s] [72/197] installing libtiff-3.8.2-5.9 [ 87s] [73/197] installing lapack-devel-3.4.1-7.2 [ 90s] [74/197] installing libgeos-devel-3.3.5-1.3 [ 91s] [75/197] installing hdf-devel-4.2r3-20.1 [ 91s] [76/197] installing mpfr-2.2.1-6.6 [ 92s] [77/197] installing lapack-3.0-939.4 [ 92s] file /usr/lib64/liblapack.a from install of lapack-3.0-939.4 conflicts with file from package lapack-devel-3.4.1-7.2 [ 92s] exit ... (full log: https://build.opensuse.org/package/live_build_log?arch=x86_64&package=libgd… ) If I understand it correctly it tries to install lapack (maybe the one coming with the distro) which is already installed in a newer version coming from Application:Geo. But how can I find out why? And why does the build work for i586? Thanks in advance for any hints, Michael -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

8 years, 9 months

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Build Service September 2012