September 2008 - openSUSE Build Service

[opensuse-buildservice] openSUSE:Tools:Devel: New snapshots for OBS with/without cross-build
by Martin Mohring 27 Sep '08

27 Sep '08

Hi, I am happy to announce another snapshot with current ( svn -r 5171 ) svn trunk for OBS. As always, there are two versions: - openSUSE:Tools:Devel/obs-all-svn - SVN snapshot of the normal OBS - openSUSE:Tools:Devel/obs-all-cross - SVN snapshot of OBS with cross-build - openSUSE:Tools:Devel/qemu-svn - SVN snapshot of the required QEMU used in cross-build Now I have also added sh4 and ppc cross-builds, although current qemu is not able to run the generated cross-build environments. I have also been successfull in adding Debian:Etch/ppc to OBS for testing ppc cross-build. PPC users I can currently recomment only to use ppc native works, they really work correctly. In order to install qemu with preinstall, qemu-svn now has a baselibs.conf to generate .arm.rpm, .ppc.rpm, .sh4.rpm packages that can be installed from prjconf of a project then. Something similiar is missing for the debian packaging, dont know atm how to do that. Michael has now put some first parts of the worker infrastructure in place (backend), so workers can report resources before jobs are scheduled. This will in the future also be used in cross-build. I have reduced the patch to remaining changes in osc/build, OBS worker/dispatcher. They are compatible to normal .deb and .rpm operation in case of not using cross-build but native build. Other is submitted to OBS svn. I plan to put in some automatic testing inside maybe openSUSE:Tools:Testing. Dirk Müller has made no progress jet in getting Maemo:4.1 running, not all the binaries seem to be available in .deb package format (some seem to come as a chroot snapshot preinstalled), we have to clear that out with Maemo people. Special thanks to Jan-Simon Möller for creating the .deb packaging of qemu-svn, and for currently working on kiwi support also two work with .deb and with cross-build. Martin -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 0

[opensuse-buildservice] putting .so files explicitly in /usr/lib and not in /usr/lib64
by Christopher Lang 26 Sep '08

26 Sep '08

Hi, in one of my packages that I am building for openSuse 10.2/x86_64 I have some custom .so files that I want to put explicitely in /usr/lib. I am installing them there, but the build server is complaining (and the build fails): /var/tmp/some-file-build/usr/lib/libSome.so: file format elf64-x86-64 /var/tmp/some-file-build/usr/lib/libSome.so: should be in */lib64 Is there a way in the spec file %files section to handle that particular situation - or is there a way to make the build server accept certain .so files in /usr/lib even for x86_64 builds? many thanks Chris http://www.acurana.de/ --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

4 7

[opensuse-buildservice] how to verify and fix broken links?
by Ludwig Nussel 26 Sep '08

26 Sep '08

Hi, Suppose I have a package linked from another project with patches (project*.diff) on top of it. Now the other package is updated and the patches no longer apply. osc rdiff doesn't work because it can't apply the patches either. How do I verify how and which of my changes got applied to the linked package? cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.de/ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

6 19

[opensuse-buildservice] Own build service: Error adding files to package
by Ulf 25 Sep '08

25 Sep '08

