June 2007 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] Matching release numbers
by James Oakley 29 Jun '07

29 Jun '07

I've been looking at the kernel projects and I've noticed that they contain a kernel-source package which is linked to by the binary and syms packages. In order for the syms package to work, all of the packages must have the same release number. I've been trying to do the same thing and failing miserably. When I try to manually set them all to the same release, in both the spec files and the history files, a couple of them will be set to release+1 and others will be set to release+2. How are you guys doing it? -- James Oakley jfunk(a)funktronics.ca --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 3

[opensuse-buildservice] Build cluster has gone crazy
by James Oakley 29 Jun '07

29 Jun '07

According to http://build.opensuse.org/monitor there are currently 629 running jobs, many of which have been running for hours. It is also reporting 85 idle hosts. Since I doubt there are 714 workers in the cluster, I guess something has gone wrong. -- James Oakley jfunk(a)funktronics.ca --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 0

[opensuse-buildservice] Fedora builds only SRC RPM
by Thomas Schmidt 28 Jun '07

28 Jun '07

The Fedora target of the project swamp only creates a SRC RPM: http://build.opensuse.org/package/show?package=swamp_svn&project=swamp Does anyone know what I am doing wrong? Thanks! -- Thomas Schmidt (tschmidt [at] suse.de) SUSE Linux Products GmbH :: Research & Development :: Internal Tools "memory management can be a bitch" (linux/kernel/fork.c:11) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 1

[opensuse-buildservice] qmake and spec files
by Dirk Stoecker 27 Jun '07

27 Jun '07

Hallo, I want to build the libqwt package, but I don't get the install part to work within a spec-file. The makefile is created by a qmake call and does not accept anything like DESTDIR. How do I tell the qmake made stuff to install in the RPM paths? Any ideas? Ciao -- http://www.dstoecker.eu/ (PGP key available) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 0

[opensuse-buildservice] osc on SLE_10
by Carsten Schoene 27 Jun '07

27 Jun '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, i just installed osc & build on a fresh SLES 10 SP1 from http://software.opensuse.org/download/openSUSE:/Tools/SLE_10/ When i run osc i get the following error, do i miss something ? sles10basic:/home # osc Traceback (most recent call last): File "/usr/bin/osc", line 7, in ? from osc import commandline File "/usr/lib64/python2.4/site-packages/osc/commandline.py", line 9, in ? from core import * File "/usr/lib64/python2.4/site-packages/osc/core.py", line 21, in ? import cElementTree as ET ImportError: No module named cElementTree sles10basic:/home # rpm -q osc build osc-0.96-27.1 build-2007.06.13-6.2 bye Carsten -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFGgJTH6NfbfHY52TsRAnGlAJ9lM0ARE3hDL5AHfMooKarMyDLucgCeK9Ch BWQuJ+RdENdHJeco3hUx/fA= =x81k -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 3

[opensuse-buildservice] Public access to .spec files
by John Pye 25 Jun '07

25 Jun '07

Hi all I have been working with the Red Hat people to try to get a package released, and I have been checking my package using the Build Service. I came across an improvement that would help greatly with this type of work. Firstly, there needs to be some way of providing public access to the spec file, as well as the .src.rpm. It is standard when submitting Fedora package to provide a web link to .spec files to allow easy review. The next thing is that the %{?dist} tag is stripped from the 'Release' header. This is bad, because the %{?dist} thing is preferred practise for Fedora packages, and reviewers expect it be there. This means that .src.rpm packages from the openSUSE build service do not meet their requirements. Also, the release tag given in the %changelog part of the spec file should be updated if the Release header is updated. Otherwise the %changelog doesn't correspond to the package version. Finally, it would be good if there were a quick and easy way to review the contents of each package built. Currently the package links go to an encrpyted HTTPS download page. It would be better if they went to a page a bit like those in the Debian and Ubuntu package repositories, showing the dependencies and file contents, and download links, etc. I've been really impressed with the Build Service so far. Keep up the great work. Cheers JP --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 1

[opensuse-buildservice] Dependencies: what if some distro have it, some distros don't?
by John Pye 25 Jun '07

25 Jun '07

Hi all I have a package that needs a fairly recent version of SCons in order to build. This version is available in most of the newer distros, but seems to be missing in some others, specifically openSUSE 10.2 and Mandriva 2006. There is a SCons package somewhere else in the Build Service and I can link to that if I want. However I am not sure how this work when for example FC6 already has the required version in the 'extras' repostory, versus openSUSE 10.2, which doesn't have it. Is there a way I can specify for the Build Service to use my local package *only when* a satisfactory version is not available in the base repository? Or is this already the default behaviour? Cheers JP --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 3

[opensuse-buildservice] PreReq handling is broken on < 10.3
by Cristian Rodriguez R. 25 Jun '07

25 Jun '07

Hi: this is the situation: package X needs Y for build and Y PreReq Z , Y gets installed but Z is not installed before Y and installation of Y aborts because it really requires Z to be installed first. Works flawlessly on factory only, and package built properly without any changes about a week ago, all the other distros break. cya Cristian.

2 3

[opensuse-buildservice] "Building" source rpm only ?
by David Cournapeau 25 Jun '07

25 Jun '07

Hi, One of the library I am trying to package is ATLAS, which is a self tuned library for blas/lapack (numeric code). Because it is tuned to the machine where it is built, packaging it is particularly tricky (and won't build on xen for some reasons). As a first step, I would like to provide source rpms only. Is this possible ? cheers, David --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 2

[opensuse-buildservice] Newbie: building an RPM using SCons in Buildservice
by John Pye 23 Jun '07

23 Jun '07

Hi all I have just uploaded the necessary files for my project to the Build Service. My package is for the ASCEND modelling environment. It has been fairly well tested and builds correctly on Fedora Core 6. I uploaded the tarball and the spec file (which is actually also included in the tarball, FWIW). The build log gets down as far as starting the build, but it says 'scons: command not found'. It seems that it's not picking up the build dependency on the 'scons' package. What do I need to do to make sure that all the necessary dependencies are there at the start of the build? I had assumed that they would just be installed as a result of the stated package BuildDepends dependencies? Looking forward to getting this all working. Seems like a really good idea. Cheers JP --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 1