April 2008 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] Mandiva 2008 is broken
by Amilcar do Carmo Lucas 01 Apr '08

01 Apr '08

Hi all, https://build.opensuse.org/package/show?package=KDevelop3&project=home%3Aam… On i586 I get: expansion error have choice for kernel >= 2.4.18 needed by alsa-plugins: kernel-desktop586-2.6.22.9-1mdv kernel-laptop-2.6.22.9-1mdv kernel-server-2.6.22.9-1mdv kernel-desktop-2.6.22.9-1mdv On x86_64 I get: expansion error nothing provides libqt3 >= 3.3.2, nothing provides libqt3-devel >= 3.3.2, nothing provides libqt3-static-devel >= 3.3.2 Both Mandiva 2006 and 2007 work fine. All RHEL, CentOS, and SuSE builds also work fine. Regards, -- Amilcar Lucas Webmaster The KDevelop project --------------------------------------------------------------------- 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] xUbuntu_7.10 has been messed up
by Amilcar do Carmo Lucas 01 Apr '08

01 Apr '08

Hi all, xUbuntu_7.10 was working fine a month ago. https://build.opensuse.org/package/show?package=KDevelop3&project=home%3Aam… Now I updated my sources and trigred a rebuild, all targets work fine, but xUbuntu_7.10 gives: expansion error nothing provides libjasper-dev >= 1.900.1 needed by kdelibs4-dev The problem is that I do not use/need libjasper-dev nor kdelibs4-dev. Please fix it. -- Amilcar Lucas Webmaster The KDevelop project --------------------------------------------------------------------- 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] pike project
by Robert Hinn 01 Apr '08

01 Apr '08

Hello, I'm one of the developers of the open-sTeam collaboration server software (http://www.open-steam.org), which is written in the pike programming language (http://pike.ida.liu.se). In the long run, I would like to use the build service to produce and publish RPM packages of our software, but since there are currently no pike rpm packages about, I tried to build my own. I succeeded (with help by the people on the build service IRC - thanks again!) in creating a project in my build service home and have successfully created packages for openSUSE 10.2, 10.3, SLES 10, Fedora Core 8 and RHEL 5 with it (only for i586, the 64-bit version doesn't seem to compile, though at the moment I think I don't need the 64-bit packages anyway ;-) ). It would be great if you could open a project outside my home for pike, so that it becomes a "regular" package. I've read in the archives that I should probably contact the maintainers of the corresponding group (Development/Languages/Other should be fine for pike, I guess), but I haven't found any information on the website as to how to contact group maintainers ;-) Could you tell me whom to contact about requesting a regular build service project for pike? By the way, the build service is really a great tool. Up to now, I've build my own build environment scripts to create packages for some distributions, but the build service makes this so much easier and less troublesome to maintain! Best regards, Robert --------------------------------------------------------------------- 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] openSUSE:Tools:Unstable OBS svn trunc -r 3598 some testresults
by Martin Mohring 01 Apr '08

01 Apr '08

Hi Michael, I have the impression that there is a concrete case where the endless rebuilds happen. E.g. we have projects openSUSE:Tools and openSUSE:Tools:Unstable. openSUSE:Tools:Unstable uses for its build targets the underlying openSUSE:Tools build targets. Lets take the build openSUSE:Tools:Unstable/rubygem-activesupport-2_0/Fedora_7/i586, which currently fails both in openSUSE:Tools and in openSUSE:Tools:Unstable. It seems that restarting the scheduler can now trigger a build of openSUSE:Tools:Unstable/rubygem-activesupport-2_0/Fedora_7/i586 into an endless loop for some reason. Both pkgs fail to build, but the scheduler decides to rebuild the pkg, which ends in a loop. Martin Martin Mohring wrote: > Martin Mohring wrote: >> Hi, >> >> Michael Schroeder wrote: >>> On Tue, Apr 01, 2008 at 03:00:23PM +0200, Martin Mohring wrote: >>> >>>> I checked that this is not the case. When I installed the new code, >>>> it triggered about 400 rebuild. They are finished after one day, >>>> only 3 remaining in a loop after 1 day of testing. Is there a log I >>>> can look for these things a search for your hint? >>>> >>> >>> The scheduler output for those packages would be helpful. >>> >> Attached is the part which loops. Btw. openSUSE:Tools:Unstable is >> very similiar to that on build.o.o, especially the ruby pkgs are an >> exact copy of yours. >> To be 100% sure, I stop the complete OBS Server and Workers. Removed >> build-roots of Workers. And then restarted again. Lets see what happens. > > The restart triggered now 2 completely other pkgs. One of them was in > failed state before. I give you a complete dump of that, from the > start of OBS. > > Now you know everything of the projects in our OBS :-) Btw, ST Linux > 2.2 and 2.3 are our crossbuild distros (they do not use the > cross-build feature with another buildtarget we are working on, they > do not modify the scheduler of yours - dont mind , we develop this in > another OBS instance here). > > Bye, Martin > --------------------------------------------------------------------- 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] Building RPMs for SLED 10
by Han Wen Kam 01 Apr '08

