- openSUSE Build Service

[opensuse-buildservice] spec files: package source: file or link?
by Andreas Jellinghaus 22 Sep '06

22 Sep '06

Hi, at least in one suse spec file I saw as source an url to the web site with our source files. I wonder: - is this only for looking for new versions? - If I keep the url in the package, will I still need to provide the downloaded file or will the build server do that for me? - is it better to replace it with the file name, and provide the downloaded and uploaded source .tar.gz? as you can see, I'm a rpm newby, so help is very welcome. Regards, Andreas --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

5 8

[opensuse-buildservice] "build did not create a logfile" ?
by Thomas Anders 22 Sep '06

22 Sep '06

I'm seeing spurious build failures on varying arch/repos for our packages. Unfortunately, "osc log ..." just gives a not-so-helpful "build did not create a logfile" message: net-snmp-main-snapshot$ osc results | grep SuSE SuSE_Factory x86_64 succeeded SuSE_Factory i586 failed: http://api.opensuse.org/result/net-snmp/SuSE_Factory/net-snmp-main-snapshot… SuSE_Linux_10.0 x86_64 succeeded SuSE_Linux_10.0 i586 succeeded SuSE_Linux_10.1 x86_64 failed: http://api.opensuse.org/result/net-snmp/SuSE_Linux_10.1/net-snmp-main-snaps… SuSE_Linux_10.1 i586 succeeded net-snmp-main-snapshot$ osc log SuSE_Factory i586 build did not create a logfile net-snmp-main-snapshot$ osc log SuSE_Linux_10.1 x86_64 build did not create a logfile Is there a BS problem? +Thomas -- Thomas Anders (thomas.anders at blue-cable.de) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

4 4

[opensuse-buildservice] Not sure best list...Need help with an issue while building vultures RPM's.
by Boyd Lynn Gerber 22 Sep '06

22 Sep '06

Hello, Sorry for cross posting. I am not sure which list this issue belongs on. I am getting this error when trying to use the nethack-vultureseye RPM. FATAL: Actual size of gametiles.bin does not match the expected size! Are you sure you are using the gametiles.bin that was built together with this executable? So I am having problems trying to package vultureseye and vulturesclaw. During the building of the to programs they both use/create ./gamedate/graphics/gametiles.bin They use the same source to build both. The only difference in the GNUmakefile is this code path ifeq ($(BUILD), nethack) BUILDDIR := build_n CFLAGS += -DVULTURESEYE else BUILDDIR := build_s CFLAGS += -DVULTURESCLAW endif The problem is that gametiles.bin is being replaced during the RPM build. Making the program with make in the orignal source or using the src RPM creates two seperate and distinct gametiles.bin. But building locally or in the SUSE build service using... osc build SUSE_Linux_10.1 i586 nethack-vultures.spec Here is what I see in the log. ... Leaving directory `/usr/src/packages/BUILD/vultures-2.1.0/nethack/util' ... Entering directory `/usr/src/packages/BUILD/vultures-2.1.0/vultures' ... tiletrans: Wrote 1567 tiles to ./gamedata/graphics/gametiles.bin 267 of 433 objects have unique tiles: 61.7% done 381 of 382 monsters have unique tiles: 99.7% done ... and ... Leaving directory `/usr/src/packages/BUILD/vultures-2.1.0/slashem/util ... Entering directory `/usr/src/packages/BUILD/vultures-2.1.0/vultures' ... tiletrans: Wrote 1567 tiles to ./gamedata/graphics/gametiles.bin 269 of 537 objects have unique tiles: 50.1% done 401 of 612 monsters have unique tiles: 65.5% done ... Here is what I see in the log Entering directory `/usr/src/packages/BUILD/vultures-2.1.0/nethack cd ./config/ ... cd ../graphics cp *.png gametiles.bin /var/tmp/nethack-vultures-2.1.0-0-root-root/usr/games/vultureseye/graphics ... Entering directory `/usr/src/packages/BUILD/vultures-2.1.0/slashem' cp *.png gametiles.bin /var/tmp/nethack-vultures-2.1.0-0-root-root/usr/games/vulturesclaw/graphics ... I am not sure what to do. When I try to add debut echo statements I create SIGSEGFAULT or some such error. Could anyone give me some ideas on trouble shooting this type of -- 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

1 0

[opensuse-buildservice] Bug with Fedora_Extras_4 and yacc (byacc/bison).
by Boyd Lynn Gerber 21 Sep '06

21 Sep '06

