April 2012 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] Problems with not existing dependencies for ubuntu which should exist
by Erik Schilling 13 Apr '12

13 Apr '12

Hello, i am trying to build packages for ubuntu. The strange thing is that i get problems with dependencys though ubuntu should have all the build dependencies in their repositories (I can successfully build the package on launchpad). Well it looks like i am building with a different repository that the official ubuntu one. But since i do not changed anything according to that in the project meta data i do not know how this should work... Has anyone an idea what i am doing wrong? Thanks for help in advance. So this is how i tried building: ~/osc/games/mana > osc build xUbuntu_11.04 mana.dsc --no-service WARNING: source service from package or project will not be executed. This may not be the same build as on server! Building mana.dsc for xUbuntu_11.04/i586 Getting buildinfo from server and store to /home/ablu/osc/games/mana/.osc/_buildinfo-xUbuntu_11.04-i586.xml Getting buildconfig from server and store to /home/ablu/osc/games/mana/.osc/_buildconfig-xUbuntu_11.04-i586 buildinfo is broken... it says: unresolvable: nothing provides libsdl-gfx1.2-dev, nothing provides libphysfs-dev, nothing provides libguichan-dev, nothing provides libsdl-mixer1.2-dev, nothing provides libsdl-net1.2-dev, nothing provides libsdl-ttf2.0-dev My .dsc: ~/osc/games/mana > cat mana.dsc Format: 1.0 Source: mana Binary: mana, mana-dbg, mana-data Architecture: any Version: 0.6.1 Maintainer: Erik Schilling <ablu.erikschilling(a)googlemail.com> Homepage: http://www.manasource.org/ Standards-Version: 3.9.2 Build-Depends: debhelper (>= 7), cmake, libsdl-gfx1.2-dev, libcurl4-gnutls-dev, libxml2-dev, libphysfs-dev, libguichan-dev, libsdl-mixer1.2-dev, libsdl-net1.2-dev, libsdl-ttf2.0-dev, hardening-wrapper Meta data of the package: ~/osc/games/mana > osc meta pkg games/mana <package project="games" name="mana"> <title>The Mana Client</title> <description>This package contains the Mana Client. See http://manasource.org/ for more information.</description> <person role="maintainer" userid="Ablu"/> <build> <enable repository="Fedora_16"/> <disable repository="Fedora_15"/> <enable repository="xUbuntu_11.04"/> </build> <url>http://manasource.org</url> </package> Meta data of the project: ~/osc/games/mana > osc meta prj games <project name="games"> <title>Games</title> <description>for Gamers by Gamers</description> <person role="maintainer" userid="matejcik"/> <person role="maintainer" userid="hhetter123"/> <person role="maintainer" userid="wstephenson"/> <person role="maintainer" userid="pbleser"/> <person role="maintainer" userid="lrupp"/> <person role="maintainer" userid="anicka"/> <person role="maintainer" userid="hmacht"/> <person role="maintainer" userid="gekker"/> <person role="maintainer" userid="dimstar"/> <person role="maintainer" userid="dstoecker"/> <person role="maintainer" userid="prusnak"/> <person role="maintainer" userid="jengelh"/> <person role="maintainer" userid="psmt"/> <person role="maintainer" userid="pgajdos"/> <person role="maintainer" userid="WernerFink"/> <person role="maintainer" userid="maxmaher"/> <person role="maintainer" userid="RedDwarf"/> <person role="maintainer" userid="bitshuffler"/> <person role="maintainer" userid="mseben"/> <person role="maintainer" userid="PVince81"/> <person role="maintainer" userid="Ansus"/> <person role="bugowner" userid="prusnak"/> <person role="bugowner" userid="RedDwarf"/> <group groupid="factory-maintainers" role="maintainer"/> <debuginfo> <enable/> </debuginfo> <build> <disable repository="Mandriva_2009.1"/> <disable repository="Mandriva_2010"/> <disable repository="Mandriva_2010.1"/> <disable repository="Debian_5.0"/> <disable repository="Debian_6.0"/> <disable repository="xUbuntu_9.10"/> <disable repository="xUbuntu_10.04"/> <disable repository="xUbuntu_10.10"/> <disable repository="xUbuntu_11.04"/> <disable repository="Fedora_15"/> <disable repository="Fedora_16"/> <disable repository="images"/> <disable repository="openSUSE_Tumbleweed"/> </build> <repository name="Debian_5.0"> <path project="Debian:5.0" repository="standard"/> <arch>i586</arch> <arch>x86_64</arch> </repository> <repository name="Debian_6.0"> <path project="Debian:6.0" repository="standard"/> <arch>i586</arch> <arch>x86_64</arch> </repository> <repository name="Fedora_15"> <path project="Fedora:15" repository="standard"/> <arch>i586</arch> <arch>x86_64</arch> </repository> <repository name="Fedora_16"> <path project="Fedora:16" repository="standard"/> <arch>i586</arch> <arch>x86_64</arch> </repository> <repository name="images"> <arch>x86_64</arch> <arch>i586</arch> </repository> <repository name="Mandriva_2009.1"> <path project="Mandriva:2009.1" repository="standard"/> <arch>i586</arch> <arch>x86_64</arch> </repository> <repository name="Mandriva_2010"> <path project="Mandriva:2010" repository="standard"/> <arch>x86_64</arch> <arch>i586</arch> </repository> <repository name="Mandriva_2010.1"> <path project="Mandriva:2010.1" repository="standard"/> <arch>x86_64</arch> <arch>i586</arch> </repository> <repository name="openSUSE_11.4"> <path project="openSUSE:11.4:Update" repository="standard"/> <path project="openSUSE:11.4:NonFree" repository="standard"/> <arch>x86_64</arch> <arch>i586</arch> </repository> <repository name="openSUSE_12.1"> <path project="openSUSE:12.1:Update" repository="standard"/> <path project="openSUSE:12.1:NonFree" repository="standard"/> <arch>x86_64</arch> <arch>i586</arch> </repository> <repository name="openSUSE_Factory"> <path project="openSUSE:Factory:NonFree" repository="standard"/> <arch>i586</arch> <arch>x86_64</arch> </repository> <repository name="openSUSE_Tumbleweed"> <path project="openSUSE:Tumbleweed" repository="standard"/> <arch>i586</arch> <arch>x86_64</arch> </repository> <repository name="SLE_10"> <path project="SUSE:SLE-10:SP4:SDK" repository="standard"/> <arch>i586</arch> <arch>x86_64</arch> </repository> <repository name="SLE_11"> <path project="SUSE:SLE-11:SP2" repository="standard"/> <arch>x86_64</arch> <arch>i586</arch> </repository> <repository name="xUbuntu_10.04"> <path project="Ubuntu:10.04" repository="standard"/> <arch>i586</arch> <arch>x86_64</arch> </repository> <repository name="xUbuntu_10.10"> <path project="Ubuntu:10.10" repository="standard"/> <arch>i586</arch> <arch>x86_64</arch> </repository> <repository name="xUbuntu_11.04"> <path project="Ubuntu:11.04" repository="standard"/> <arch>i586</arch> <arch>x86_64</arch> </repository> <repository name="xUbuntu_9.10"> <path project="Ubuntu:9.10" repository="standard"/> <arch>i586</arch> <arch>x86_64</arch> </repository> </project> -- 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] Build ignoring 'my' package
by Dominique Leuenberger a.k.a DimStar 13 Apr '12

