openSUSE Build Service August 2009

buildservice@lists.opensuse.org

54 participants
73 discussions

[opensuse-buildservice] Mandriva 2009 - problem with mysterious X
by Marcin Wojdyr 21 Aug '09

21 Aug '09

Hello, when compiling program on Madriva 2009, it seems that every libtool option has 'X' prepended. The package builds without any problems on all other RPM-based hosts. make[2]: Entering directory `/usr/src/rpm/BUILD/xylib-0.4/xylib' /bin/sh ../libtool --tag=CXX --mode=compile i586-mandriva-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I.. -O2 -g -pipe -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -fomit-frame-pointer -march=i586 -mtune=generic -fasynchronous-unwind-tables -MT libxy_la-xylib.lo -MD -MP -MF .deps/libxy_la-xylib.Tpo -c -o libxy_la-xylib.lo `test -f 'xylib.cpp' || echo './'`xylib.cpp ../libtool: line 844: X--tag=CXX: command not found ../libtool: line 877: libtool: ignoring unknown tag : command not found ../libtool: line 844: X--mode=compile: command not found The full log: https://build.opensuse.org/package/live_build_log?arch=i586&package=xylib&p… Any ideas what's wrong here? Thanks, Marcin -- Marcin Wojdyr | http://www.unipress.waw.pl/~wojdyr/ -- 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] Import build service packages into git
by Andreas Gruenbacher 21 Aug '09

21 Aug '09

Hello, I have been working on an import tool from the build service into git repositories; the result seems to be basically working now. It is available as: home:agruen:Factory/bsgit The git repository is available at: http://git.opensuse.org/?p=people/agruen/bsgit.git Exporting changes into the build service is not supported yet, but it's a start. Integration into osc also hasn't happened, yet. The tool tries to be nice to the server and not request the same data over and over again. Still, when fetching a package, this retrieves all the package's revisions unless you create a shallow copy using bsgit's --depth=N option. So please do not blindly fetch huge packages with a long history just to see what happens. (What would happen is pretty clear -- I would get into troubles with the build service maintainers!) Here is how to use bsgit: $ mkdir stuff $ cd stuff $ git init $ bsgit fetch home:agruen:Factory bsgit Fetching home:agruen:Factory/bsgit (1) Fetching home:agruen:Factory/bsgit (2) Branch 'bsgit' created. $ git branch -a * bsgit remotes/api.opensuse.org/home/agruen/Factory/bsgit $ bsgit pull Fetching home:agruen:Factory/bsgit (3) Branch 'bsgit' updated. $ bsgit fetch Already up-to-date. Observe that bsgit created a remote branch with a long name that encodes the server, project, and package. This is the state of the package in the build service. A local branch, 'bsgit', tracks that remote branch. You may make changes on the local branch. When you fetch a package, this will leave the local branch alone (except for creating it when it doesn't exist). A pull does a fetch, followed by a rebase of the local branch. (It doesn't do a merge because we will not be able to export merges to the build service anyways, at least not with the current backend.) When bsgit detects a source link, it creates a remote branch for the target package as well (i.e., the package linked to), and it expands the source link. Source links are expanded against the revision of the target package that they were *created* against. Very unfortunately, the build service backend does not record the revision it creates a source link against. Until that is fixed (and I hope soon!), some guessing is involved, and some source links may be expanded against the wrong revision. Here is a source link example: $ bsgit clone home:coolo:branches:home:darix:Factory FastCGI Fetching openSUSE:Factory/FastCGI (1) Fetching openSUSE:Factory/FastCGI (2) Fetching openSUSE:Factory/FastCGI (3) Fetching home:darix:Factory/FastCGI (1) Fetching home:coolo:branches:home:darix:Factory/FastCGI (1) Fetching home:coolo:branches:home:darix:Factory/FastCGI (2) Branch 'FastCGI' created. $ git branch -a * FastCGI remotes/api.opensuse.org/home/coolo/branches/home/darix/Factory/FastCGI remotes/api.opensuse.org/home/darix/Factory/FastCGI remotes/api.opensuse.org/openSUSE/Factory/FastCGI Cheers, Andreas -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

5 15

[opensuse-buildservice] build fails because: extractbuild failed
by Hans-Peter Jansen 21 Aug '09

21 Aug '09

Hi, lately, I found sporadic builds failing with: booting XEN kernel ... xm create -c /var/run/bsworker_5/build/xen.conf name=build:5_root memory=750 disk=phy:/dev/abuild/5_root,hda1,w disk=phy:/dev/abuild/5_swap,hda2,w extra=quiet init=/.build/build panic=1 console=ttyS0 Using config file "/var/run/bsworker_5/build/xen.conf". Error: Domain 'build:5_root' already exists with ID '27' extractbuild failed It would be nice to detect those, and restart the build. Thanks, Pete -- 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] Source for software.opensuse.org
by Luke Imhoff 21 Aug '09

21 Aug '09

I'm trying to switch the *.opensuse.org links in our local OBS instance to point to internal versions of those pages and was wondering where the source for software.opensuse.org is located. It would be nice to be able to do searches on the rpms we generate from our internal OBS the same way I can for the public OBS now. If not all of software.opensuse.org is available then at least the part that corresponds to http://software.opensuse.org/search would be nice. -- 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] Need help to build package - ramlog
by doiggl＠velocitynet.com.au 20 Aug '09

20 Aug '09

Hello, I would like to build the following application in opensuse build service (against factory repo both 32 and 64 bit) and I need step by step guide to setup, compile and build the rpms in the build service . Thankyou Glenn So far I have got some details. - Details of the project > http://freshmeat.net/projects/ramlog/ and http://tofu3.szm.sk/ramlog/ - An account on opensuse build service on which to build it. - Rpm source code (I don't know which one to use out of these to use for the build process) > http://tofu3.szm.sk/ramlog/1.1.0/rpm/ramlog-1.1.0-1.noarch.rpm > or http://tofu3.szm.sk/ramlog/1.1.0/rpm/ramlog-1.1.0-1.src.rpm > or http://tofu3.szm.sk/ramlog/1.1.0/ramlog-1.1.0-1.tar.gz - Changelog details > http://tofu3.szm.sk/ramlog/changelog.txt - Contents of the spec file gotten from source (see below) #rpm -qlp ramlog-1.1.0-1.src.rpm ramlog-1.1.0-1.tar.gz ramlog.spec # rpm -ivhU ramlog-1.1.0-1.src.rpm 1:ramlog warning: user jandrejkovic does not exist - using root warning: group jandrejkovic does not exist warning: user jandrejkovic does not exist warning: group jandrejkovic does not exist # # ramlog.spec contents # # cat /usr/src/packages/SPECS/ramlog.spec Summary: ramlog daemon places /var/log into ramdisk on startup and copies it back to harddisk on shutdown Name: ramlog Version: 1.1.0 Release: 1 License: GPL v3 Group: System Environment/Daemons Source: %{name}-%{version}-%{release}.tar.gz #Source0: %{name}-%{version}-%{release}.tar.gz #Source1: ramlog.8.gz #Source2: ramlog.cron #Source3: %{name}-%{version}-%{release} ##Patch: ramlog1.0.0.patch BuildRoot: /var/tmp/%{name}-buildroot Requires: coreutils, e2fsprogs, util-linux, gawk, lsof, grep, chkconfig Packager: Jan Andrejkovic BuildArch: noarch %description ramlog act as system daemon. On startup it creates ramdisk, it copies files from /var/log into ramdisk and mounts ramdisk as /var/log. All logs after that will be updated on ramdisk. On shutdown it saves log files back to harddisk so logs are consistent. If you restart the service, ramlog saves content of ramdisk do harddisk, so logs are not lost in case of power outage or kernel panic. Install ramlog if you have enough of free memory and you want to keep your logs on ramdisk. It is good for notebook users, for systems with UPS or for systems running from flash - to save some write cycles. %install [ "$RPM_BUILD_ROOT" != "/" ] && rm -rf $RPM_BUILD_ROOT mkdir -p $RPM_BUILD_ROOT mkdir -p -m 755 $RPM_BUILD_ROOT/etc/rc.d/init.d mkdir -p -m 755 $RPM_BUILD_ROOT/usr/share/man/man8/ mkdir -p -m 755 $RPM_BUILD_ROOT/etc/cron.daily install -m 644 ramlog.8.gz $RPM_BUILD_ROOT/usr/share/man/man8/ramlog.8.gz install -m 755 ramlog.cron $RPM_BUILD_ROOT/etc/cron.daily/ramlog install -m 755 %{name}-%{version}-%{release} $RPM_BUILD_ROOT/etc/rc.d/init.d/ramlog [ $? -ne 0 ] && (echo Error: ramlog was not installed successfully; exit 1) %pre #Below check is not needed if the same version of ramlog is beeing installed, however if new version is installed #it is always better to uninstall properly first, otherwise if new feature is introduced, uninstall may not work properly if [ -f /var/tmp/ramlog_uninstall_flag_file ]; then echo ramlog was not completely uninstalled, you have to restart the system first\! exit 1 fi #[ -f /var/tmp/ramlog_uninstall_flag_file ] && rm -f /var/tmp/ramlog_uninstall_flag_file exit 0 %post logsize=`du -c /var/log | tail -1 | awk {'print $1'}` logsizemax=$(($logsize+$logsize/100*35)) #add 35% logsizemax=$(($logsizemax/1000*1000+1000)) #round to megabytes memtotal=`cat /proc/meminfo | grep MemTotal: | awk '{print $2}'` memleft=$(($memtotal-$logsizemax)) #My formula: (Total memory - (logsize + 35%)) > 256 M [ $memleft -lt 256000 ] && { echo Error: Not enough memory - Total memory is $memtotal kbytes, logsize is $logsize kbytes; exit 1; } if [ -f /sbin/new-kernel-pkg ]; then if [ `/sbin/new-kernel-pkg --help 2>&1 | grep -e --update | wc -l` -eq 1 ]; then /sbin/new-kernel-pkg --kernel-args=ramdisk_size=$logsizemax --update `uname -r` else /sbin/new-kernel-pkg --kernel-args=ramdisk_size=$logsizemax --install `uname -r` fi else echo "ramlog: Warning: You have to add kernel parameter ramdisk_size manually. Estimated value is $memleft, so you add \"ramdisk_size=$memleft\" as a kernel paramter to your boot manager configuration file - such as grub.conf or lilo.conf" fi #/bin/sed -i -e "s/^RAMDISKSIZE=[0-9][0-9]*/RAMDISKSIZE=${logsizemax}/g" /etc/rc.d/init.d/ramlog /sbin/chkconfig --add %{name} /sbin/chkconfig %{name} on %preun cp /etc/rc.d/init.d/ramlog /etc/rc.d/init.d/ramlog.uninst %postun if [ -f /sbin/new-kernel-pkg ]; then /sbin/new-kernel-pkg --remove-args=ramdisk_size --update `uname -r` else echo "ramlog: Warning: You have to remove/update kernel parameter ramdisk_size in your grub.conf or lilo.conf manually." fi mv /etc/rc.d/init.d/ramlog.uninst /etc/rc.d/init.d/ramlog /sbin/chkconfig --add %{name} /sbin/chkconfig %{name} on /sbin/service %{name} uninstall %clean [ "$RPM_BUILD_ROOT" != "/" ] && rm -rf $RPM_BUILD_ROOT %files %defattr(-,root,root) #%doc README TODO COPYING ChangeLog %doc README COPYING ChangeLog INSTALL FAQ VERSION /etc/rc.d/init.d/ramlog /etc/cron.daily/ramlog /usr/share/man/man8/ramlog.8.gz %changelog * Sun Jun 08 2008 Jan Andrejkovic <jandrejkovic(a)gmail.com> - version 1.1.0 released: - added support for Ubuntu - added support for SELinux - now ramlog saves security context of all files in /var/log - logs are saved to HDD even if stop is not successful - added logging feature - created .deb package for Ubuntu - fixed some bugs * Wed Jan 13 2008 Jan Andrejkovic <jandrejkovic(a)gmail.com> - first version 1.0.0 released - created .rpm package -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

8 29

[opensuse-buildservice] Pruning builds to conserve build power?
by Lars Marowsky-Bree 20 Aug '09

20 Aug '09

Hi, I'm not sure whether this has been given some thought yet. But it seems that there's an awful lot of build power "wasted" to rebuild packages that don't have users (anymore), or a lot of _links around which are no longer used etc. Is there possibly some way to prune them from blocking the rebuild power of the system? Low-key solution: require that each "build & publish" bit is refreshed manually every N weeks? Regards, Lars -- Architect Storage/HA, OPS Engineering, Novell, Inc. SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) "Experience is the name everyone gives to their mistakes." -- Oscar Wilde -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

4 5

[opensuse-buildservice] Packagers Section in Weekly News
by Sascha 'saigkill' Manns 20 Aug '09

20 Aug '09

Hello Mates, today i got an interesting Idea in our Weekly News Survey. An User asks for an own Packaging Section. He mean that that is an place for Packagers to announce fixed Packages (with an Bugzilla Reference). So the Weekly News Format is maybe: * Bugzilla-Number and Summary * Package and Version * Date and Packager * Free Text: What is changed. (Short Issue). Exists interesting about that Idea? Would Packager like to announce through the Weekly News? -- Sincerely yours Sascha Manns openSUSE Ambassador openSUSE Marketing Team openSUSE Build Service Web: http://saschamanns.gulli.to Project-Blog: http://lizards.opensuse.org/author/saigkill Private-Blog: http://saschasbacktrace.blogspot.com -- 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] server:php repository warning
by Cristian Rodríguez 20 Aug '09

20 Aug '09

Hi: Recently we have switched server:php repositories to PHP 5.3.x , there are a number of issues that you should be aware in case you are using them - In some builds, mysql extensions are broken, this has been fixed in the meanwhile. - Initial testing results are far from promising... if you find any problem please fill a bug report at bugzilla.novell.com - There is an inconsistency between server:php and server:php:extensions so packages may get uninstalled, or broken on upgrade, this is temporary. Thanks for flying with openSUSE ;-) . -- 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] How to change my email address?
by Paul Elliott 19 Aug '09

19 Aug '09

Home of pelliott11 https://build.opensuse.org/home shows my name and email address. My email address has changed. How do I change it? "Edit User Data" and "Edit Tag Data" show no applicable fields. Than You. -- Paul Elliott 1(512)837-1096 pelliott(a)BlackPatchPanel.com PMB 181, 11900 Metric Blvd Suite J http://www.free.blackpatchpanel.com/pme/ Austin TX 78758-3117

2 5

RE: [opensuse-buildservice] -fPIC failing on RHEL5/CentOS5 builds?
by Scott Cantor 19 Aug '09

19 Aug '09

Scott Cantor wrote on 2009-08-18: > So, ummm, that ain't from me. I did try passing the mcpu option in a simple > command manually when I scanned my working config.log, but I didn't get that > deprecation warning at the time, so I'm looking into it, but seems to me > this is a problem. (For anybody else's benefit...) I found the docs on controlling the build and from what I can tell the osc source code and my local copy of the settings includes OptFlags that match the right compiler settings but the default values used by the build service in the VMs are out of date. I'm attempting to override them with the new defaults and expect that will fix it. I guess I'd ask that whoever maintains the remote builds update those defaults if possible. Non-relocatable code causes problems with SELinux among other things. -- Scott -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 0

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Build Service August 2009