Hi, I tried to setup my own build service on SLES10 SP2 64bit server. OBS-1.0.0-4 Everything works fine so far. But if i try to add files to a package (local file), I' ll get this error message. Any ideas? OpenSUSE Webclient Error: Error Details: Errorcode: unknown Message: uninitialized constant ApplicationHelper::EXTERNAL_FRONTEND_HOST Exception from Webclient: ActionView::TemplateError: uninitialized constant ApplicationHelper::EXTERNAL_FRONTEND_HOST Stack Trace: On line #23 of package/_files.rhtml 20: <%= link_to("[Show]", :action => :view_file, :project => @project, 21: :package => @package, :file => file[:name] ) %> 22: </td> 23: <td><%= link_to "[Download]", file_url( @project, @package, file[:name] ) %></td> 24: <td><%= link_to "[Remove]", {:action => :remove_file, :project => @project, 25: :package => @package, :filename => file[:name]}, 26: {:confirm => "Really remove file '#{file[:name]}'?" }%></td> /usr/lib64/ruby/gems/1.8/gems/activesupport-2.0.2/lib/active_support/dependencies.rb:263:in `load_missing_constant' /usr/lib64/ruby/gems/1.8/gems/activesupport-2.0.2/lib/active_support/dependencies.rb:453:in `const_missing' app/helpers/application_helper.rb:58:in `get_frontend_url_for' app/helpers/package_helper.rb:9:in `file_url' app/views/package/_files.rhtml:23:in `_run_erb_47app47views47package47_files46rhtml' app/views/package/_files.rhtml:11:in `each' app/views/package/_files.rhtml:11:in `_run_erb_47app47views47package47_files46rhtml' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_view/base.rb:637:in `send' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_view/base.rb:637:in `compile_and_render_template' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_view/base.rb:365:in `render_template' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_view/base.rb:316:in `render_file' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_view/base.rb:331:in `render' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_view/partials.rb:120:in `render_partial' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_view/base.rb:352:in `render' app/views/package/show.rhtml:39:in `_run_erb_47app47views47package47show46rhtml' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_view/base.rb:637:in `send' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_view/base.rb:637:in `compile_and_render_template' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_view/base.rb:365:in `render_template' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_view/base.rb:316:in `render_file' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/base.rb:1100:in `render_for_file' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/base.rb:836:in `render_with_no_layout' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/layout.rb:262:in `render_without_benchmark' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/benchmarking.rb:51:in `render' /usr/lib64/ruby/1.8/benchmark.rb:293:in `measure' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/benchmarking.rb:51:in `render' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/base.rb:1153:in `default_render' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/base.rb:1159:in `perform_action_without_filters' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/filters.rb:697:in `call_filters' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/filters.rb:689:in `perform_action_without_benchmark' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/benchmarking.rb:68:in `perform_action_without_rescue' /usr/lib64/ruby/1.8/benchmark.rb:293:in `measure' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/benchmarking.rb:68:in `perform_action_without_rescue' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/rescue.rb:199:in `perform_action' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/base.rb:524:in `send' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/base.rb:524:in `process_without_filters' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/filters.rb:685:in `process_without_session_management_support' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/session_management.rb:123:in `process' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/base.rb:388:in `process' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/dispatcher.rb:171:in `handle_request' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/dispatcher.rb:115:in `dispatch' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/dispatcher.rb:126:in `dispatch_cgi' /usr/lib64/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/dispatcher.rb:9:in `dispatch' /usr/lib64/ruby/gems/1.8/gems/rails-2.0.2/lib/fcgi_handler.rb:101:in `process_request' /usr/lib64/ruby/gems/1.8/gems/rails-2.0.2/lib/fcgi_handler.rb:149:in `with_signal_handler' /usr/lib64/ruby/gems/1.8/gems/rails-2.0.2/lib/fcgi_handler.rb:99:in `process_request' /usr/lib64/ruby/gems/1.8/gems/rails-2.0.2/lib/fcgi_handler.rb:77:in `process_each_request' /usr/lib64/ruby/vendor_ruby/1.8/fcgi.rb:612:in `each_cgi' /usr/lib64/ruby/vendor_ruby/1.8/fcgi.rb:609:in `each' /usr/lib64/ruby/vendor_ruby/1.8/fcgi.rb:609:in `each_cgi' /usr/lib64/ruby/gems/1.8/gems/rails-2.0.2/lib/fcgi_handler.rb:76:in `process_each_request' /usr/lib64/ruby/gems/1.8/gems/rails-2.0.2/lib/fcgi_handler.rb:50:in `process!' /usr/lib64/ruby/gems/1.8/gems/rails-2.0.2/lib/fcgi_handler.rb:24:in `process!' public/dispatch.fcgi:24 Best wishes, Ulf -- Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger --------------------------------------------------------------------- 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] Ignoring files in a osc checkout
by Vincent Untz 25 Sep '08

25 Sep '08

