February 2008 - openSUSE Build Service

[opensuse-buildservice] Duplicities in BuildService
by Pavol Rusnak 08 Feb '08

08 Feb '08

Hi all! I read today that TrueCrypt 5.0 is out. I immediately checked BuildService and found 4 different packages: project | version -----------------+------------------- home:vitsoft | 4.3a security:privacy | 4.3a + patches home:lluke123 | 5.0 home:bbendix | broken (no source) I'm sure that this situation happens for other packages as well. Would it be possible to show some kind of warning when creating new package, like "package 'foo' already exists in project 'bar'" (with hyperlinks to package and project). But this would be just warning, so I still can my own build if I really want. I think this will bring several benefits (if users started to cooperate more): * reduced waste of human resources * reduced hardware requirements (disk space, build power) * increased quality of packages (more updates, current versions) -- Best Regards / S pozdravom, Pavol RUSNAK SUSE LINUX, s.r.o Package Maintainer Lihovarska 1060/12 PGP 0xA6917144 19000 Praha 9, CR prusnak[at]suse.cz http://www.suse.cz --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 3

[opensuse-buildservice] lots of machines idle, but
by Detlef Steuer 07 Feb '08

07 Feb '08

my triggered builds take ages to get scheduled. OBS status shows 60 or so hosts idle and 0 buils waiting. Hey, _I am waiting_ ! Something wrong with scheduling? :-) detlef -- Wisely, and slow. They stumble that run fast. - Shakespeare --------------------------------------------------------------------- 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] BuildRequires calculation issue
by Wolfgang Rosenauer 07 Feb '08

07 Feb '08

Hi, I just ran into an issue which would be easy to fix from the spec file but I wonder why the buildservice doesn't handle it correctly: My package BuildRequires: java-devel and I'm using SUSE:SL-10.1:NonFree/standard. That means that it installs java-1_5_0-sun-1.5.0_06-17 on x86_64 (with i586 it works correctly since it pulls in 1.4.2) but I get the following error in the buildservice: nstalling java-1_5_0-sun-1.5.0_06-17 /var/tmp/rpm-tmp.515: line 5: update-alternatives: command not found /var/tmp/rpm-tmp.515: line 27: update-alternatives: command not found /var/tmp/rpm-tmp.515: line 29: update-alternatives: command not found /var/tmp/rpm-tmp.515: line 37: update-alternatives: command not found error: %post(java-1_5_0-sun-1.5.0_06-17.x86_64) scriptlet failed, exit status 127 The package update-alternatives isn't installed before the java package although the Java package has PreReq: /usr/sbin/update-alternatives So why isn't it handled correctly? Thanks, Wolfgang --------------------------------------------------------------------- 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] problems with cpio in BS
by Petr Mladek 07 Feb '08

07 Feb '08

Hello, I have been unable to finish any build of OpenOffice_org in the OpenOffice.org:UNSTABLE project. There are some strange problems with cpio. One type of the crash is in the %install phase (SLED_10, i586): --- cut --- File listed twice: /usr/share/ooo-2.0/sdk/classes/com/sun/star/lib/loader/WinRegKeyException.class File listed twice: /usr/share/ooo-2.0/sdk/classes/win/unowinreg.dll create archive failed on file /var/tmp/OpenOffice_org-2.3.99.2-build/usr/lib/ooo-2.0/devel/solver/680/unxlngi6.pro/pck/tplwizfax_sl.zip: cpio: write failed - Bad file descriptor md: stopping all md devices. xenbus_dev_shutdown: device/console/0: Initialising != Connected, skipping System halted. --- cut --- Another crash happens after the build finishes (openSUSE_10.2, i586): --- cut --- Wrote: /usr/src/packages/RPMS/i586/OpenOffice_org-officebean-2.3.99.2-3.1.i586.rpm Wrote: /usr/src/packages/RPMS/i586/OpenOffice_org-devel-2.3.99.2-3.1.i586.rpm Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.19963 + umask 022 + cd /usr/src/packages/BUILD + cd ooo-build-2.3.99.2 + rm -rf /var/tmp/OpenOffice_org-2.3.99.2-build + exit 0 mount: can't find / in /etc/fstab or /etc/mtab md: stopping all md devices. xenbus_dev_shutdown: device/console/0: Initialising != Connected, skipping System halted. cpio extract failed --- cut --- There are another crashes caused by not enough disk space. I haven't reproduced the problem locally yet (using osc build). Do you have any idea what could cause it? Is it a problem specific for the BS build machines? -- Best Regards, Petr Mladek software developer --------------------------------------------------------------------- SUSE LINUX, s. r. o. e-mail: pmladek(a)suse.cz Lihovarská 1060/12 tel: +420 284 028 952 190 00 Prague 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz/ --------------------------------------------------------------------- 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] build flags in web interface
by John Pye 07 Feb '08

