August 2009 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] [PATCH] Add --build-abuild-id to osc and build and add --map-repo to osc
by David Greaves 22 Feb '10

22 Feb '10

When building locally in a qemu/chroot and debugging I find I want to edit the files in the chroot from my desktop gui editor but they're all owned by 399:399. This pair of patches allows me to set the uid:gid to match my local user and eases this process. usage is: build --build-abuild-id uid:gid or more usually: osc build --build-abuild-id 500:500 osc also accepts (and extends the default) .oscrc settings: build-abuild-id = 500:500 It only supports numeric ids. The osc patch also adds --map-repo to aggregatepac which allows repository mapping(s) to be given as SRC=TARGET[,SRC=TARGET] eg, a real usage: osc aggregatepac -m MerStable_Debian_5.0=Mer0.13_Debian_5.0,MerStable_Ubuntu_9.04=Mer0.13_Ubuntu_9.04 Maemo:Mer:0.13:HW:N8x0 advanced-power Maemo:Mer:Stable:HW:N8x0 https://build.opensuse.org/package/view_file?file=_aggregate&package=advanc… David -- "Don't worry, you'll be fine; I saw it work in a cartoon once..."

3 5

[opensuse-buildservice] cannot open Pubkeys index using db3 - No such file or directory (2)
by Dave Plater 02 Oct '09

02 Oct '09

Hi, can anyone tell me what this means :- RPM build errors: cannot open Pubkeys index using db3 - No such file or directory (2) Thanks Dave P -- 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] Why doesn't osc use rpm-python?
by Luke Imhoff 14 Sep '09

14 Sep '09

Is there a reason why osc calls rpm directly using subprocess instead of using the rpm python library from rpm-python? I'm trying to finish Marcus Hüwe work on injecting local rpm data and I was going to use the rpm library, but if there's some design reason to not use it, I'll use subprocess calls to rpm. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 7

[opensuse-buildservice] osc 0.121 candidate
by Adrian Schröter 07 Sep '09

07 Sep '09

Hi, there were plenty changes in osc svn, so it is time for a new release. However, there might be unwanted incompatibilities, so I prepared first a candidate in openSUSE:Tools:Unstable Have a look here for the 0.121 packages: http://software.opensuse.org/search?baseproject=openSUSE:Tools:Unstable&p=1… (installing the package alone should be sufficient, no need to add the repo) There are esp. many fixes for the request handling and Juergen also implemented new interesting commands like "osc my ..." to get an overview about "my" packages, projects or requests. Also plenty of convenience commands have been add by Juergen. There are of course also further changes, check the NEWS file for more details. I would like to hear some "great stuff" or "why the heck has _THIS_ changed" comments before making this an official release. please help testing :) thanks adrian -- Adrian Schroeter SUSE Linux Products GmbH 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

6 12

[opensuse-buildservice] How to debug when "OpenSUSE Webclient Error" occured ?
by Jian Lee 27 Aug '09

27 Aug '09

Hi, guys I've setup obs-server on CentOS platform from obs-server-1.6.0-14.1.src.rpm owned by openSUSE 10. Configure mysql database, Tune the IP interface to LAN : ----------------------------- # grep { /etc/lighttpd/vhosts.d/obs.conf $HTTP["host"] =~ "172.16.70.30\.?" { $SERVER["socket"] == "172.16.70.30:81\.?" { $SERVER["socket"] == "172.16.70.30:82\.?" { =========================================== Then Use the "Admin"/"opensuse" as Username/Password to login. First time no error occured, but now It has "OpenSUSE Webclient Error" when i login 172.16.70.30 (http://172.16.70.30/home) : --------------------------------------------------------- Error Details: Errorcode: unknown Message: <?xml version="1.0" encoding="iso-8859-1"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> <head> <title>404 - Not Found</title> </head> <body> <h1>404 - Not Found</h1> </body> </html> Exception from Webclient: ActiveXML::Transport::NotFoundError: <?xml version="1.0" encoding="iso-8859-1"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> <head> <title>404 - Not Found</title> </head> <body> <h1>404 - Not Found</h1> </body> </html> Stack Trace: /srv/www/obs/common/lib/activexml/transport.rb:543:in `handle_response' /srv/www/obs/common/lib/activexml/transport.rb:534:in `http_do' /srv/www/obs/common/lib/activexml/transport.rb:346:in `find' /srv/www/obs/common/lib/activexml/base.rb:69:in `find' /srv/www/obs/webclient/app/controllers/application.rb:116:in `basic_auth' /srv/www/obs/webclient/app/controllers/application.rb:74:in `authorize' .... ==================================================================== Did anyone have ideas ? Thanks, all -- Jian Lee Chinese Blog : http://jianlee.ylinux.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] osc reference like what was done for zypper.
by Boyd Lynn Gerber 26 Aug '09