13 Apr '12

Hi, I seem to have an odd issue in home:dimstar:gcc47. On a project level, use-for-build is disabled (to not trigger too many rebuilds) openCOLLADA has use-for-build enabled on package level blender BuildRequires openCOLLADA-devel, yes I always see it 'pulling in' the 'old' version, not my updated one... took me a while of course to see that. So now I changed the BuildRequires to be >= svn840 (svn838 is the one being pulled in). Obviously, now blender shows 'unresolvable', which is better, but not explainable (just yet). Can anybody see why openCOLLADA-devel svn868, which is built in home:dimstar:gcc47, is not being used here? Thanks a lot! (This won't fix blender for gcc 4.7 just yet, but at least it stops me from chasing bugs in underlying packages which I already fixed). Dominique -- 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] [PATCH] [backend] fix error msg when using external tool.
by Hector Oron 13 Apr '12

13 Apr '12

Fix typo on error message when using external publisher program. Signed-off-by: Hector Oron <hector.oron(a)collabora.co.uk> --- src/backend/bs_publish | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/src/backend/bs_publish b/src/backend/bs_publish index afa1bbb..f549261 100755 --- a/src/backend/bs_publish +++ b/src/backend/bs_publish @@ -1430,7 +1430,7 @@ sub publish { return; } if (system($BSConfig::publishprogram->{$prp}, $prp, $extrep)) { - die(" $BSConfig::publishprogram{$prp} failed: $?\n"); + die(" $BSConfig::publishprogram->{$prp} failed: $?\n"); } goto publishprog_done; } -- 1.7.9.1 -- 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] Problems when trying to commit changes - Message requested by adrianS
by Erik Schilling 12 Apr '12

12 Apr '12

Hello, as requested by adrianS on irc I am sending a message to the list for later debugging: commiting changes using osc fails after entering commit text: ~/osc/games/mana > osc ci rpm: -bp: unknown option Aborting: service call failed: /usr/lib/obs/service/source_validator --outdir /tmp/tmpEDsBEm *** Error: ~/osc/games/mana > Information: System: Fedora 16 /usr/lib/build > yum info obs-service-source_validator build Loaded plugins: langpacks, presto, refresh-packagekit Installed Packages Name : build Arch : noarch Version : 2012.03.06 Release : 88.1 Size : 573 k Repo : installed From repo : openSUSE_Tools Summary : A Script to Build SUSE Linux RPMs License : GPL-2.0+ Description : This package provides a script for building RPMs for SUSE Linux in a : chroot environment. Name : obs-service-source_validator Arch : noarch Version : 0.2 Release : 17.1 Size : 54 k Repo : installed From repo : /obs-service-source_validator-0.2-17.1.noarch ######<- downloaded this from buildservice page since after the downtime it took very long to apear in the repository. Summary : An OBS source service: defines all source-validator checks used by Factory License : GPL-2.0+ Description : This is a source service for openSUSE Build Service. : : This service runs all checks as required by openSUSE:Factory project. This can be used : to guarantee that all checks succeed also on the service side. This plugin can be : used via project wide defined services. Best regards Erik Schilling (Ablu) -- 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] [PATCH] [backend] (deb) Add Sources files to Release file.
by Hector Oron 12 Apr '12