07 Feb '08

Hi all Sometime not far back a new thing was added to the web UI for OBS that prevented 'complex' flag combinations to be used from the web interface. I get an error like this: "ERROR Your flag configuration seems to be too complex to be saved through this interface. Please use OSC." I would like to comment that the direct result of preventing web UI users from disabling certain builds is that they will tend not to bother, and your compile farm capacity will be needless wasted. If it's possible, could I urge that the full flag functionality be restored, and even better, could some clever javascript/AJAX be used to make these flag settings more responsive -- they are quite slow to use at present (and I imagine this might have been part of the reason for the above 'error' message). I think the web UI is overall an excellent tool -- please, do 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

4 5

Re: [opensuse-buildservice] Removal of Java:Sun-Java-1.5 Project
by Petr Mladek 06 Feb '08

06 Feb '08

On Wednesday 06 February 2008, Adrian Schröter wrote: > On Tuesday 05 February 2008 19:40:44 wrote Petr Mladek: > AFAIK our java people says that the default should be > "BuildRequires: java-devel" > > and this should be mapped according to the java enviroment, what the distro > is using. > > So you should get gcc-java when you build against openSUSE:Factory, and sun > java when you build against openSUSE:Factory:NonFree Great, it seems to work. > I will have a more detailed look at your reports below later this week. Thanks a lot for help. -- Best Regards, Petr Mladek software developer --------------------------------------------------------------------- SUSE LINUX, s. r. o. e-mail: pmladek(a)suse.cz Lihovarská 1060/12 tel: +420 284 028 952 190 00 Prague 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz/ --------------------------------------------------------------------- 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] java support
by John Calcote 05 Feb '08

05 Feb '08

Hi list, I wonder if I can get some straight advice on this issue once and for all. :) I have a package (openxdas) in my home project (jcalcote) that generates a daemon, written in C, and two client libraries - one written in C and the other written in pure Java. I've created my autotools configure.ac and Makefile.am files to build all three components, but I'm beginning to think that I'm on the bleeding edge here, functionally speaking. The java client library builds just fine on my personal SLED 10 system with IBM Java 1.5 installed. I can even generate source and binaries rpm files that install just fine. I'm using the following BuildRequires line in my spec file - both on my system, and in my project on the build service: BuildRequires: gcc libgcc java2-devel-packages unixODBC-devel expat But this only works on a few select platforms. Here's my status page Debian_Etch i586 - failed because expat is still 1.0 x86_64 - failed because expat is still 1.0 Fedora_Extras_6 i586 - nothing provides java-1_4_2-sun-devel x86_64 - nothing provides java-1_4_2-sun-devel openSUSE_10.2 i586 - nothing provides java-1_5_0-sun-devel x86_64 - nothing provides java-1_5_0-sun-devel openSUSE_10.3 i586 - success! x86_64 - success! openSUSE_Factory i586 - java compile problems - bad extension of class Exception. x86_64 - java compile problems - bad extension of class Exception. SLES_9 i586 - failed - seems to be an expat library version issue - undefined reference to XML_StopParser. x86_64 - failed - seems to be an expat library version issue - undefined reference to XML_StopParser. SLE_10 i586 - success! x86_64 - success! xUbuntu_7.10 i586 - failed because expat is still 1.0 x86_64 - failed because expat is still 1.0 Fedora_8 i586 - nothing provides java-1_4_2-sun-devel x86_64 - nothing provides java-1_4_2-sun-devel Now, I can fix the java compiler issues where I've done something dumb in my source code - that takes care of the openSUSE_Factory issues I think. But what can I do about the platforms that want a particular version of java - expanded I presume from the java2-devel-packages macro? 1. Am I just going about this the wrong way? Should I stop trying to compile my java source code in my rpm package, just compile it separately and provide a java client jar file separately? It should be portable, since it's java. But is this the right way to do it - should this stuff be working for me? 2. How I can specify that I want expat 2.0, and not just any old expat library. Thanks in advance, John --------------------------------------------------------------------- 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] Removal of Java:Sun-Java-1.5 Project
by Adrian Schroeter 05 Feb '08

05 Feb '08