26 Aug '09

Hello, I was wondering if we could put together a card like the one just release for zypper but for osc. I really like the zypper one. After seeing it I was thinking "Whooowwww, I realy could use one like this for osc" Any way, I think I could assist, but not really be the lead. -- Boyd Gerber <gerberb(a)zenez.com> 801 849-0213 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] Build Team Meeting
by Adrian Schröter 26 Aug '09

26 Aug '09

present: mls, bg, cwh, lrupp, adrian Topics: * Status * Downtime expected between 2009-09-11 - 13th * Attribute system Status Round ============ mls/abauer: * got complains about software search, but this is on hold since a long time. We need to discuss how and when the software portals may solve this on the openSUSE conference. mls: * working on bs_worker product creation support (obsoleting local worker) -> open issue is how to do the signing adrian: * trouble with dead build host hardware. It seems all of the newer and powerfull 16x build hosts are about to die due to hardware failures. * dig into lxc in general, prepare usage for source services Downtime expected on 2009-09-11 till 13th ======================================== Due to scheduled power outage of our building we will be down on 12th and 13th september. We will use 11th afternoon for updating our main servers (from SLES 10 to 11). Affected public services are: download.opensuse.org (we may find a backup solution for this one) software/build/api.opensuse.org lists.opensuse.org features.opensuse.org Attribute System ================ * API implementation is complete except for - default values are not supported yet - extra permissions (acl) -- Adrian Schroeter SUSE Linux Products GmbH 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

[opensuse-buildservice] submitreqs vanished
by Christian 26 Aug '09

26 Aug '09

Hi, just wondering where all my sr are gone. ON webapi there are none listed. But they weren't accepted, because all "project.diff" are still in my projects. Any idea ? Kind Regards Chris -- 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] Install OBS in CentOS -- "Webclient Error: Unable to connect to API"
by Jian Lee 26 Aug '09

26 Aug '09

Hi, your guys! I want install obs on CentOS 5, after I build obs-server-0.9.1-4.1.src.rpm, and installed ------------------------- # rpm -qa|grep obs obs-worker-0.9.1-4.1 obs-api-0.9.1-4.1 obs-server-0.9.1-4.1 ========================= follow the cache page on google http://203.208.39.132/search?q=cache:Dm1eKDTlDg4J:https://forgesvn1.novell.… and install guide on http://en.opensuse.org/Build_Service/Build_Service_Installation_Tutorial/Ce… use the default configure but just modified the ip interface and username/password of mysql database , and create the needed empty database in mysql server . but when i login the web interface, i get following errors: --------------------------- OpenSUSE Webclient Error: Error Details: Errorcode: 500 Message: Unable to connect to API =========================== no useful info I found in /srv/obs/log/ and /var/log/lighttpd/, anyone can give me a help? Thanks for all your guys! -- Jian Lee MSN : lijian.gnu(a)gmail.com -- 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] package download
by Peter Czanik 25 Aug '09

25 Aug '09

Hello, Is there an easier way of downloading packages from unpublished repositories than one by one with copy&pase of URL-s? I mean, https://build.opensuse.org/project/show?project=home%3Adl9pf%3Abranches%3Ao… is not yet published, but I can get a package list at https://api.opensuse.org/build/home:dl9pf:branches:openSUSE:Factory/crossco… and download them copy&paste of package names from the XML files, for example https://api.opensuse.org/build/home:dl9pf:branches:openSUSE:Factory/crossco… to get mingetty. Right now I can boot openSUSE ARM, but it is just base:build:arm, which is pretty limited, without mingetty, udev, etc. I'd like to bring it to console login, and then to sshd, but downloading packages this way is a bit time consuming :-) Bye, CzP -- 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] --ignorearch
by Peter Czanik 25 Aug '09

25 Aug '09