01 Apr '08

Hi all, Thanks to opensuse buildservice hosting kmp drivers (appleonkel) for ASUS Eee PC, I was able to install opensuse 10.3 on it. However, I now have a need to install SLED 10 SP1 on the Eee PC. I need drivers for wlan(atl), audio, acpi and webcam. Since these drivers are available for opensuse 10.3 on the build service, how/what can I do to get these drivers built against SLED 10? Also, as an aside, I can't seem to get xorg.conf to have the right settings on SLED 10 (the same settings worked on opensuse 10.3). Thanks. Han

3 7

Re: [opensuse-buildservice] openSUSE:Tools:Unstable OBS svn trunc -r 3598 some testresults
by Martin Mohring 01 Apr '08

01 Apr '08

Hi, Michael Schroeder wrote: > On Tue, Apr 01, 2008 at 03:00:23PM +0200, Martin Mohring wrote: > >> I checked that this is not the case. When I installed the new code, it >> triggered about 400 rebuild. They are finished after one day, only 3 >> remaining in a loop after 1 day of testing. Is there a log I can look >> for these things a search for your hint? >> > > The scheduler output for those packages would be helpful. > Attached is the part which loops. Btw. openSUSE:Tools:Unstable is very similiar to that on build.o.o, especially the ruby pkgs are an exact copy of yours. To be 100% sure, I stop the complete OBS Server and Workers. Removed build-roots of Workers. And then restarted again. Lets see what happens. Martin

1 0

[opensuse-buildservice] Interesting summary pages
by Vincent Untz 01 Apr '08

01 Apr '08

Hi, Since I've started helping packaging GNOME, I was wondering if there were any easy page where I could know the current status of things. I don't think we have this. I know that Debian has some interesting examples: + http://dehs.alioth.debian.org/maintainer.php?name=gnome-panel Shows some information about the upstream status + http://packages.qa.debian.org/g/gnome-panel.html Shows some information about a specific package, including a TODO item about a new upstream release and links to bugs I know I've used this website quite a few times to know what was happening in Debian wrt some package. + http://qa.debian.org/developer.php?login=pkg-gnome-maintainers@lists.alioth… Big table with lots of information about packages maintained by some maintainer. (too much information, imho, though) I'd really love to get something similar (but improved, of course ;-)). I'd be especially interested in a page listing all the packages I'm interested in, with a small list of things for each package: + new upstream version to package + number of rpmlint errors to fix (with a link to display them) + number of relevant bugs in our bugzilla (hard right now, since we don't have a component for each package) + builds/doesn't build on some architecture/distro (we already have this, good!) Vincent -- Les gens heureux ne sont pas pressés. --------------------------------------------------------------------- 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] Build Service Status report
by Adrian Schröter 01 Apr '08

01 Apr '08