Hi, I wonder if there's any way to have some files ignored by osc in a directory that is a project or package checkout. Example: $ osc co GNOME:Factory libwnck [...] $ cd GNOME:Factory/libwnck $ touch ignore-this $ osc status ? ignore-this And I don't want to have ignore-this here. It's not that much about appearing in 'osc status' than the fact that I don't want this file to be commitable. There's a hack which works with osc. If I create a plugin and do: exclude_stuff.append('ignore-this') then the file will be ignored. However, this will only work with clients that are using the osc python modules, and therefore it's not a perfect solution. So, back to my question :-) Is there some local metadata that can be set for this? If no at the moment, is this something that would be desirable? Vincent -- Les gens heureux ne sont pas pressés. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 1

[opensuse-buildservice] [PATCH] optionally show tracebacks upon (many) osc errors
by Michael Wolf 25 Sep '08

25 Sep '08

Yo Attached is a patch that shows tracebacks upon many osc errors. It's probably not complete. The motivation is that when working on plugins (and, I assume, osc itself), messages you get from the following except AttributeError, e: print >>sys.stderr, e return 1 aren't very helpful, because there's little indication where the problem lies. But when I add show-python-tracebacks = true to my ~/.oscrc, I can see exactly where and how I'm screwing up -- pretty useful. I have only been running with this patch for about an hour, but it seems to work pretty well so far. Michael.

3 2

[opensuse-buildservice] [PATCH] teach osc to run post-command hooks
by Michael Wolf 25 Sep '08

25 Sep '08

Yo Attached is a patch that enables osc to run post-command hooks. To use it, create ~/.osc/hooks. Inside that directory, create a directory for each command you'd like to hook. For instance, ~/.osc/hooks/build/. Everything in that directory will be run when the command completes. It tries to ignore backup files and the like, but I surely missed a few created by editors I don't use. :) A script in ~/.osc/hooks/build might look like: #!/bin/sh notify-send "osc build finished" but of course they can be as simple or complicated as you wish. Of course, they need to be executable. Finally, directories need to be named for real command names, so, for instance, create a hook in ~/.osc/hooks/checkout, even if you actually always run "osc co ...". I've been running with this patch for about two weeks and it seems to work ok. It would be cool to be able to send arguments to the hooks, but currently the patch doesn't do that. Michael.

4 3

[opensuse-buildservice] Hermes notification for addition of a package
by Vincent Untz 25 Sep '08

25 Sep '08

Hi, Is there a way with hermes to be notified of the addition of a package? It's possible to be notified of deletion (OBS_SRCSRV_DELETE_PACKAGE) but I don't see anything for addition... Thanks, Vincent -- Les gens heureux ne sont pas pressés. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 1

Re: [opensuse-buildservice] Own build service: Error adding files to package
by Ulf 24 Sep '08

24 Sep '08

Hi Carsten, I added these lines to /srv/www/obs/webclient/config/environments/production_slave.rb EXTERNAL_FRONTEND_HOST = "192.168.100.223" EXTERNAL_FRONTEND_PORT = 80 EXTERNAL_FRONTEND_PROTOCOL = 'http' Now I got this error message: Error Details: Errorcode: unknown Message: wrong constant name 192.168.100.223 Exception from Webclient: ActionView::TemplateError: wrong constant name 192.168.100.223 Any new idea? I' also tried the VMware Virtual Appliance (http://www.vmware.com/appliances/directory/924) but the link points to nowhere. Best wishes, Ulf -- Ist Ihr Browser Vista-kompatibel? Jetzt die neuesten Browser-Versionen downloaden: http://www.gmx.net/de/go/browser --------------------------------------------------------------------- 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] Automatically update of OBS packages on SuSE
by Carsten Gerlach 23 Sep '08

23 Sep '08

Hi list readers, what do I have to do, that SuSE 11.0 realises that there is a new version of my package on my home repository? I added this repository already to the SuSE online repository and if I start yast manually and have a look to updates, then I find them. But automatically this dosn't work. Is the problem in my spec file or do I have to change something in the SuSE settings? You find the spec file here: https://build.opensuse.org/package/show?package=nted&project=home%3Adaswald… Thank you for any hint in which direction I have to look. Greetings, Carsten -- Hier ist mein öffentlicher GPG-Schlüssel: http://daswaldhorn.funpic.de/gpg.html ========================================= www.stopptdievorratsdatenspeicherung.de

4 4