Hello, Yesterday I tried to install a few packages on ARM and it failed with: "package mingetty-1.0.7s-94.5.arm7l is intended for a armv7l architecture" Of course the machine is armv7l arthitecture and the package works fine when installed with rpm's --ignorearch option. Where rpm looks for architecture information? dl9pf wrote last evening, that: (17.59.58) |dl9pf|: what's the output of uname -a and cat /proc/cpuinfo on the board ? (18.00.19) |dl9pf|: rpm checks some of these and complains - buildservice uses rpm --ignorearch I'd try to fix it for my board in the kernel sources, if I knew what to change. Here is the current output: (21.23.15) CzP: czanik@bigone111:~> cat uname.txt (21.23.15) CzP: Linux bigone111 2.6.26-394-gf56b72e #1 PREEMPT Wed Jun 24 17:19:45 CEST 2009 armv7l armv7l armv7l GNU/Linux (21.23.48) CzP: czanik@bigone111:~> cat cpuinfo.txt (21.23.48) CzP: Processor : ARMv7 Processor rev 1 (v7l) (21.23.48) CzP: BogoMIPS : 799.53 (21.23.48) CzP: Features : swp half thumb fastmult vfp edsp (21.23.48) CzP: CPU implementer : 0x41 (21.23.48) CzP: CPU architecture: 7 (21.23.48) CzP: CPU variant : 0x2 (21.23.48) CzP: CPU part : 0xc08 (21.23.48) CzP: CPU revision : 1 (21.24.06) CzP: Cache type : write-back (21.24.06) CzP: Cache clean : read-block (21.24.06) CzP: Cache lockdown : not supported (21.24.06) CzP: Cache format : Unified (21.24.06) CzP: Cache size : 768 (21.24.06) CzP: Cache assoc : 1 (21.24.06) CzP: Cache line length : 8 (21.24.06) CzP: Cache sets : 64 (21.24.06) CzP: Hardware : Freescale MX51 Babbage Board (21.24.06) CzP: Revision : 51020 (21.24.06) CzP: Serial : 0000000000000000 Bye, CzP -- 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] Weekly News: Announcing Meetings via news.o.o
by Sascha 'saigkill' Manns 24 Aug '09

24 Aug '09

Hello Mates, i would just remind you, to announce meetings in news.o.o too. The thing behind them is, that we use an script for fetching news.o.o events automaticly. It would be great if we all have the events on an central place. Thank you very much :-) -- 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

1 0

[opensuse-buildservice] different control files for different debian platforms?
by Paul Elliott 24 Aug '09

24 Aug '09

Is it possible to have different control files for different debian platforms? I have a package that has a Build-requires dependancy of libboost-dev for most debian platforms, however, xUbuntu 9.04 wants this to be libboost1.35-dev. Is it possible to have a control-xUbuntu_9.04 file the same way you can have a foo-Fedora_Extras_6.spec for rpm based distributions? What is the best way to handle this? I don't think you can ifdef a debian control file the way you can a rpm spec file. Thank 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

4 11

[opensuse-buildservice] mandriva_version broken on 2009.1
by Stephan Kleine 24 Aug '09

24 Aug '09

Hi folks. I just noticed that one is neither able to specifically target Mandriva 2009.1 with %if tags in .specs nor do packages containing %{?mandriva_version} build for 2009.1 because the %if comparison always results in a parse error cause of the ".". The way I see it that can be fixed in two ways: 1. The %if %else %endif comparison gets fixed 2. The mandriva_version numbering scheme is changed for all supported Mandriva versions so it is similar to the openSUSE one - 2008 -> 200800, 2009 -> 200900, 2009.1 -> 200910, ... IMHO the second way is probably easier cause only the prjconf has to be changed. Disadvantage is that it probably would break some of the current builds but since there aren't that many Mandriva packages anyways on OBS and it's easy to fix that shouldn't be much of a problem. Last but not least the suggested numbering would be future proof so it were an unique issue. I also filed a bug regarding this: https://bugzilla.novell.com/show_bug.cgi?id=533587 Soo, what do you think, can we get that please fixed asap? Cheers, Stephan -- 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] No ARM builds running on Build Service
by David Greaves 24 Aug '09

24 Aug '09

It appears that the arm scheduler(?) is down. There are no arm builds, the queue is at 0/0 and the architecture isn't appearing in the monitor for new projects. Triggering a rebuild on an existing project is a no-op :( David -- "Don't worry, you'll be fine; I saw it work in a cartoon once..." -- 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] Setting Optflags in remote builds?
by Scott Cantor 24 Aug '09

24 Aug '09

