February 2008 - openSUSE Build Service

[opensuse-buildservice] Re: aggregates broken?
by Dr. Peter Poeml 05 Mar '08

05 Mar '08

[resend, with unidiotified list address] On Thu, Feb 28, 2008 at 12:03:29PM +0100, Michael Schroeder wrote: > On Wed, Feb 27, 2008 at 08:19:30PM +0100, Dr. Peter Poeml wrote: > > what's wrong if aggregates are "blocked" even though the origin package > > is succeeded? > > > > Happens with Apache/GeoIP. > > > > A bug? > > Currently aggregates wait till the complete source project is > built. I see nothing in "devel:libraries:c_c++" nor "Apache" which is not completely built. Still, it is "blocked". By what? Peter -- "WARNING: This bug is visible to non-employees. Please be respectful!" SUSE LINUX Products GmbH Research & Development

1 1

[opensuse-buildservice] Re: [opensuse-project] How should we inform packagers about new upstream versions?
by Pascal Bleser 05 Mar '08

05 Mar '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Christian Morales Vega wrote: > Sometimes do you find packages in the OBS that are outdated. You never > know why, perhaps the packager doesn't knows about the new upstream > version and perhaps he knows but is just busy. > Up to now when I found such a case I reported it like an "Enhancement" > bug in bugzilla. But some packagers think bugzilla isn't the correct > place for such a thing. > > If the packager doesn't knows about the new version he can leave the > package outdated for a long time. So would be good that, at some time, > if an user finds the problem he reports it. But, how should be > reported? There is any feature planned in the OBS to help with this? > What other distros do? A very good point. Personally, I think Bugzilla is the best place to report it. It also makes it much easier to track the status. The problem is finding the relation package->packager, to know whom to assign the Enhancement request. IIRC there's the option for packagers to include bugzilla information in their OBS projects and packages now -- I haven't looked at it yet, so I can't say much more about it. But it should really be made easily available to end-users. IMO the easiest option would be to use the %PACKAGER tag in the rpm files for that ("rpm -q --qf '%{PACKAGER}\n' foobar" or "rpm -qi foobar"), but it would require adding that feature to the OBS (or rather, to build). Would be better discussed on opensuse-buildservice(a)opensuse.org though, which is why I'm CC'ing this email there (please followup on that list). cheers - -- -o) Pascal Bleser <pascal.bleser(a)opensuse.org> /\\ http://opensuse.org -- I took the green pill _\_v FOSDEM::23+24 Feb 2008, Brussels, http://fosdem.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFHxb1Jr3NMWliFcXcRAk1GAKCBVdhDitbbBokX6CilM44e51Og0ACeMS0S J2Z66hkPrbvlpiFyqtSjw30= =mnns -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

5 4

[opensuse-buildservice] ANN: Yabsc 0.2
by James Oakley 05 Mar '08

05 Mar '08

I have just made a second release of Yabsc. Source can be downloaded from http://www.funktronics.ca/yabsc/ Packages can be found at http://software.opensuse.org/search?baseproject=openSUSE%3A10.3&p=1&q=yabsc Changes include: - The "All" tab now shows results for all project targets - The views now use more flexible custom data models - The code size has actually decreased by 30% On the TODO list: - Make non-blocking API calls - Make refresh interval configurable - Save window geometry on exit - Allow adding projects to the watchlist -- 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

3 3

[opensuse-buildservice] Cannot get gpg keys from BS.
by Boyd Lynn Gerber 05 Mar '08

05 Mar '08