present: jcborn, abauer, mls, tpatzig, freitag, rlihm, adrian, poeml, froh Topics: * General work reports * Future release planing General work reports ==================== jcborn: * debugged usb stick image generation for Factory with KIWI * continued work on meta data generation for installation medias abauer: * submit request should be implemented in the API today. * missing: validation of request xml mls: * backend can reuse remote schedulers, some calls need to be routed via the api to get real use out of this. This feature will allow easy setup of own build service instances by reusing the base projects of opensuse.org build host. * binary repository cache implemented, but it blocks the source server too long atm. * added keeplink parameter to avoid removal of source linked packages tpatzig: * worked on hermes web frontend (codename starship) freitag: * worked a bit on hermes, esp on notification message abstraction. * Hermes is not yet integrated in the build service, but get tested with SWAMP instance to detect bottle necks and performance. rlihm: * worked on opensuse forum theme. poeml: * new osc release is building atm. - further support of submit request handling - link handling is new, source linked packages can be build now :) - commit handling of source links not yet implemented, need info about the API call, WIP adrian: * Presented Build Service at Novell Brainshare. Main topics of interessted people are: - Simple add-on packages distribution - Cross compiling support Future Release Planing ====================== We will release the next release as version 0.9, because we want have full support for openSUSE:Factory contributions with 1.0. Version 0.9 will be released next week depending on finishing the last features, packaging and testing. Features of 0.9: - easy patch generation of existing packages (WIP in API) - submit request mechanism in API, backend and osc (done) - submit request listing in API, backend and osc (done) - submission handling in case of accepted request (almost there, WIP) - Inter build service connectivity (done in backend, TBD in API) - Support of multi architecture build handling (not yet implemented) - Automated Image Creation (WIP, 80% done) - Signing key handling per projects (done) - qemu build support in build script (done) - local build of source linked packages (done) Features of 1.0 (Soft target date is 1.5.2008): - "Upstream Project" definition handling - osc support for "Upstream Project" handling - Special openSUSE:Factory checkin handling tools for autobuild team. - Full Factory tree generation support AI: freitag/poeml write "best practice" for editing packages in foreign projects -- Adrian Schroeter SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) email: adrian(a)suse.de ------------------------------------------------------- -- Adrian Schroeter SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) 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

1 0

Re: [opensuse-buildservice] rpmlint feedback
by Michal Marek 01 Apr '08

01 Apr '08

Dirk Mueller wrote: > Proper rpmlint integration in buildservice is already tracked via bnc#297050, > however it has been completely ignored so far and I honestly don't know who > to assign it to. My plan is to add rpmlint support to the build script and to the buildservice somehow and then dump home:michal-m:rpmlint. > Michal, if you want to improve experience, I suggest to install a config file > with at least one "setBadness()" call in /etc/rpmlint/config. I suggest you > add that to rpmlint-bs. OK, I will fix that. Michal --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 0

Re: [opensuse-buildservice] rpmlint feedback
by Wolfgang Rosenauer 01 Apr '08

01 Apr '08

Dirk Mueller wrote: > On Tuesday 01 April 2008, Michal Marek wrote: > > >>> "This package contains a library and provides no %post scriptlet >>> containing a call to ldconfig." >>> "This package contains a library and provides no %postun scriptlet >>> containing a call to ldconfig." >>> The package contains: >>> %post -p /sbin/ldconfig > > and the main package is the library package it complains about? I cannot > reproduce that. I assume the check was valid and that you forgot about > passing -n libfoo42 to %post. Michal mentioned that the error came from the debuginfo package. What is true. I haven't noticed that. >>> openSUSE's very own package sources have no Packager tag as well. It's >>> added from the buildsystem to the resulting RPMs though. >>> How about making this a warning only? > > It looks like the buildservice integration is buggy. it has to install a magic > config file to trigger the actual scoring and error system we have in > factory. Michal will be interested I guess ;-) >>> "Your package containing shared libraries does not end in a digit and >>> should probably be split." >>> For this certain package it already was discussed that it's not a >>> package which fits into the shlib-policy but anyway I guess rpmlint >>> can't decide on that. > > yep. > >>> 6. >>> "The jar file does not contain a META-INF/MANIFEST file." >>> Not all JAR files have to contain a META-INF/MANIFEST file, how about a >>> warning instead of an error? > > it is a warning here. the fact that you see it as an error is because rpmlint > doesn't run in the "openSUSE" mode where you use it. > > Proper rpmlint integration in buildservice is already tracked via bnc#297050, > however it has been completely ignored so far and I honestly don't know who > to assign it to. > > Michal, if you want to improve experience, I suggest to install a config file > with at least one "setBadness()" call in /etc/rpmlint/config. I suggest you > add that to rpmlint-bs. Thanks for the feedback, Wolfgang --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 0