Related to my question about getting -fPIC to work on Red Hat 5, I'm not having any success using osc meta prjconf to create a custom set of Optflag settings to use for non-local builds. I guess I interpreted the documentation as implying that that was the whole point of creating a custom build config. http://en.opensuse.org/Build_Service/prjconf Is there some kind of delay involved? An additional step to enable them? No way to do it at all? What I specifically did was check out my project, then run osc meta prjconf <project> -e and put just a set of Optflag lines into the file copied from the settings in the osc default config I found. If the build service was using these settings to begin with, I'd be ok, but it's using stale values. Anyway, then I triggered a rebuild of an affected package, but it's still using the same Optflags as before. -- Scott -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 3

[opensuse-buildservice] buildservice breaks a package
by Mathias Homann 24 Aug '09

24 Aug '09

Hi, i have this package which builds just fine locally, even when i check it with rpmlint, but on buildservice it breaks with this: WARNING: '/usr/lib/rpm/brp-desktop.data/suse-screensavers.menu' does not exist WARNING: '/usr/lib/rpm/brp-desktop.data/preferences-gnome.menu' does not exist WARNING: '/usr/lib/rpm/brp-desktop.data/applications-kmenuedit.menu' does not exist + /usr/lib/rpm/brp-rpath ERROR: RPATH "/usr/src/packages/BUILD/slitechat-1.4.0/doc" on /var/tmp/build-root-slitechat/usr/bin/slitechat is not allowed ERROR: RPATH "/usr/src/packages/BUILD/slitechat-1.4.0/3rdParty-2.0.0/lib/i686-linux" on /var/tmp/build-root-slitechat/usr/bin/slitechat is not allowed ERROR: RPATH "/usr/src/packages/BUILD/slitechat-1.4.0/GUI" on /var/tmp/build-root-slitechat/usr/bin/slitechat is not allowed ERROR: RPATH "/usr/src/packages/BUILD/slitechat-1.4.0/LLChatLib" on /var/tmp/build-root-slitechat/usr/bin/slitechat is not allowed ERROR: RPATH "/usr/src/packages/BUILD/slitechat-1.4.0/doc" on /var/tmp/build-root-slitechat/usr/bin/slitechat is not allowed ERROR: RPATH "/usr/src/packages/BUILD/slitechat-1.4.0/3rdParty-2.0.0/lib/i686-linux" on /var/tmp/build-root-slitechat/usr/bin/slitechat is not allowed ERROR: RPATH "/usr/src/packages/BUILD/slitechat-1.4.0/GUI" on /var/tmp/build-root-slitechat/usr/bin/slitechat is not allowed ERROR: RPATH "/usr/src/packages/BUILD/slitechat-1.4.0/LLChatLib" on /var/tmp/build-root-slitechat/usr/bin/slitechat is not allowed where did that come from? bye, MH -- Die unaufgeforderte Zusendung einer Werbemail an Privatleute verstößt gegen §1 UWG und §823 I BGB (Beschluß des LG Berlin vom 2.8.1998 Az: 16 O 201/98). Jede kommerzielle Nutzung der übermittelten persönlichen Daten sowie deren Weitergabe an Dritte ist ausdrücklich untersagt! -- 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] MonoOSC Help written :-)
by Petit Eric 23 Aug '09

23 Aug '09

Hi The MonoOSC starter guide is written, fill free to complete it : http://en.opensuse.org/MonoOSC/Guide The help is available from MonoOSC Main form (F1 key) and in setting form :-) -- Cordially. Small Eric Quotations of the days: --------------------------------------------------------------------------- I have no special talents. I am only passionately curious -- 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] build21 dead :(
by Christian 22 Aug '09

22 Aug '09

Hi, build21 is dead for 1 day now. Is there anybody who is taking care about it ? Kind Regards Chris -- 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] How does one share source file between packages?
by Paul Elliott 21 Aug '09

21 Aug '09

How does one share source files between packages? I am sorry if this is a dumb question, but I have read references to linking but nothing that would tell me how to do it. Thank 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 1

[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

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

19 Aug '09

I've just started attempting to use the build service for my project and got a report that one of the binaries contained a bunch of text relocations, indicating -fPIC wasn't used during the build. After some cross checking, I found that the usual checks in configure were being done, but that on two of the build platforms (RH5/CentOS5), the gcc/g++ checks were failing and it was omitting the flag. Both architectures were affected. I tested locally with CentOS 5 and confirmed that I get different (correct) results from my rpmbuild. I know there's no direct access to config.log, so it's a bit difficult to determine why this might be, but wondered if anybody had a clue or has seen this behavior in their projects? For reference the checks I'm referring to are: checking for gcc option to produce PIC... -fPIC checking if gcc PIC flag -fPIC works... no checking for g++ option to produce PIC... -fPIC checking if g++ PIC flag -fPIC works... no I saw nothing unexpected in my local config.log where the check passes, it's a typical gcc/g++ command. -- Scott -- 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] Re: [Mono-list] MonoOSC Help wanted :-)
by Petit Eric 18 Aug '09