Hello, I am trying to build some of the projects in my home:gerberb Verifying integrity of cached packages The following package could not be verified: /var/tmp/osbuild-packagecache/home:gerberb/openSUSE_10.3/i586/python-pydns-2.3.0-8.1.i586.rpm: (SHA1) DSA sha1 md5 (GPG) NOT OK (MISSING KEYS: GPG#d986a842) - If the key is missing, install it first. For example, do the following: gpg --keyserver pgp.mit.edu --recv-keys d986a842 gpg --armor --export d986a842 > /home/gerberb/keyfile-d986a842 and, as root: rpm --import /home/gerberb/keyfile-d986a842 Then, just start the build again. This is what I get... gpg --keyserver pgp.mit.edu --recv-keys d986a842 gpg: requesting key D986A842 from hkp server pgp.mit.edu gpgkeys: key D986A842 not found on keyserver gpg: no valid OpenPGP data found. gpg: Total number processed: 0 What can be done? Thanks, -- Boyd Gerber <gerberb(a)zenez.com> ZENEZ 1042 East Fort Union #135, Midvale Utah 84047 --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

4 3

[opensuse-buildservice] Newbie: just wishing to compile
by Luciano Mannucci 05 Mar '08

05 Mar '08

Hello folks! I'm new to the build service. I have an apple PPC laptop with OpenSuse 10.3 and I just wish to compile packages fromthe build services that are already there only for the intel platforms. Do I need to start a new projet of my own each time or can I use the existing ones? I don't think I need to rewrite my own specs from scratch... Thanks for any help, luciano. -- /"\ /Via A. Salaino, 7 - 20144 Milano (Italy) \ / ASCII RIBBON CAMPAIGN / PHONE : +39 2 485781 FAX: +39 2 48578250 X AGAINST HTML MAIL / E-MAIL: posthamster(a)sublink.sublink.ORG / \ AND POSTINGS / WWW: http://www.mannucci.ORG/ --------------------------------------------------------------------- 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] Mandriva 2008 added / 2007 fixed
by Adrian Schröter 02 Mar '08

02 Mar '08

Hi, I added Mandriva 2008 due to request. Build is possible for i586 and x86_64 architectures. Mandriva 2007 x86_64 build got fixed as well. The openSUSE:Tools project does build our tools for these targets now as reference. bye adrian -- 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

4 6

[opensuse-buildservice] Build fails because unit tests runs daemon
by John Calcote 29 Feb '08

29 Feb '08

Hi list, I added a unit test to my project at home:jcalcote/dnx This project built on all flavors of SuSE linux, plus fedora, debian, and ubuntu 7 before I added this new unit test. Now it fails on all but the debian and ubuntu builds - probably because these platforms' hacked up control files don't run "make check". I can successfully build this package locally - it just won't build on the obs servers. DETAILS: The unit test I added was a shell script to load my client daemon, ensure that it initialized properly, then send it a kill signal and wait for it to cleanup its own lock file (dnxClient.pid). Now, before you jump all over me for trying to write files to system directories during a build, be aware that I've configured my daemon to use a test directory for such files. Here's the relevant portion of the test script: - - - - - - - - - - - - - - - - - - # Execute the dnx client as a daemon ./dnxClient -c $PWD/testrun/test.cfg -r $PWD/testrun \ -l $PWD/testrun/test.log -D $PWD/testrun/test.dbg # Give it time to create its lock file count=0 while ((count<15)) && [ ! -e $PWD/testrun/dnxClient.pid ]; do sleep 1; let count++ done # Ensure we HAVE a lock file now if [ ! -e $PWD/testrun/dnxClient.pid ]; then echo "dnxClient.pid NOT found - daemon didn't start!" exit 1 fi - - - - - - - - - - - - - - - - - - Here's a portion of the build log from the openSUSE:10.2 target: - - - - - - - - - - - - - - - - - - ... Making check in client make[1]: Entering directory `/usr/src/packages/BUILD/dnx-0.15.1/client' /usr/bin/make check-TESTS make[2]: Entering directory `/usr/src/packages/BUILD/dnx-0.15.1/client' dnxClient.pid NOT found - daemon didn't start! FAIL: dnxClientTest.sh ================================================ 1 of 1 tests failed Please report to dnx-devel(a)lists.sourceforge.net ================================================ make[2]: *** [check-TESTS] Error 1 ... - - - - - - - - - - - - - - - - - - You can see that the script prints this message when the dnxClient daemon doesn't write its lock file. FYI, the command line options are: -c - specify configuration file. -r - specify run path (where the pid file will be created) -l - specify the log file name. -D - specify the debug log file name. I'm guessing there's some rule against running programs on the build servers that use fork-fork-exec. Any help would be much appreciated. 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

4 11

[opensuse-buildservice] Requesting help creating a .spec file for Exaile
by Adam Olsen 28 Feb '08

28 Feb '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I am the lead developer of Exaile (http://www.exaile.org) and I'd like to use the openSUSE build service to create packages for it. I've read through the tutorial, but I'm wondering, how do I find out what the different deps are named on different distros? Are there any example .spec files for pygtk apps available? Thanks in advance. - -- Adam Olsen SendOutCards.com http://www.vimtips.org http://last.fm/user/synic -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: http://firegpg.tuxfamily.org iD8DBQFHxvuITSjho5GlGw8RAsaTAKCaFd2Pf/cESs1dD3PCpx7Re424cwCeP8I6 yIDm10ue37fHfcvUR3HuMrI= =ci1v -----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 1

[opensuse-buildservice] Help needed to build google-perftools packages for 64 bit Linux/Solaris/AIX
by Bollam Lavanya 28 Feb '08

28 Feb '08

Hi, I am new to this group. Please help me how should I proceed to get the 64 bit package for google-perftools through openSuse. The google-perftools packages contains some utilities to improve and analyze the performance of C++ programs. This includes an optimized thread-caching malloc() and cpu and heap profiling utilities. Currently we can get32 bitversion of this on internet. But I need 64 bitversion. Thanks Lavanya

3 3

[opensuse-buildservice] Questions about a .spec file to compile a patched kernel
by doiggl＠velocitynet.com.au 27 Feb '08

27 Feb '08

Hello all, I have a wish to put up into the opensuse build service a rpm (factory) build of the following application, but I am stuck on constructing a good .spec file which will apply the patch to the kernel source ,and then compile it into an installable rpm, and I was wondering if you could help me with this please. It will be a steep learning curve for me as I am new to all this. Application:reiser4-for-2.6.24 Source patch for Kernel: http://chichkin_i.zelnet.ru/namesys/reiser4-for-2.6.24.patch.gz Developer info links: http://marc.info/?l=reiserfs-devel&r=1&w=2 http://www.nabble.com/ReiserFS---General-f1023.html Question 1 Do I need to copy Linux Kernel(s) From: http://download.opensuse.org/repositories/Kernel:/HEAD/openSUSE_Factory/x86… and http://download.opensuse.org/repositories/Kernel:/HEAD/openSUSE_Factory/i58… To: ..../home/XXX/src/kernel-default-2.6.24... Questions: 2. Do I need a 2 copies of the Kernel Source for each platform (x86_64 & i586) ? (eg kernel-source-2.6.24.?-??.?.x86_64.rpm and kernel-source-2.6.24.?-??.?.i586.rpm ) 3. Can someone provide me a .spec and .config file which will do the following thins: - Unpack the Kernel Sources (both platforms x86_64 & i586) - Apply the patch e.g (patch -p1 < ..../home/XXX/src/reiser4-for-2.6.24.patch) - Copy in a good .config file (Do I need one/where do I copy it to ?) - make/build the rpm installable binary and patched source code rpm packages (using make binrpm-pkg ?? ) - 4. Can the make/build process output a output an rpm like kernel-reiser4-2.6.24.1-76.1.x86_64.rpm and kernel-reiser4-2.6.24.1-76.1.i586.rpm 5. How do I use the .spec and .config file do I have to upload them somewhere ?. 6. Finally how and when do I know the build process passed/failed ? Thankyou for your help. Glenn. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

5 6