March 2007 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] Project/Package Messages
by Pavol Rusnak 27 Mar '07

27 Mar '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello all! My proposal is to add messages similar to Status messages shown on Build Service Status page to every project/package page. Any BuildService user can add message, but only project/package maintainers can set special "Private" flag. When this flag is set, message is only shown to other maintainers of project/package (it is not publicly visible to everyone). Messages from maintainers can also be highlighted with color and/or icon. This feature would help to coordinate maintainers of larger projects and also allow simple and quick feedback from users (when OBS will be open for everyone). I know that this functionality can be achieved by using emails and I'm aware of some drawbacks that this feature might bring (harder maintenance of OBS, larger database overhead and size), but I still think simple internal messaging system is worth considering. What do YOU think? - -- Best Regards / S pozdravom, Pavol RUSNAK SUSE LINUX, s.r.o Package Maintainer Lihovarska 1060/12 PGP 0xA6917144 19000 Praha 9, CR prusnak[at]suse.cz http://www.suse.cz -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFGCTgQASE5C6aRcUQRAndLAJ428Cj1WkfQC1oMN4FuXdwh9vQ19gCg0oMn XnGv27xBeaEYJmDNfy6xWZk= =McZo -----END PGP SIGNATURE----- --------------------------------------------------------------------- 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] not owning a project
by Jordi Massaguer i Pla 27 Mar '07

27 Mar '07

Hello, I already have a personal account at the BuildService. However, I am worried about what would happen if I do not want/I am not allowed to mantain a package I create there. Let's look into a more specific example. I am working for a company A. A wants to publish some packages using the BuildService (great!), (this packages are owned by the company). Then, someone else in the company gets into the project and goes on with the coding of that package. It that packages was into my account, how can the new person work on that? Maybe we should have asked for a "company account" and share the password between me and the new developer? greetings, jordi --------------------------------------------------------------------- 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] /srv/obs/ subdirs on different partitions
by Michal Marek 27 Mar '07

27 Mar '07

Hi, it took me >1 hour to figure out what's wrong. The worker successfully built the rpm, but it didn't show up in the :full directory and 'osc log' still reported 'building'. The problem was that I created /srv/obs/build as a symlink to a larger partition, but the repserver didn't expect that and tried to link files fron .../build to .../jobs and didn't abort when this didn't work. See attached patch. In case the link() is just a performance optimization (the code doesn't relly on the two files being links), it would be a nice feature to fallback to File::Copy :) But aborting with a meaningful error message is IMO sufficient. Michal

2 1

[opensuse-buildservice] project removal request
by Wolfgang Rosenauer 27 Mar '07

27 Mar '07

Hi, would anyone please remove the mozilla:experimental repository. It was never used but replaced by mozilla:beta Thanks, Wolfgang --------------------------------------------------------------------- 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] wundering what --clean or --noinit are going to do?
by Richard Bos 27 Mar '07

27 Mar '07

/ME wundering what --clean or --noinit are going to do: osc help build openSUSE_Factory i586 gramps.spec build: build a package on your local machine You need to call the command inside a package directory. usage: 1. osc build <platform> <arch> <specfile> [--clean|--noinit] 2. BUILD_DIST=... osc build <specfile> [--clean|--noinit] where BUILD_DIST equals <platform>-<arch> What is going to be cleaned? The package cache, build directory or the install directory or just all? --noinit? What is it going to do? -- Richard Bos We are borrowing the world of our children, It is not inherited from our parents. --------------------------------------------------------------------- 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 system/server problem for openSUSE_Factory x86_64
by Richard Bos 27 Mar '07

27 Mar '07