18 Aug '09

2009/8/18 Oisín Grehan <oising(a)gmail.com>: > Is that OSC as in Open Sound Control? sorry, i don't understand your question, you mean : MonoOSC is Open source ? > > On Tue, Aug 18, 2009 at 6:47 AM, Petit Eric <surfzoid(a)gmail.com> wrote: >> >> Hi >> An user ask to an "quickstart guide", is there an MonoOSC user who >> want to write it ? >> >> https://sourceforge.net/tracker/index.php?func=detail&aid=2839338&group_id=… >> >> Unlucky, i really haven't got time and don't practice doc. >> >> -- >> Cordially. >> >> Small Eric Quotations of the days: >> >> --------------------------------------------------------------------------- >> I have no special talents. I am only passionately curious >> _______________________________________________ >> Mono-list maillist - Mono-list(a)lists.ximian.com >> http://lists.ximian.com/mailman/listinfo/mono-list > > > > -- > > --- > 404 signature missing > -- Cordially. Small Eric Quotations of the days: --------------------------------------------------------------------------- I have no special talents. I am only passionately curious -- 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] package publishing issues
by Cristian Rodríguez 18 Aug '09

18 Aug '09

Hi: The server:php and server:php:extensions repositories are taking a significant amount of time that varies between 3 days to weeks to get already built packages published to the download server, I was wondering how exactly the obs chooses what to publish and when, and if that is configurable .. let's say: I have target A in server:php and target B in server:php:extensions, B uses A for build and hence depends on it, If A rebuilds I want to have A and B published at the same time to avoid inconsistencies, is that possible ? -- 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] MonoOSC Help wanted :-)
by Petit Eric 18 Aug '09

18 Aug '09

Hi An user ask to an "quickstart guide", is there an MonoOSC user who want to write it ? https://sourceforge.net/tracker/index.php?func=detail&aid=2839338&group_id=… Unlucky, i really haven't got time and don't practice doc. -- Cordially. Small Eric Quotations of the days: --------------------------------------------------------------------------- I have no special talents. I am only passionately curious -- 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] Unowned directories question
by doiggl＠velocitynet.com.au 18 Aug '09

18 Aug '09

Hello To get past this Warning message I have gotten a workaround for it. (see workaround below) Warning message: bugzilla-3.4.1-14.1.noarch.rpm: directories not owned by a package: - /etc/httpd - /etc/httpd/conf.d - /usr/share/bugzilla/extensions - /usr/share/bugzilla/lib bugzilla-doc-3.4.1-14.1.noarch.rpm: directories not owned by a package: - /usr/share/bugzilla/docs bugzilla-doc-build-3.4.1-14.1.noarch.rpm: directories not owned by a package: - /usr/share/bugzilla/docs System halted. #WORKAROUND #---------- %if 0%{?suse_version} # With unowned dirs /etc/httpd/, the build will fail so own them ourselves %dir %{_sysconfdir}/etc/httpd %dir %{_sysconfdir}/etc/httpd/conf.d %dir %{_sysconfdir}/etc/httpd/conf.d/bugzilla.conf %endif Questions: Does the workaround look ok ?, and at what line should I place the code in the .specfile ? Specfile -> https://build.opensuse.org/package/view_file?file=bugzilla.spec&package=Bug… Thanks for the advice Glenn -- 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] Is this a bug in osc?
by Dave Plater 17 Aug '09

17 Aug '09

I removed a package from my build service project and home directory ( a .desktop file) and then found that it was necessary so I put it back in my local project directory. Then I performed an osc ci and it checked in three files that I had changed but failed to include the above mentioned package is this normal and I should manually upload new files or is this a bug? Regards Dave P -- 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] BUG: self-dependency in build problem on OBS
by David Greaves 17 Aug '09

17 Aug '09

If I want to build a deb package that depends on itself for building then it fails. I assumed it was being removed by build or osc but traced it to the API response. eg: https://api.opensuse.org/build/home:lbt:arm:cross/xUbuntu_9.04/armv5el/m4/_… https://api.opensuse.org/build/home:lbt:arm:cross/xUbuntu_9.04/armv5el/dpkg… Both m4 and dpkg-dev are build-essential The first (m4) package does not have m4 in the <bdep> list but has dpkg-dev The second (dpkg) package does not have dpkg-dev in the <bdep> list but has m4 (dpkg provides dpkg-dev of course) This bites when building any package in build-essential or any other package that self build-depends; they all need modifying to build on OBS. David -- "Don't worry, you'll be fine; I saw it work in a cartoon once..." -- 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] bs and ARM
by Peter Czanik 17 Aug '09