12 Apr '12

On Debian style repositories include Source and Source.gz as part of Release file. Signed-off-by: Hector Oron <hector.oron(a)collabora.co.uk> --- src/backend/bs_publish | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/src/backend/bs_publish b/src/backend/bs_publish index e3ced5d..afa1bbb 100755 --- a/src/backend/bs_publish +++ b/src/backend/bs_publish @@ -568,7 +568,7 @@ EOL close(OUT) || die("close: $!\n"); open(OUT,">>$extrep/Release") || die("$extrep/Release: $!\n"); - foreach my $f ( "Release", "Packages", "Packages.gz" ) { + foreach my $f ( "Release", "Packages", "Packages.gz", "Sources", "Sources.gz" ) { open(FILE,"<$extrep/$f") || die; my @all = <FILE>; -- 1.7.9.1 -- 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] osc revisions while linking
by Praveen_Paladugu＠Dell.com 11 Apr '12

11 Apr '12

While using linking on OBS, I get a _link file similar to the following <link package="CentOS-Live-VMDK" rev="9310cbd84d63e722ad66abca52a985fa" cicount="copy" baserev="9310cbd84d63e722ad66abca52a985fa"> <patches> <apply name="project.diff" /> </patches> </link> I searched around on the opensuse-buildservice mailing list and found out the value assigned to "rev" is an md5sum. Could someone please clarify md5sum of what is captured in "rev" . Also I am only interested in using the standard revision numbers in the links (ex: 12, 34, 89 etc). There is a way to map the md5sum value to a particular revision of the source project? Is there way to tell OSC to use only the revision numbers instead of md5sum values while creating new links? Thank you Praveen K Paladugu Dell Linux Engineering -- 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] Managing updates in a private obs.
by Peter Morreale 11 Apr '12

11 Apr '12

Hello All, I hope this is the right mailing list, please advise is not.... Thx. I'm in the process of creating a private OBS instance to support creation of a distro for a storage platform. The distro will be based on either CentOS or openSUSE and contain proprietary application packages. The one thing I can't seem to grok from the wiki is how updates are managed for the base OS using obs? I think our goal would be to have the ability to create our distro that included all relevant updates to base OS packages at the time of image creation. Regardless of whether we use a public repo instance for the base OS, or a private one, the repo is static wrt to package updates for the base distro. So I'm a little lost on how to manage package updates. I searched through the archives for the last six months and unless I missed a thread, didn't see anything resembling this... How do other private obs instances handle this? Any advice would be welcome. Best Regards, -PWM -- 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] pullrpms utility
by Archie Cobbs 11 Apr '12

11 Apr '12

I wanted to share an idea and get people's feedback... On several occasions I've wanted to build a private repository containing all the RPMs - both standard and proprietary - needed to build a complete system. The idea is that, for some target machine, we start with a "master" RPM that (directly and indirectly) requires every other RPM that the target machine needs. There may be a bunch of these target machines and associated RPMs. The goal is then to build a single RPM repository containing all of the (directly and indirectly) required RPMs for all of these target machines. It should also be possible to add to this repository over time. This single repository is then used to build the target machines. E.g., it could be put on a DVD, etc., so no network need be available. To do this I wrote a simple utility that is a wrapper around zypper and createrepo called "pullrpms" available here: http://code.google.com/p/pullrpms/ I'm curious if other people have encountered this same problem, and how they have addressed it, etc. FWIW. -Archie -- Archie L. Cobbs -- 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] Appliance's repository vhost doesn't work out of the box
by Gregor Dschung 11 Apr '12

11 Apr '12

Hi. The file dist/obs-apache2.conf from obs-server-2.2.131.tar.bz2, package obs-server, project openSUSE:Tools:Unstable is configured to use /srv/obs/repos for the repository vhost. In the appliance, this leads to the error "[Tue Apr 10 12:29:43 2012] [error] [client 10.136.17.142] Symbolic link not allowed or link target not accessible: /srv/obs" as /srv/obs is a symlink to /obs. I guess, in the appliance this config file should be patched to use /obs/repos, so the appliance works out of the box? Regards, Gregor -- 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] Running testsuite only on local build?
by Andreas Jaeger 11 Apr '12

11 Apr '12

Is it possible to check in the spec file whether I'm building with osc locally or in obs? Or whether it's in Factory or in my home project? The following did not work for me: # Enable testsuite runs for local builds %if 0%{?opensuse_bs} %define run_testsuite 0 %else %define run_testsuite 1 %endif It disabled the testsuite with osc as well. I want to run the testsuite for glibc not as part of openSUSE:Factory but have it run e.g. locally. How can I achieve this best? Andreas -- Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

4 8