Just for the record (for my package gramps-beta): Wrote: /usr/src/packages/SRPMS/gramps-2.2.6-2.1.src.rpm Wrote: /usr/src/packages/RPMS/i586/gramps-2.2.6-2.1.i586.rpm Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.30168 + umask 022 + cd /usr/src/packages/BUILD + cd gramps-2.2.6 + exit 0 mount: can't find / in /etc/fstab or /etc/mtab md: stopping all md devices. xenbus_dev_shutdown: device/console/0: Initialising != Connected, skipping System halted. Error: can't get 'https://api.opensuse.org/result/home:rbos/openSUSE_Factory/gramps-beta/i586…' HTTP Error 500: Internal Server Error Debugging output follows. url: https://api.opensuse.org/result/home:rbos/openSUSE_Factory/gramps-beta/i586… response: <?xml version="1.0" encoding="UTF-8"?> <status code="uncaught_exception"> <summary>execution expired</summary> <details></details> <exception> <type>Timeout::Error</type> <message>execution expired</message> <backtrace> <line>/usr/lib64/ruby/1.8/timeout.rb:54:in `rbuf_fill'</line> <line>/usr/lib64/ruby/1.8/timeout.rb:56:in `timeout'</line> <line>/usr/lib64/ruby/1.8/timeout.rb:76:in `timeout'</line> <line>/usr/lib64/ruby/1.8/net/protocol.rb:132:in `rbuf_fill'</line> <line>/usr/lib64/ruby/1.8/net/protocol.rb:116:in `readuntil'</line> <line>/usr/lib64/ruby/1.8/net/protocol.rb:126:in `readline'</line> <line>/usr/lib64/ruby/1.8/net/http.rb:2195:in `read_chunked'</line> <line>/usr/lib64/ruby/1.8/net/http.rb:2175:in `read_body_0'</line> <line>/usr/lib64/ruby/1.8/net/http.rb:2141:in `read_body'</line> <line>/usr/lib64/ruby/1.8/net/http.rb:2166:in `body'</line> <line>/usr/lib64/ruby/1.8/net/http.rb:2105:in `reading_body'</line> <line>/usr/lib64/ruby/1.8/net/http.rb:1048:in `request'</line> <line>/usr/lib64/ruby/1.8/net/http.rb:944:in `request_get'</line> <line>/usr/lib64/ruby/1.8/net/http.rb:375:in `get_response'</line> <line>/usr/lib64/ruby/1.8/net/http.rb:545:in `start'</line> <line>/usr/lib64/ruby/1.8/net/http.rb:374:in `get_response'</line> <line>/srv/www/opensuse/frontend/current/public/../config/../lib/opensuse/backend.rb:116:in `do_get'</line> <line>/srv/www/opensuse/frontend/current/public/../config/../lib/opensuse/backend.rb:75:in `get_log_chunk'</line> <line>/srv/www/opensuse/frontend/current/public/../config/../app/controllers/result_controller.rb:130:in `log'</line> <line>/usr/lib64/ruby/gems/1.8/gems/actionpack-1.12.3/lib/action_controller/base.rb:910:in `perform_action_without_filters'</line> <line>/usr/lib64/ruby/gems/1.8/gems/actionpack-1.12.3/lib/action_controller/filters.rb:368:in `perform_action_without_benchmark'</line> <line>/usr/lib64/ruby/gems/1.8/gems/actionpack-1.12.3/lib/action_controller/benchmarking.rb:69:in `perform_action_without_rescue'</line> <line>/usr/lib64/ruby/1.8/benchmark.rb:293:in `measure'</line> <line>/usr/lib64/ruby/gems/1.8/gems/actionpack-1.12.3/lib/action_controller/benchmarking.rb:69:in `perform_action_without_rescue'</line> <line>/usr/lib64/ruby/gems/1.8/gems/actionpack-1.12.3/lib/action_controller/rescue.rb:82:in `perform_action'</line> <line>/usr/lib64/ruby/gems/1.8/gems/actionpack-1.12.3/lib/action_controller/base.rb:381:in `process_without_filters'</line> <line>/usr/lib64/ruby/gems/1.8/gems/actionpack-1.12.3/lib/action_controller/filters.rb:377:in `process_without_session_management_support'</line> <line>/usr/lib64/ruby/gems/1.8/gems/actionpack-1.12.3/lib/action_controller/session_management.rb:117:in `process'</line> <line>/usr/lib64/ruby/gems/1.8/gems/rails-1.1.4/lib/dispatcher.rb:38:in `dispatch'</line> <line>/usr/lib64/ruby/gems/1.8/gems/rails-1.1.4/lib/fcgi_handler.rb:150:in `process_request'</line> <line>/usr/lib64/ruby/gems/1.8/gems/rails-1.1.4/lib/fcgi_handler.rb:54:in `process!'</line> <line>/usr/lib64/ruby/1.8/fcgi.rb:612:in `each_cgi'</line> <line>/usr/lib64/ruby/1.8/fcgi.rb:609:in `each_cgi'</line> <line>/usr/lib64/ruby/gems/1.8/gems/rails-1.1.4/lib/fcgi_handler.rb:53:in `process!'</line> <line>/usr/lib64/ruby/gems/1.8/gems/rails-1.1.4/lib/fcgi_handler.rb:23:in `process!'</line> <line>/srv/www/opensuse/frontend/current/public/dispatch.fcgi:24</line> </backtrace> </exception> </status> While restarting the build the following error is reported: home:rbos/gramps-beta> osc log openSUSE_Factory x86_64 build08 started "build gramps.spec" at Sun Mar 25 16:46:32 UTC 2007. Building 'gramps-beta' for project 'home:rbos' target 'openSUSE_Factory' arch 'x86_64' srcmd5 '8a7411e86ba6ac3f924cb3062abd4865' Using BUILD_ROOT=/abuild/root_1/.mount Using BUILD_ARCH=x86_64:i686:i586:i486:i386 Doing XEN build in /abuild/root_1/root processing specfile /abuild/root_1/.build-srcdir/gramps.spec... running changelog2spec --target rpm --file /abuild/root_1/.build-srcdir/gramps.spec init_buildsystem --rpmlist /abuild/root_1/.rpmlist gramps.spec ... preinstalling aaa_base... etc preinstalling perl... preinstalling libvolume_id... copying packages... reordering...done Error: Device 769 (vbd) could not be connected. Hotplug scripts not working. Using config file "/var/run/bsworker_1/build/xen.conf". -- Richard Bos We are borrowing the world of our children, It is not inherited from our parents. --------------------------------------------------------------------- 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] repo vs platform
by Richard Bos 26 Mar '07