17 Aug '09

Hello, Finally I got a little time, so I'd like to try to compile a few packages for Debian ARM. Last time I worked with the BS, I used PPC and openSUSE 11.0. Now looking for info, how to get started BS for ARM. So, I got some questions: - which version to use if I want to compile for ARM? - http://en.opensuse.org/Build_Service/Build_Service_Installation_Tutorial only has instructions up to openSUSE 11.0. Does the same apply for 11.1? Is it the doc I should use for cross builds: http://en.opensuse.org/Build_Service/Concepts/CrossDevelopment ? - Can I compile for Debian Lenny? ( http://en.opensuse.org/Build_Service/Concepts/CrossDevelopment only mentions Etch ) Some packages are not included in Debian Lenny for ARM, which are available in Ubuntu and I'd try to recompile them for Debian... - is it already possible to boot openSUSE/ARM? Would be nice to see it running at least in Qemu... Bye, CzP -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 7

[opensuse-buildservice] RPM signing problem
by Cristian Morales Vega 16 Aug '09

16 Aug '09

For some days I have been receiving emails about failed builds. Now I'm looking into them and seems to be a problem signing packages in Factory: sign libglpng-devel-1.45-1.41.i586.rpm failed: 256 Any idea? -- 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] [osc] patch to support overlay filesystem - RFC
by Jan-Simon Möller 14 Aug '09

14 Aug '09

Hi ! During work on openSUSE@ARM I frequently wanted to change single files or add single files to the buildroot without recompiling a dependency package or adding the files to a dummy rpm. Thus here are 2 patches for osc and build which will do this: Take all files in the specified "overlay"-folder and copy them to the buildroot before actually starting the build. This can help especially in local development with osc build if you e.g. want to delpoy a custom debugger, a custom qemu-arm or even a patched file. Best, Jan-Simon Signed-off-by: Jan-Simon Möller <jansimon.moeller(a)opensuse.org> Index: build.py =================================================================== --- build.py (Revision 7845) +++ build.py (Arbeitskopie) @@ -511,6 +511,23 @@ vm_options, build_descr, buildargs) + # special handling for overlay + if opts.overlay: + myoverlay=os.path.abspath(opts.overlay) + if os.path.isdir(myoverlay): + cmd = '%s --root=%s --rpmlist=%s --dist=%s --overlay=%s --arch=%s %s %s %s' \ + % (config['build-cmd'], + config['build-root'], + rpmlist_file.name, + bc_file.name, + myoverlay, + bi.buildarch, + vm_options, + build_descr, + buildargs) + else: + print "ERROR: OVERLAY ("+myoverlay+") is no directory." + sys.exit(1) if config['su-wrapper'].startswith('su '): tmpl = '%s \'%s\'' Index: commandline.py =================================================================== --- commandline.py (Revision 7845) +++ commandline.py (Arbeitskopie) @@ -2238,6 +2238,8 @@ @cmdln.option('--clean', action='store_true', help='Delete old build root before initializing it') + @cmdln.option('--overlay', metavar='OVERLAY', + help='Copy overlay filesystem to buildroot after installing all RPMs. This must be a valid directory (e.g. /tmp/overlay-root). The files are copied as-is.') @cmdln.option('--no-changelog', action='store_true', help='don\'t update the package changelog from a changes file') @cmdln.option('--noinit', '--no-init', action='store_true', Index: build =================================================================== --- build (Revision 7845) +++ build (Arbeitskopie) @@ -63,6 +63,7 @@ INCARNATION= DISTURL= CHANGETARGET= +OVERLAY= export PATH=$BUILD_DIR:/sbin:/usr/sbin:$PATH @@ -157,6 +158,9 @@ --icecream N use N parallel build jobs with icecream + --overlay OVERLAY + Copy overlay filesystem to buildroot after installing + all RPMs. This must be a valid directory. --debug enable creation of a debuginfo package @@ -664,6 +668,10 @@ *-changelog) CHANGELOG=true ;; + --overlay) + OVERLAY=$ARG + shift + ;; -*) echo Unknown Option "$PARAM". Exit. cleanup_and_exit 1 @@ -1332,6 +1340,17 @@ BUILD_SUCCEEDED=false + if test -n "$OVERLAY" ; then + if test -d "$OVERLAY"; then + pushd $OVERLAY + echo "Copying overlay to BUILD_ROOT" + tar -cpf - . | (cd $BUILD_ROOT ; tar -xf -) + popd + else + echo "OVERLAY ($OVERLAY) is no directory - skipping" + fi + fi + if test "$BUILDTYPE" = spec ; then test -z "$BUILD_RPM_BUILD_STAGE" && BUILD_RPM_BUILD_STAGE=-ba -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

