- openSUSE Build Service

[opensuse-buildservice] osc build openSUSE_Factory i586 gramps.spec --clean, pkg filesystem error
by Richard Bos 28 Mar '07

28 Mar '07

Just for the record, while executing: # osc build openSUSE_Factory i586 gramps.spec --clean ................. running filesystem preinstall script .init_b_cache/scripts/filesystem.pre: line 1: syntax error near unexpected token `"/usr/include/X11"' .init_b_cache/scripts/filesystem.pre: line 1: `os.remove ("/usr/include/X11")' .................. -- 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

4 6

[opensuse-buildservice] Re: [opensuse-packaging] trigger_false_failures
by Marcus Rueckert 28 Mar '07

28 Mar '07

On 2007-03-27 13:08:23 +0200, Stanislav Brabec wrote: > Because I have a big problem with false failures in the Build Service, > which make nearly impossible to make complete rebuild of GNOME:UNSTABLE > and I already spent several hours by clicking to "trigger rebuild", > I wrote a simple script, which auto-triggers false failures. > > >From my experiments, it seems to be optimal to call this script every 30 > minutes or so. Longer period may cause repeated triggering of too many > dependent packages, shorter period may trigger packages, which not yet > properly updated its status. your script is sadly a bit punishing for the buildservice. the smarter solution: $ echo "machine api.opensuse.org login <username> password <yourpass>" >> ~/.netrc $ chmod 0600 ~/.netrc $ curl -n -X POST -d '' 'https://api.opensuse.org/build/GNOME:UNSTABLE?cmd=rebuild&code=failed' > Note: I am not able to trigger packages with "+" in name in any way (nor > via). It seems to be a bug of Build Service, e. g.: the '+' should be fixed since ages. > osc rebuildpac GNOME:UNSTABLE libxml++ i586 isnt the repository missing here? osc rebuildpac takes 4 args. > does not work, web interface does not work as well. maybe something for andreas to look into. :) but i thought we fixed it. please keep in mind it wont jump to the news state instantly sometimes. if the scheduler is busy it can take a few seconds. so be patient. last but not least adrian promised xen will be more stable now. so lets hope ;) hope this helps, darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

5 7

[opensuse-buildservice] Problem installing local OBS !!NOSIG!!
by Dominique Leuenberger 28 Mar '07

28 Mar '07

Hi, I'm in process of installing OBS on my computer in order to make some things easier for me and because that particular project can not be moved to the BS. So I installed the rpms obs-server, obs-worker and obs-api and followed the documentation in README.SETUP (after Darix told me where it was... Thanks again at this point). Now I have lighttpd running and the websites 127.0.42.{1,2} can be reached. -I can log in as Admin on 127.0.42.2 The problem is: on 127.0.42.1, by entering user Admin with the corresponding password, then clicking 'Login' brings me to an error in Firefox, stating that it detected a misbehaving redirect, that can not work. In the log files I found the following: Processing MainController#index (for 127.0.42.1 at 2007-03-27 22:44:56) [GET] [I|# 5370] Session ID: e147629921c8ce4fffcb2f7ffc1aa052 [I|# 5370] Parameters: {"action"=>"index", "controller"=>"main"} [D|# 5370] return_to: / [I|# 5370] Rendering within layouts/application [I|# 5370] Rendering main/index [D|# 5370] Rendered main/_search_form (0.00192) [I|# 5370] Completed in 0.03992 (25 reqs/sec) | Rendering: 0.03798 (95%) | 200 OK [http://127.0.42.1/] [I|# 5370] Processing UserController#store_login (for 127.0.42.1 at 2007-03-27 22:45:02) [POST] [I|# 5370] Session ID: e147629921c8ce4fffcb2f7ffc1aa052 [I|# 5370] Parameters: {"x"=>"0", "y"=>"0", "user_login"=>"Admin", "action"=>"store_login", "controller"=>"user", "user_password"=>"opensuse"} [D|# 5370] return_to: /user/store_login [D|# 5370] Admin wants to log in with pwd XXX [D|# 5370] Default url = http://127.0.42.1/ [I|# 5370] Redirected to http://127.0.42.1/user/store_login [I|# 5370] Completed in 0.00142 (702 reqs/sec) | 302 Found [http://127.0.42.1/user/store_login] [I|# 5370] The second block repeats 20 times until FF gives up What can be wrong in this situation? Where can I have a look? How can I debug it further ? I'd really like to get this thing running :-) Greetings, Dominique TMF is a global management and accounting outsourcing firm with 72 offices in 56 countries and over 2,000 professionals (February 2007). TMF is expanding rapidly throughout the world. Learn more about our unique network and our services and visit our website at www.tmf-group.com. The information contained in this e-mail communication is confidential and solely intended for the person to whom it is addressed. If someone other than the intended recipient should receive or come into possession of this e-mail communication, he/she will not be entitled to read, disseminate, disclose or duplicate it. If you are not the intended recipient, you are requested to notify the sender and to destroy the original e-mail communication. TMF is neither liable for the correct and complete transmission of the information contained in this e-mail communication nor for any delay in its receipt. This footnote also confirms that this email message has been checked for the presence of computer viruses. --------------------------------------------------------------------- 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] new build host worker images & server downtime
by Adrian Schröter 27 Mar '07

27 Mar '07

Hi, we have deployed new system images (of course created with KIWI ;) to all build hosts. These do contain a number of fixes for outstanding issues, esp. for the random failures on setup of the build enviroments. It is unknown for now if these also fix the problem of random failures after successfull build (according to log file). Please report any kind of failures which are not caused by packaging / source problems, where the build is newer than this mail. We will have a short downtime of the build service, including software.o.o and download.o.o on friday 07:00 UTC. We get more electrical power in our server room for more build hosts :) I suppose the downtime will be shorter than 1 hour. bye adrian -- Adrian Schroeter SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) 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

2 1

[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