Hi, I will remove the obsolete project Java:Sun-Java-1.5 in a second. There quite some projects which do still build against. These repositories will get disabled and point to the "deleted" project. No built rpms will disappear, but also no new packages get build until you fix your project setup. You can do this easily by calling osc meta prj -e <your_project> and replace <path project="deleted...." repository="...."/> with a propper :NonFree project which provides the matching Java engines, for example <path project="openSUSE:10.3:NonFree" repository="standard"/> thanks adrian -- Adrian Schroeter SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany email: adrian(a)suse.de --------------------------------------------------------------------- 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] Which directory structure under /srv/obs/build for Ubuntu/Debian builds?
by Christopher Lang 05 Feb '08

05 Feb '08

Hi, I am experimenting with a local obs and so far I like it quite a lot! I have a question with regard to the directory structure for base packages: The directory tree structure for the base repository packages according to: http://en.opensuse.org/Build_Service/Build_Service_Installation_Tutorial/op… looks like this: chris@builder:/srv/obs> tree build/ build/ |-- SUSE:SL-10.1 | `-- standard | `-- i586 | | `-- :full | | `-- *.i586.rpm | `-- noarch | | `-- :full | | `-- *.noarch.rpm | `-- x86_64 | `-- :full | `-- *.x86_64.rpm |-- Ubuntu:7.04 | `-- standard ???? My question is: What would be the proper directory structure for an Ubuntu or Debian base repository? Just copy all .deb files from the Debian repository path pool/main into the standard/ dir? A quick hint is much appreciated. many thanks! Chris http://www.acurana.de/ --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 4

[opensuse-buildservice] Bugfix testing
by Marcus Rueckert 05 Feb '08

05 Feb '08

hi, To verify that we really fixed a bug, we need to reboot the buildservice webserver. This includes the following hosts: http://api.opensuse.org/ http://build.opensuse.org/ http://software.opensuse.org/ The downtime should be less than 5 minutes. Thanks for your understanding. with kind regards darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 2

[opensuse-buildservice] 'have choice' for F8 for text-www-browser
by John Pye 05 Feb '08

05 Feb '08

Hi all I believe that there was a request that issues such as these be notified to the mailing list: "have choice for text-www-browser needed by docbook-utils: lynx elinks w3m" This error arose in my building log here, for Fedora 8: https://build.opensuse.org/package/show?package=fityk&project=home%3Ajdpipe Cheers JP --------------------------------------------------------------------- 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] Build-service repositories for stable openSUSE versions (10.3)
by Smartysmart34 04 Feb '08

04 Feb '08

Hi all, I had a kind of weird discussion these days about the openSUSE build-Service repositories and I would like to get your feedback. If this is the wrong location please redirect me to wherever this topic fits best. My impression was: As the default OpenSUSE 10.3 comes with some preconfigured repositories and they are all named "openSUSE BuildService - xyz" I assumed that these repositories are run by the openSUSE Project team. So I expected them to have some sort of quality assurance even though I knew the content was not part of the official final release. I valued them higher then any other "I put together some stuff and if you want add my repo" privately run Repository - at least regarding content, quality and trustworthiness. But now someone told me, that these repositories are no better then any other repository one can find out there. Is this right? Or to put it the other way round: What is the difference between these standard-shipped repositories and any other repository I could add? thank you and kind regards, Martin --------------------------------------------------------------------- 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] Re: [Lf_driver_backport] chroot tools (build and mock)
by Susanne Oberhauser 04 Feb '08

04 Feb '08

Hi, Martin from Fujitsu Siemens computers is testing the build server and has a proxy setup to access the internet. Corporate policy. Don't ask. Now the lack of https proxy support in urllib2 is biting him hard: Martin Wilck <martin.wilck(a)fujitsu-siemens.com> writes: > Susanne Oberhauser wrote: > > > osc platforms | grep -Ei "/standard" > targetlist > > from "conf.py": > > # HTTPS proxy is not supported by urllib2. It only leads to an error > # or, at best, a warning. > # https://bugzilla.novell.com/show_bug.cgi?id=214983 > # https://bugzilla.novell.com/show_bug.cgi?id=298378 > if 'https_proxy' in os.environ: > del os.environ['https_proxy'] > > This makes osc pretty much unusable from here :-( > Do we have to fix python's urllib implementation first? How should we proceede? S. -- Susanne Oberhauser +49-911-74053-574 SUSE -- a Novell Business OPS Engineering Maxfeldstraße 5 Processes and Infrastructure Nürnberg SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 1

[opensuse-buildservice] Instruction on http://en.opensuse.org/Build_Service/Deb_builds are not useful for creating .deb packages
by G. Massera 04 Feb '08

04 Feb '08