4 13

[opensuse-buildservice] Can't commit read-only file
by Luke Imhoff 14 Aug '09

14 Aug '09

I was trying to importsrcpkg the automake.src.rpm from SLES 10 to rebuild it for SLES 11 when I came upon a bug. The tarball is unpacked as readonly: osc importsrcpkg automake-1.9.6-13.2.src.rpm A automake No files were committed to the server. Please commit them manually. Package 'automake' only imported locally % cd automake/ % ls -la automake-1.9.6.tar.bz2 -r--r--r-- 1 luke criemp 765505 2009-08-14 09:24 automake-1.9.6.tar.bz2 If I then try to commit the files: % osc addremove % osc ci -m "SLES 10 automake" ... Transmitting file data ..[Errno 13] Permission denied: '/notbackedup/users/luke/obs/devel:tools:building/automake/.osc/automake-1.9.6.tar.bz2' The file cache under .osc has automake-1.9.6.tar.bz2 as read-only also, so it can't be written when the mod is submitted to the server. -- 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] Does osc modify gcc build flags?
by Dave Plater 13 Aug '09

13 Aug '09

Hi, I have a package that when building with osc gives a warning about uninitialized variables being used but rpmbuild doesn't. Is there a way to receive these warnings using make? Regards Dave P -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

6 14

[opensuse-buildservice] Re: [opensuse-programming] What's the best way to cure uninitialized variables?
by Dave Plater 13 Aug '09

13 Aug '09

On 08/08/2009 04:11 PM, Philipp Thomas wrote: > On Sat, 08 Aug 2009 15:01:42 +0200, you wrote: > > >> The warnings come from osc, I don't get these warnings when I build the >> same package using kdevelop3. >> > The warnings definitely come from the compiler when passed the right > Options, which is mainly -Wall! But as they are only warnings the > compiler will succeed in compiling. OSC scans the comipler output and > turns some warnings into fatal errors because the past has shown us > that these lead to broken programs. > > If you carefully log the compiler output[1] and scan it afterwards > you'll see all those warnings the compiler produced. > > Philipp > > 1) My favourite for logging when not using 'osc build' is is defining > a simple shell function mk() { make "$@" 2>&1 | tee mlog; }. Now > you simply call mk (possibly whith additional options for make) and > afterwards have a complete log. > > Well I must admit I feel like an idiot, I was setting C flags in cmake and not the CXX flags (at least I'll never make the same mistake). I can now get the exact same messages to display in kdevelop3 as I receive from osc, without the summary of course. Thanks very much for your patience with me. Regards Dave P -- 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] Atomic package set updates
by Luke Imhoff 13 Aug '09

13 Aug '09

Here's the use case we have for our developers: 1) The kernel gets a change by a checkin of kernel-source by Alice. This triggers a build of kernel-FLAVORs and kernel-syms as they are all linked to the kernel-source package (and any indirect dependents). 2) kernel-source finishes building 3) kernel-source is available for build use now 4) kernel-syms hasn't finished building as it's wating on kernel-FLAVORs (which take longer than kernel-source) 5) Bob tries to build foo-kmp, which BuildRequires kernel-source and kernel-syms, but osc buildinfo says expansion error because kernel-syms cannot find the old version of kernel-source. kernel-syms has Requires: kernel-source = %{version}-%{release} to make sure they tightly match. Now we could get around this by making kernel-syms not dependent on a strict version-release match with kernel-source, but then the kernel-syms would be incorrect if the developer tried to build against it. So, is there someway to not release the changes in kernel-source that affect the buildinfo to developers doing local builds with 'osc build' until after all builds triggered by the checkin of kernel-source finishes? -- 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] kiwi >= 3.6 in obs?
by Carsten Hoeger 12 Aug '09

12 Aug '09

Hi, is it planned to have kiwi >=3.6 in obs to support images using custom branding using <preferences> [...] <boot-theme>FOO</boot-theme> [...] </preferences> -- With best regards, Carsten Hoeger

2 2

[opensuse-buildservice] osc rq list -M -s accepted doesn't show all requests
by Jan-Simon Möller 12 Aug '09

12 Aug '09

Hi ! For documentation I want to list all my accepted/declined/revoked/... requests, but osc rq list -M -s accepted doesn't show all accepted requests . Most of the 16xxx range is missing (also not in the other states). And I'm sure, I submitted stuff ;) . So the question is: are these requests lost or can I query for them somehow using my loginname ? Best, Jan-Simon -- 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] Slightly Off-Topic: How to create bootsplash logo.mng?
by Carsten Hoeger 12 Aug '09