Hi, I am getting a yacc not found on Fedora_Extras_4. Below is the error message. yacc -d dgn_comp.y make: yacc: Command not found make: *** [dgn_yacc.c] Error 127 make: Leaving directory `/usr/src/redhat/BUILD/vultures-2.1.0/nethack/util' error: Bad exit status from /var/tmp/rpm-tmp.33147 (%build) I have the following in the spec file. %if 0%{?suse_version} BuildRequires: bison %endif %if 0%{?fedora_version} BuildRequires: byacc %endif I had but thought if I add an other target it may not work. Also the %elseif instead of %else, did not seem to work. %if 0%{?suse_version} BuildRequires: bison %else %if 0%{?fedora_version} BuildRequires: byacc %endif I see this in the log file. It should be byacc not bison or an error that bison is not available. But I get ... installing bison-2.0-6 ... In Fedora_Extras_5 I see (which is correct)... ... installing byacc-1.9-29.2.1 ... -- 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 10

[opensuse-buildservice] A way to copy/move packages
by Dr. Peter Poeml 21 Sep '06

21 Sep '06

Hi, specifically to facilitate moving packages around, in order to join duplicate efforts ;) I have added a new command to osc. Packages are building currently. Combined with the deletepac command, it helps with moving and renaming. % osc help copypac "Copy" a package, possibly cross-project. usage: osc copypac SOURCEPRJ SOURCEPAC DESTPRJ [DESTPAC] The DESTPAC name is optional; the source packages' name will be used if DESTPAC is omitted. Regards, Peter -- SUSE LINUX Products GmbH Bug, bogey, bugbear, bugaboo: Research & Development A malevolent monster (not true?); Some mischief microbic; What makes someone phobic; The work one does not want to do. From: Chris Young (The Omnificent English Dictionary In Limerick Form)

1 0

[opensuse-buildservice] large file upload failing
by Holger Hetterich 21 Sep '06

21 Sep '06

Whenever I upload a very large file, the result is connection reset by peer, regardless of using osc or the Web frontend. The Wesnoth tarball has 71 MBs. I also filed a bug 205704. Any workaround available? Holger --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 2

[opensuse-buildservice] Problem with excluding files with Fedora_Extras_5
by Boyd Lynn Gerber 21 Sep '06

21 Sep '06

Hello, I keep getting these errors on Fedora_Extras_5 RPM build errors: File not found: /var/tmp/nethack-vultures-2.1.0-29.1-root-nobody/usr/games/vultureseye/mapbg.xpm File not found: /var/tmp/nethack-vultures-2.1.0-29.1-root-nobody/usr/games/vultureseye/pet_mark.xbm File not found: /var/tmp/nethack-vultures-2.1.0-29.1-root-nobody/usr/games/vultureseye/rip.xpm File not found: /var/tmp/nethack-vultures-2.1.0-29.1-root-nobody/usr/games/vultureseye/x11tiles These files should be excluded. I have the following in my spec file and have tried all the following top is current, and back. ---------------------------------------------------------- %if 0%{?suse_version} %{_prefix}/games/vultureseye/mapbg.xpm %{_prefix}/games/vultureseye/pet_mark.xbm %{_prefix}/games/vultureseye/rip.xpm %{_prefix}/games/vultureseye/x11tiles %else %endif ---------------------------------------------------------- %if 0%{?suse_version} %{_prefix}/games/vultureseye/mapbg.xpm %{_prefix}/games/vultureseye/pet_mark.xbm %{_prefix}/games/vultureseye/rip.xpm %{_prefix}/games/vultureseye/x11tiles %endif ---------------------------------------------------------- %if %{?suse_version:1}0 %if 0%{?suse_version} %{_prefix}/games/vultureseye/mapbg.xpm %{_prefix}/games/vultureseye/pet_mark.xbm %{_prefix}/games/vultureseye/rip.xpm %{_prefix}/games/vultureseye/x11tiles %endif %endif ---------------------------------------------------------- %if %{?suse_version:1}0 %if 0%{?suse_version} %{_prefix}/games/vultureseye/mapbg.xpm %{_prefix}/games/vultureseye/pet_mark.xbm %{_prefix}/games/vultureseye/rip.xpm %{_prefix}/games/vultureseye/x11tiles %else %endif %endif ---------------------------------------------------------- If I do not have the above I get these files are not in package on all SUSE Builds. How can I get around this error. -- 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

2 2

[opensuse-buildservice] newby questions
by Andreas Jellinghaus 20 Sep '06

20 Sep '06

hi, as a real newby I have lots of questions, maybe you can answer some of these? a) on the web page - why no add all for adding all distributions? would simplify it for most users b) adding the same distribution twice by accident gives an sql error. maybe you want to add code to does that check of handle the mistake more graceful. c) ubuntu edgy might be nice, so packages for the development distribution can be created too. (ok, more of a feature request :) d) is there a code name based selection system for building packages? e.g. it would be nice if I could upload *.diff.gz.sarge *.diff.gz.dapper *.diff.gz.etch and *.diff.gz.edgy with slightly different content for debian sarge/etch and ubuntu dapper and edgy. same again for rpm based distributions - while it might be a nice long term project to look in depth what distributions does what changes and why and how to merge them, as short term project it might be much nicer to edit the spec files, upload a new version of a package and get rebuilds without much work. e) versioning updates: is there any automatic in place that will update the versions e.g. in spec files and debian changelog files? if I upload mysoft 0.a.b+1, would I need to edit all spec files and diff.gz to manualy enter the new version or does some automatic this for me? same with revisions, if dsc files or something is changed. f) debian builds: debian has this habbit of renaming mypackage-0.a.b.tar.gz to mypackage_0.a.b.orig.tar.gz. do I need to upload the same file under both names, or will you take care of this with a symlink or rename for debian builds? g) If I want to jointly develop packages with a group of people, we need a non home: repository, right? and I need to ask here for approval before creating one? h) if I guesses correctly at g) I'd like to have either "smartcard:" or "opensc-project:" or "opensc:" for opensc, openct, libp11, engine_pkcs11, pam-p11, pam_pkcs11, gtkcard, pcsc-lite, libccid, opensc-java and friends i) opensuse buildservice is restricted to open source software as far as I know. what about java addons, are they ok? specifically, if java forces the author to sign them and to keep the signature key private? at opensc-project we have a new project "opensc-java" which is a java crypto service (with smart cards via opensc as backend), and we needed to go through all the hassle of signing it etc. so while the source code is open source, it won't work with java unless signed. so our "build" process would be more like uploading the binaries and only moving files into place (or building from source, but the result wouldn't work at all, as we need to keep the signing key private). h) are there any plans to add the metadata e.g. for debian package pools? (dist/ directory, "Package" files etc.)? thanks for your help! Regards, Andreas --------------------------------------------------------------------- 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 problem with SDL_ttf.h need SDL_ttf-devel.
by Boyd Lynn Gerber 20 Sep '06

20 Sep '06

Hello, I was told that I needed to add SDL_ttf-devel for Fedora builds. How do I get it added to the build service and Is there a way to only include it for Fedora? I do not have access to a Fedora System. Below is the error I am getting... In file included from vultures_win_event.c:13: vultures_txt.h:7:21: error: SDL_ttf.h: No such file or directory make[2]: *** [build_n/vultures_win_event.d] Error 1 make[2]: Leaving directory `/usr/src/redhat/BUILD/vultures-2.1.0/vultures' make[1]: *** [../win/vultures/build_n/vultures.o] Error 2 make[1]: Leaving directory `/usr/src/redhat/BUILD/vultures-2.1.0/nethack/src' make: *** [vultureseye] Error 2 make: Leaving directory `/usr/src/redhat/BUILD/vultures-2.1.0/nethack' error: Bad exit status from /var/tmp/rpm-tmp.29140 (%build) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.29140 (%build) 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

3 2

[opensuse-buildservice] suggestion: auto import from several distributions
by Andreas Jellinghaus 20 Sep '06

20 Sep '06

I think this could be nice: some auto import feature. for example I could add "opensc" and then it would add the files from latest suse factory, fedora core current, mandriva cvs, debian etch and ubuntu dapper. technically - if the package name is the same - it should be easy to get all the srpm / dsc&diff.gz files as at least all big community distributions have an open development tree where everyone can see what happends. a bigger problem might be merging spec files. but maybe an auto inserting %ifdef can be done, so later step by step these can be removed? and sometimes there is the same file in two srpm with different content. it could get a postfix like ".suse" or ".fc5" or something and the %source like could be changed to match that. ok, the more I think about it: not that easy. but any way for developers to find out what (at least the big) distributions are doing with their releases and how they differe from each other would be a nice step forward and a big help for supporting users on linux distributions other than the one someone is using himself. Regards, Andreas p.s. while spec files with %ifdef should allow easy merging of rpm based distributions, I have no clue what to do about debian and ubuntu when they differ. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 0