26 Mar '07

Why this the distribution name sometimes called repo and in other commands platform. See below. In the 'osc help log' output it's called platform, shouldn't repo be more consistent with other commands and with the webinterface too? # osc help rebuildpac rebuildpac: Causes a package to be rebuilt usage: osc rebuildpac <project> <package> [<repo> [<arch>]] With the optional <repo> and <arch> arguments, the rebuild can be limited to a certain repository or architecture. Note that it is normally NOT needed to kick off rebuilds like this, because they principally happen in a fully automatic way, triggered by source check-ins. In particular, the order in which packages are built is handled by the build service. # osc log missing argument log: Shows the log file from a package (you need to be inside a package directory) usage: osc log <platform> <arch> To find out <platform> and <arch>, you can use 'osc results' -- Richard Bos Without a home the journey is endless --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 5

[opensuse-buildservice] openSUSE:dropped?
by Michal Marek 23 Mar '07

23 Mar '07

Hi, would there be interest for a repository with packages dropped from the distribution? My idea is a readonly repository with no build targets that packagers could link to (like openSUSE:factory), patch if needed and rebuild for newer distributions. I would take care of updating the repository in case of security updates. Opinions? thanks, Michal --------------------------------------------------------------------- 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] HTTP Error 500: Internal Server Error uncaught_exception execution expired
by Cristian Rodriguez R. 22 Mar '07

22 Mar '07