12 Aug '09

Hi, I know, it's off-topic, but I was unable to find any _clear_ instruction on how to create bootsplash logo.mng files. Some e.g. state, that a special version of convert must be used, or sililar... Does anybody have a pointer on how to exactly do that on openSUSE (11.1)? -- With best regards, Carsten Hoeger

1 0

[opensuse-buildservice] GSoC - summary of this week's meeting
by Marcus Hüwe 12 Aug '09

12 Aug '09

Hi, here's a summary of this week's meeting: Since the rails oauth-plugin[1] got support for oauth 1.0a I started to migrate the frontend so that it also supports 1.0a. This was a nice exercise to learn how certain things are done with rails. Additionally I did some code cleanups, bugfixing etc. The goal for this week is more testing, bugfixing and writing a user documentation. Marcus [1] http://code.google.com/p/oauth-plugin -- 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] Notifications (was: Re: [opensuse-packaging] New packages for factory)
by Peter Poeml 12 Aug '09

12 Aug '09

On Mon, Aug 10, 2009 at 02:32:04 +0200, Stephan Kulow wrote: > On Monday 10 August 2009 16:45:33 Dominique Leuenberger wrote: > > I think the minimum 'feedback' we need finally to get working is hermes > > acting properly on SR creation / accepting / revoking / declining. > > > > Not having any feedback (good or bad) is unfriendly practice. Of course it > > should not be that besides a proper osc rq accept -m "Thanks for this > > wonderful package. It has just been accepted to Factory and will appear in > > the next sync" you have to do any additional steps. > > > > Unfortunately, the above does not create a mail to the person that > > initiated the osc sr create > > request. > > Agreed. Some get mails, some don't. This is something that needs to be fixed > in the build service asap. Do you get no mails at all or just some are > missing? Because I do not miss any mails (the opposite is true :) I get commit mails for some projects (Subversion), and not for some others (devel:languages:python). The "_mypackages" filter in hermes doesn't work correctly, I guess. But the largest blocker for me is that I don't get any commit diffs at all. (Not implemented.) How can I track the work of others, and review it, and how can they follow on what I do, without? So far, I have to rely on good commit messages, or dig out the changes in an elaborate manual process. Peter -- "WARNING: This bug is visible to non-employees. Please be respectful!" SUSE LINUX Products GmbH Research & Development

10 20

[opensuse-buildservice] how to find out why a package is excluded from build?
by Carsten Hoeger 11 Aug '09

11 Aug '09

Hi, I copied my branding package from the Education project: https://build.opensuse.org/package/show?package=gfxboot-branding-ox&project… It builds locally now using osc build but issues some warnings, though: RPMLINT report: =============== gfxboot-branding-ox.noarch: W: no-changelogname-tag gfxboot-branding-ox.src: W: no-changelogname-tag There is no %changelog tag in your spec file. To insert it, just insert a '%changelog' in your spec file and rebuild it. gfxboot-branding-ox.noarch: W: suse-branding-missing-conflicts otherproviders(gfxboot-branding) Any branding flavor package that provides the generic branding must also conflict with all other branding packages via a special otherproviders() gfxboot-branding-ox.noarch: W: suse-branding-supplement-missing packageand(gfxboot:branding-ox) branding packages should provide a supplemnent in the form Supplements: packageand(basepackage:branding-<flavour>) gfxboot-branding-ox.noarch: W: suse-branding-wrong-branding-supplement packageand(branding-ox:gfxboot) 2 packages and 0 specfiles checked; 0 errors, 5 warnings. mobile finished "build gfxboot-branding-ox.spec" at Mon Aug 10 18:02:25 CEST 2009. I've no idea why it insists on missing the %changelog tag, because it is really there. The other warnings also appear in the buildlog of the gfxboot package from Education, so I assume that I can just ignore them. OBS just silently excludes that package. Any idea? -- With best regards, Carsten Hoeger

3 6