Hello, I tryied to use the instruction at http://en.opensuse.org/Build_Service/Deb_builds for creating a Debian repository (or in general a .deb package)... without obtaning nothing. After looking for solution into the debian documentation, and with a lot of trials... finally I created .deb packages. As I write in discussion part of the page... the mandatory files (the minimal set of files necessary to compile a .deb package) is different from that specified in the page... and I proposed to re-write the page telling my experience. Because no-one replyied on the discussion or by e-mail... I repeat my proposal here. In fact, creating the .deb packages are very simple... with the correct instructions... and I want to contribute with my experience. Cheers, Gianluca --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

6 7

[opensuse-buildservice] osc build causes "Too many arguments" in /usr/bin/build
by Matthias Bach 03 Feb '08

03 Feb '08

Hi! I was trying to do a local build using 'osc build openSUSE_10.3 x86_64 sane-backends-snapshot.spec'. However the build will fail on invocation of the build-script: sudo /usr/bin/build --root=/var/tmp/build-root --rpmlist=/tmp/rpmlist.bCcRF4 --dist=/tmp/buildconfig.24-lvT sane-backends-snapshot.spec --norootforbuild --changelog /usr/bin/build: line 387: test: too many arguments Usage: /usr/bin/build <src-dirctory> Manuall invoking /usr/bin/build will work. sudo build --rpms /media/SU1030.001/suse/ Is there a newer version of /usr/bin/build that I will have to use. I am using the one from opensuse 10.3 with the osc from openSUSE:/Tools, this means I got the newest version I could find of those two tools Any advice is appreciated, Matthias -- Matthias Bach www.marix.org "Was nicht mit einer gewissen Unsicherheit behaftet ist, kann unmöglich die Wahrheit sein." - Richard P. Feynman

2 3

[opensuse-buildservice] Is there an enviroment variable that point to Source root tree ??
by G. Massera 02 Feb '08

02 Feb '08

Hello, on opensuse the source tree is /usr/src/packages/SOURCE on mandriva /usr/src/rpm/SOURCE on Fedora /usr/src/redhat/SOURCE ... :-S is there an enviroment variable like $BUILD_ROOT ... (i.e. $SOURCE_ROOT) that point to source tree ?? Thanks, Gianluca --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

5 6

Re: [opensuse-buildservice] Re: Error at line 20 of cmake.spec
by Michal Marek 01 Feb '08

01 Feb '08

[adding opensuse-buildservice to cc again] G. Massera wrote: > Michal Marek ha scritto: >> Do you have cmake package that builds on RHEL (and still builds on >> openSUSE)? It would be great to build such tools in one place >> (devel:tools:scm) for as many distributions as possible, to avoid having >> to rebuild in other projects. >> > From here you find the cmake that I link > https://build.opensuse.org/package/show?package=cmake&project=openSUSE%3A10… > > And here: > https://build.opensuse.org/package/show?package=cmake&project=home%3AEmmeG > you'll find the two cmake-CentOS_5.spec and cmake-RHEL_5.spec that allow > to build also on CentOS and RHEL. Could you merge the SUSE and RHEL(CentOS) spec into one (cmake.spec)? They seem to be very similar, so it should be possible to push the changes to openSUSE:Factory, on which devel:tools:building/cmake (*) is based. BTW, there are 32 projects which rebuild cmake atm, most of them would be fine with an _aggregate. Michal (*) Err, it's devel:tools:building, not devel:tools:scm, sorry for the confusion. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 5

[opensuse-buildservice] How to detect distribution with %if block in .spec file ??
by G. Massera 01 Feb '08

01 Feb '08

Hello, I want to put into the .spec file some block distribution-dependent... so, it would very nice if is it possible to use the %if syntax to detect the distribution and run the corrisponding block only on some distributions. Of course, I can create name-Distro.spec file for each Distro... but sometimes is more useful the %if syntax because there are somethings that changes between Suse and Fedora ... but remains the same on all Fedora (6,7,8)... so, instead of creating three .spec identically for each version of Fedora, it would more easy to add just one block to detect if is a Suse or Fedora distro. Thanks, Gianluca --------------------------------------------------------------------- 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] Where can I find CMake 2.4.7 for all distro supported by buildservice ??
by G. Massera 01 Feb '08

01 Feb '08

I have some packages that needs cmake 2.4.7 ... but I cannot find it for all distribution (in particular, Fedora, Mandriva and CentOS) in the repositories for aggregate it. Firstly, I decided to create a cmake package in my repositories ... but there are so many users that re-create cmake packages... and I'm wondering if there is an easy centralized way for aggreate it in such way that is automatically available on all distro supported. Thanks, Gianluca --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

4 5