While attempting to build a very large C++ code (that takes literally hours to build here) I get the following error from the buildservice. Error: can't get 'https://api.opensuse.org/result/home:elvigia/openSUSE_10.2/crystalspace/x86…' HTTP Error 500: Internal Server Error Debugging output follows. url: https://api.opensuse.org/result/home:elvigia/openSUSE_10.2/crystalspace/x86… response: <?xml version="1.0" encoding="UTF-8"?> <status code="uncaught_exception"> <summary>execution expired</summary> <details></details> <exception> <type>Timeout::Error</type> <message>execution expired</message> <backtrace> <line>/usr/lib64/ruby/1.8/timeout.rb:54:in `rbuf_fill'</line> <line>/usr/lib64/ruby/1.8/timeout.rb:56:in `timeout'</line> <line>/usr/lib64/ruby/1.8/timeout.rb:76:in `timeout'</line> <line>/usr/lib64/ruby/1.8/net/protocol.rb:132:in `rbuf_fill'</line> <line>/usr/lib64/ruby/1.8/net/protocol.rb:116:in `readuntil'</line> <line>/usr/lib64/ruby/1.8/net/protocol.rb:126:in `readline'</line> <line>/usr/lib64/ruby/1.8/net/http.rb:2195:in `read_chunked'</line> <line>/usr/lib64/ruby/1.8/net/http.rb:2175:in `read_body_0'</line> <line>/usr/lib64/ruby/1.8/net/http.rb:2141:in `read_body'</line> <line>/usr/lib64/ruby/1.8/net/http.rb:2166:in `body'</line> <line>/usr/lib64/ruby/1.8/net/http.rb:2105:in `reading_body'</line> <line>/usr/lib64/ruby/1.8/net/http.rb:1048:in `request'</line> <line>/usr/lib64/ruby/1.8/net/http.rb:944:in `request_get'</line> <line>/usr/lib64/ruby/1.8/net/http.rb:375:in `get_response'</line> <line>/usr/lib64/ruby/1.8/net/http.rb:545:in `start'</line> <line>/usr/lib64/ruby/1.8/net/http.rb:374:in `get_response'</line> <line>/srv/www/opensuse/frontend/current/public/../config/../lib/opensuse/backend.rb:116:in `do_get'</line> <line>/srv/www/opensuse/frontend/current/public/../config/../lib/opensuse/backend.rb:75:in `get_log_chunk'</line> <line>/srv/www/opensuse/frontend/current/public/../config/../app/controllers/result_controller.rb:130:in `log'</line> <line>/usr/lib64/ruby/gems/1.8/gems/actionpack-1.12.3/lib/action_controller/base.rb:910:in `perform_action_without_filters'</line> <line>/usr/lib64/ruby/gems/1.8/gems/actionpack-1.12.3/lib/action_controller/filters.rb:368:in `perform_action_without_benchmark'</line> <line>/usr/lib64/ruby/gems/1.8/gems/actionpack-1.12.3/lib/action_controller/benchmarking.rb:69:in `perform_action_without_rescue'</line> <line>/usr/lib64/ruby/1.8/benchmark.rb:293:in `measure'</line> <line>/usr/lib64/ruby/gems/1.8/gems/actionpack-1.12.3/lib/action_controller/benchmarking.rb:69:in `perform_action_without_rescue'</line> <line>/usr/lib64/ruby/gems/1.8/gems/actionpack-1.12.3/lib/action_controller/rescue.rb:82:in `perform_action'</line> <line>/usr/lib64/ruby/gems/1.8/gems/actionpack-1.12.3/lib/action_controller/base.rb:381:in `process_without_filters'</line> <line>/usr/lib64/ruby/gems/1.8/gems/actionpack-1.12.3/lib/action_controller/filters.rb:377:in `process_without_session_management_support'</line> <line>/usr/lib64/ruby/gems/1.8/gems/actionpack-1.12.3/lib/action_controller/session_management.rb:117:in `process'</line> <line>/usr/lib64/ruby/gems/1.8/gems/rails-1.1.4/lib/dispatcher.rb:38:in `dispatch'</line> <line>/usr/lib64/ruby/gems/1.8/gems/rails-1.1.4/lib/fcgi_handler.rb:150:in `process_request'</line> <line>/usr/lib64/ruby/gems/1.8/gems/rails-1.1.4/lib/fcgi_handler.rb:54:in `process!'</line> <line>/usr/lib64/ruby/1.8/fcgi.rb:612:in `each_cgi'</line> <line>/usr/lib64/ruby/1.8/fcgi.rb:609:in `each_cgi'</line> <line>/usr/lib64/ruby/gems/1.8/gems/rails-1.1.4/lib/fcgi_handler.rb:53:in `process!'</line> <line>/usr/lib64/ruby/gems/1.8/gems/rails-1.1.4/lib/fcgi_handler.rb:23:in `process!'</line> <line>/srv/www/opensuse/frontend/current/public/dispatch.fcgi:24</line> </backtrace> </exception> </status> is there a time limit for jobs in the buildservice ??

3 3

[opensuse-buildservice] Building requires a X-server
by Werner Hoch 21 Mar '07

21 Mar '07

Hi all, the package matplotlib in the project science requires an X-server (or at least a DISPLAY) to build (without changing the configuration files). Can I access an X-Server in the buildservice? What are the required changes in my spec file? Background: matplotlib is a python package that gets some configuration informations by calling some python routines: > import gtk produces a warning on openSUSE 10.2 and and error on SUSE_Linux_10.1 > import Tkinter > tk = Tkinter.Tk() raises an error as there is no DISPLAY set. Patching out all checks is possible but I don't like this. Regards Werner --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 1