March 2007 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] Passing options to build for non-local builds
by Andrew Beekhof 13 Mar '07

13 Mar '07

Is there any way to pass options to build for non-local builds? Ie. --changelog The reason being I'd like to always use package.changes instead of the changelog provided by the upstream tarball. (Particularly relevant for debian builds) -- Andrew Beekhof SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) --------------------------------------------------------------------- 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] Debian build errors
by Thomas Anders 13 Mar '07

13 Mar '07

Not sure if this is related to the recent Debian build improvements or changes in our package, but I now get the following errors when building on either Debian_Etch or xUbuntu_6.06 (the old way, using none of the recently added features): [...] package contains more than one tar file: net-snmp_5.5+svn.orig.tar.gz net-snmp.tar.bz2 dpkg-source: error: cannot open .dsc file /usr/src/packages/SOURCES.DEB/*.dsc: No such file or directory ----------------------------------------------------------------- ----- building net-snmp_5.5+svn.dsc (user abuild) ----------------------------------------------------------------- ----------------------------------------------------------------- /.build/build: line 746: hostname: command not found -su: line 0: cd: /usr/src/packages/BUILD: No such file or directory md: stopping all md devices. xenbus_dev_shutdown: device/console/0: Initialising != Connected, skipping System halted. Full log: https://api.opensuse.org/result/net-snmp/Debian_Etch/net-snmp-main-snapshot… What's wrong? +Thomas -- Thomas Anders (thomas.anders at blue-cable.de) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 13

[opensuse-buildservice] Making debian builds easier
by Michael Schroeder 13 Mar '07

13 Mar '07

Hi buildservice fanatics, I've added some code to better integrate debian builds with rpm based builds. As you probably know, debian packages consist of exactly three parts (unless it's an "native debian" package"): - the pristine tarball - a diff file - a dsc file As rpm is much more flexible providing support for multiple patch files, I added some code that autogenerates the debian diff file from plain files, a tar ball, and a set of patches. The generated diff file includes: - all files of the form "debian.*", so you can use a plain "debian.rules" file in the source. - all files from a debian.tar tar file (possibly compressed). It is an error to provide a file both in the tarball and as debian.* file. - all patches from a "debian.series" file, or, if it doesn't exist, a "series" file. This file has the standard "quilt" format, i.e. each line consists of a patch file name and the patch arguments. The diff file generator parses the arguments for "-p" to strip off path components. This allows you to structure your sources identical both for rpm and deb based systems, you can have - the pristine tarball (no need to put .orig in the name, it'll get renamed to the "canonical" debian tar name automatically) - all the patches you need - the series file which provides the patch ordering and naming info - a debian.tar.gz file for things you don't have to touch often - debian.* files for files you often change I also changed the changelog converter so that it understands the debian format, so you no longer need to keep two files up to date. Just make the debian change log the .changes file of the package, the converter automatically uses it as debian/changelog in the diff as long as there is no other changelog. Any more suggestions? Cheers, Michael. -- Michael Schroeder mls(a)suse.de SUSE LINUX Products GmbH, GF Markus Rex, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

5 18

[opensuse-buildservice] Unable to configure the MySQL database with rake migrate
by Jochen Hebbrecht 13 Mar '07

13 Mar '07

I searched the mailinglist, but I guess nobody had this problem. What is defined wrong? The role is in the file: [root@OBS frontend]# cat /srv/www/obs/frontend/vendor/plugins/active_rbac/app/model/role.rb # The Role class represents a role in the database. Roles can have permissions # associated with themselves. Roles can assigned be to roles and groups. # # The Role ActiveRecord class mixes in the "ActiveRbacMixins::RoleMixin" module. # This module contains the actual implementation. It is kept there so # you can easily provide your own model files without having to all lines # from the engine's directory class Role < ActiveRecord::Base include ActiveRbacMixins::RoleMixin end The error: [root@OBS frontend]# cd /srv/www/obs/frontend/ [root@OBS frontend]# rake migrate (in /srv/www/obs/frontend) /srv/www/obs/frontend/config/boot.rb:38:Warning: require_gem is obsolete. Use gem instead. == InitialDatabase: migrating ================================================= -- create_table("groups", {:force=>true}) -> 0.0631s -- add_index("groups", ["parent_id"], {:name=>"groups_parent_id_index"}) -> 0.0471s -- create_table("groups_roles", {:force=>true, :id=>false}) -> 0.0348s -- add_index("groups_roles", ["group_id", "role_id"], {:name=>"groups_roles_all_index", :unique=>true}) -> 0.0469s -- add_index("groups_roles", ["role_id"], {:name=>"role_id"}) -> 0.0469s -- create_table("groups_users", {:force=>true, :id=>false}) -> 0.0348s -- add_index("groups_users", ["group_id", "user_id"], {:name=>"groups_users_all_index", :unique=>true}) -> 0.0475s -- add_index("groups_users", ["user_id"], {:name=>"user_id"}) -> 0.0535s -- create_table("roles", {:force=>true}) -> 0.0354s -- add_index("roles", ["parent_id"], {:name=>"roles_parent_id_index"}) -> 0.0476s rake aborted! Expected /srv/www/obs/frontend/vendor/plugins/active_rbac/app/model/role.rb to define Role --------------------------------------------------------------------- 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] rcobrepserver unable to start using perl-socket-msghdr
by Jochen Hebbrecht 13 Mar '07

13 Mar '07

We are trying to run our own Build Service ... The problem is we are stuck in step 1.1 op README.SETUP ... When we start the rcobsrepserver, we get this error ... Any idea's? [root@OBS ~]# rpm -q perl perl-5.8.5-16.RHEL4 [root@OBS ~]# rpm -q perl-Socket-MsgHdr perl-Socket-MsgHdr-0.01-3.1 [root@OBS ~]# /usr/sbin/rcobsrepserver start bs_repserver (pid 3471) is running... [root@OBS ~]# cat /srv/obs/log/rep_server.log Can't locate loadable object for module Socket::MsgHdr in @INC (@INC contains: build /usr/lib/perl5/5.8.5/i386-linux-thread-multi /usr/lib/perl5/5.8.5 /usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.4/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.3/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.2/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.1/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.0/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.5 /usr/lib/perl5/site_perl/5.8.4 /usr/lib/perl5/site_perl/5.8.3 /usr/lib/perl5/site_perl/5.8.2 /usr/lib/perl5/site_perl/5.8.1 /usr/lib/perl5/site_perl/5.8.0 /usr/lib/perl5/site_perl /usr/lib/perl5/vendor_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.4/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.3/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.2/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.1/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.0/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.5 /usr/lib/perl5/vendor_perl/5.8.4 /usr/lib/perl5/vendor_perl/5.8.3 /usr/lib/perl5/vendor_perl/5.8.2 /usr/lib/perl5/vendor_perl/5.8.1 /usr/lib/perl5/vendor_perl/5.8.0 /usr/lib/perl5/vendor_perl .) at BSHandoff.pm line 26 Compilation failed in require at BSHandoff.pm line 26. BEGIN failed--compilation aborted at BSHandoff.pm line 26. Compilation failed in require at ./bs_repserver line 45. BEGIN failed--compilation aborted at ./bs_repserver line 45. --------------------------------------------------------------------- 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] SPEC-File patching
by Dirk Stoecker 13 Mar '07

13 Mar '07

Hello, Is it possible or can it be implemented to have a patchfile for the SPEC File? When I link to a package of another project I usually detect errors in the specfile, which prevent build for some targets/destinations/... I then checkin my own SPEC-File to fix that. But this has some disadvantages: - It's impossible to see, what I changed, - Changes in the original project are not copied Checking in a file xxx.spec.patch would make it easier to do such things. Also you can then send the original package maintainer a link to the new package and he/she can look at the diff file and maybe include this stuff in the original package. Ciao -- http://www.dstoecker.eu/ (PGP key available) --------------------------------------------------------------------- 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: [opensuse-packaging] mingw cross-toolchain
by Robert Schiele 13 Mar '07

13 Mar '07

On Thu, Jan 11, 2007 at 07:40:32PM +0100, Robert Schiele wrote: > On Thu, Jan 11, 2007 at 03:42:20PM +0100, Ludwig Nussel wrote: > > Robert Schiele wrote: > > > I have packaged a cross-toolchain for Windows machines based on the latest > > > releases of the mingw gcc port. You can find everything at > > > http://pi3.informatik.uni-mannheim.de/~schiele/suse/. > > > > That's nice. Would you mind putting that into the build service? > > I can make a copy there if this is desired. Just suggest a project name. Since no project name was suggested for 6 weeks I just took CrossToolchain:mingw. Unfortunately a linker crash occurred for all 10.0 or newer distributions that cannot be reproduced on the respective systems locally. Thus binaries for these distributions are not available in the build service but have to be fetched from the URL above. Robert -- Robert Schiele Dipl.-Wirtsch.informatiker mailto:rschiele@gmail.com "Quidquid latine dictum sit, altum sonatur."

3 7

[opensuse-buildservice] build08 error
by Thomas Anders 12 Mar '07

12 Mar '07

I'm currently getting a strange error from build08: - --- snip --- build08 started "build net-snmp_5.2.4+svn.dsc" at Mon Mar 12 18:43:52 UTC 2007. Building 'net-snmp-5.2-snapshot' for project 'net-snmp' target 'Debian_Etch' arch 'i586' srcmd5 'c0045a977577acb2b06aad157930eee5' [...] Error: Device 769 (vbd) could not be connected. Hotplug scripts not working. Using config file "/var/run/bsworker_7/build/xen.conf". - --- snap --- and the build is marked as failed. Full details: https://api.opensuse.org/result/net-snmp/Debian_Etch/net-snmp-5.2-snapshot/… What's wrong? +Thomas -- Thomas Anders (thomas.anders at blue-cable.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] Webclient
by Dirk Stoecker 12 Mar '07

12 Mar '07

Hello, When Removing a package from a project and afterwards displaying the project monitor an exception occurs: Error Details: Errorcode: 500 Message: undefined method `code' for nil:NilClass Exception from Webclient: ActionView::TemplateError: undefined method `code' for nil:NilClass Stack Trace: On line #51 of app/views/project/monitor.rhtml 48: # sane default - TODO: fix this in the controller 49: status = 'unknown' 50: status = @statushash[repo][arch][packname] 51: case status.code 52: when 'failed' 53: @failed[packname] = true 54: when 'expansion error' #{RAILS_ROOT}/app/views/project/monitor.rhtml:51:in `_run_rhtml_project_monitor' #{RAILS_ROOT}/app/views/project/monitor.rhtml:46:in `_run_rhtml_project_monitor' #{RAILS_ROOT}/app/views/project/monitor.rhtml:45:in `_run_rhtml_project_monitor' #{RAILS_ROOT}/app/views/project/monitor.rhtml:40:in `_run_rhtml_project_monitor' /usr/lib64/ruby/gems/1.8/gems/actionpack-1.12.3/lib/action_view/base.rb:314:in `compile_and_render_template' /usr/lib64/ruby/gems/1.8/gems/actionpack-1.12.3/lib/action_view/base.rb:290:in `render_template' /usr/lib64/ruby/gems/1.8/gems/actionpack-1.12.3/lib/action_view/base.rb:249:in `render_file' /usr/lib64/ruby/gems/1.8/gems/actionpack-1.12.3/lib/action_controller/base.rb:699:in `render_file' /usr/lib64/ruby/gems/1.8/gems/actionpack-1.12.3/lib/action_controller/base.rb:621:in `render_with_no_layout' /usr/lib64/ruby/gems/1.8/gems/actionpack-1.12.3/lib/action_controller/layout.rb:243:in `render_without_benchmark' /usr/lib64/ruby/gems/1.8/gems/actionpack-1.12.3/lib/action_controller/benchmarking.rb:53:in `render' /usr/lib64/ruby/1.8/benchmark.rb:293:in `measure' /usr/lib64/ruby/gems/1.8/gems/actionpack-1.12.3/lib/action_controller/benchmarking.rb:53:in `render' /usr/lib64/ruby/gems/1.8/gems/actionpack-1.12.3/lib/action_controller/base.rb:911:in `perform_action_without_filters' /usr/lib64/ruby/gems/1.8/gems/actionpack-1.12.3/lib/action_controller/filters.rb:368:in `perform_action_without_benchmark' /usr/lib64/ruby/gems/1.8/gems/actionpack-1.12.3/lib/action_controller/benchmarking.rb:69:in `perform_action_without_rescue' /usr/lib64/ruby/1.8/benchmark.rb:293:in `measure' /usr/lib64/ruby/gems/1.8/gems/actionpack-1.12.3/lib/action_controller/benchmarking.rb:69:in `perform_action_without_rescue' /usr/lib64/ruby/gems/1.8/gems/actionpack-1.12.3/lib/action_controller/rescue.rb:82:in `perform_action' /usr/lib64/ruby/gems/1.8/gems/actionpack-1.12.3/lib/action_controller/base.rb:381:in `process_without_filters' /usr/lib64/ruby/gems/1.8/gems/actionpack-1.12.3/lib/action_controller/filters.rb:377:in `process_without_session_management_support' /usr/lib64/ruby/gems/1.8/gems/actionpack-1.12.3/lib/action_controller/session_management.rb:117:in `process' /usr/lib64/ruby/gems/1.8/gems/rails-1.1.4/lib/dispatcher.rb:38:in `dispatch' /usr/lib64/ruby/gems/1.8/gems/rails-1.1.4/lib/fcgi_handler.rb:150:in `process_request' /usr/lib64/ruby/gems/1.8/gems/rails-1.1.4/lib/fcgi_handler.rb:54:in `process!' /usr/lib64/ruby/1.8/fcgi.rb:612:in `each_cgi' /usr/lib64/ruby/1.8/fcgi.rb:609:in `each_cgi' /usr/lib64/ruby/gems/1.8/gems/rails-1.1.4/lib/fcgi_handler.rb:53:in `process!' /usr/lib64/ruby/gems/1.8/gems/rails-1.1.4/lib/fcgi_handler.rb:23:in `process!' /srv/www/opensuse/webclient/current/public/dispatch.fcgi:24 Ciao -- http://www.dstoecker.eu/ (PGP key available) --------------------------------------------------------------------- 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] Cannot use `build` tool to build openssh-4.4p1-24 rpm on SuSE10.2
by Hung Lin 12 Mar '07

12 Mar '07

Hi, I tried to create openssh-4.4p1-24 rpm on SuSE10.2 machine. I used the `build` tool and here's the command I ran: test124:~/suse_build/openssh-4.4p1-24 # build --rpms /mnt/10.2/ openssh.spec logging output to /var/tmp/build-root/.build.log... test124 started "build openssh.spec" at Mon Mar 12 12:11:47 EDT 2007. Using BUILD_ROOT=/var/tmp/build-root Using BUILD_RPMS=/mnt/10.2/ Using BUILD_ARCH=i586:i486:i386 processing specfile /root/suse_build/openssh-4.4p1-24/openssh.spec... init_buildsystem openssh.spec ... expanding package dependencies... expansion error have choice for syslog needed by openct: syslogd syslog-ng It seems it cannot resolve the dependencies of the required rpms. The thing I don't understand is that I removed all packages in "usedforbuild" line and ran the same command again, it still showed the same error messages. I tried to use `build` tool to build hello-2.1.1-343 and it works fine. Thank you very much for your time. Hung Lin Software Engineer NexTone Communications, Inc. -- Network Without Limits -- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 1