September 2007 - openSUSE Build Service

[opensuse-buildservice] Re: [opensuse-svn] r2148 - trunk/buildservice/src/clientlib/python/osc/osc
by Dr. Peter Poeml 12 Sep '07

12 Sep '07

On Wed, Sep 12, 2007 at 12:01:17PM -0600, Novell Forge SVN wrote: > Author: Marcus_H [...] > Log: > added a bit more functionality to do_maintainers. It is possible to add and delete users from a project/package [...] > + @cmdln.option('-a', '--add', metavar='user', > + help='add a new maintainer') > + @cmdln.option('-d', '--delete', metavar='user', > + help='delete a maintainer from a project or package') Hey, that's just great! Peter -- "WARNING: This bug is visible to non-employees. Please be respectful!" SUSE LINUX Products GmbH Research & Development

1 0

[opensuse-buildservice] Request for server:ltsp
by CyberOrg 12 Sep '07

12 Sep '07

Hi I would like to move ltsp packages I have been working on in home:cyberorg:experimental to server:ltsp. Here is the project details: http://developer.novell.com/wiki/index.php/KIWI-LTSP Thanks -J -- CyberOrg --------------------------------------------------------------------- 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] Status: openSUSE Build Service
by Adrian Schröter 12 Sep '07

12 Sep '07

Hi, this weeks status report regarding the OBS. Please correct me or add items, I forgot. thanks. * New code deployment on api.o.o, this has now improved/extensive support for build flags, even configurable per architecture or repository. * First move of backend server went successfully. We plan to do this next and final move in the next weeks including replacing the server hardware. * Missing bookmark to software.opensuse.org/search in openSUSE 10.3 betas. AI: adrian create bugreport for these (done) * move software.o.o vhost to api.o.o hardware WIP: abauer * repository generation gets moved out of the scheduler into an own process. This allows to scale better and avoids some bugs WIP: mls * Discussion about how to implement improved repository signing. See seperate mail about this from last week on this list. * download.opensuse.org will get used more heavily with openSUSE 10.3. Optimisations are reviewed and implemented by poeml. (WIP) * A ruby-mysql memleak got fixed, this might help our problems on api.o.o, but this is not sure yet. * We want to establish a release process for new build service code. This is needed to support different instances within Novell, but also important for externals to keep stable versions running. AI: adrian keep this on your list * Discussion about the need of a key handling module in YaST for package keyring. AI: adrian make official feature request for openSUSE 11.0 (done) * AI: Klaas review OBS documentation from Frank. Discuss a way with Frank to put it online. * build.o.o currently does not use encryption. We can switch to https, there are no speed problems expected. We can not offer http and https at the same time. Decision to switch. AI: adrian coordinate with Matt * Discussion about the urgency of build support for MacOS X and MS Windows in the build service. AI: adrian get feedback from PM. -- 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

4 4

[opensuse-buildservice] Gotcha when building newer software for older targets
by Dr. Peter Poeml 12 Sep '07

12 Sep '07

Hi, there is a potential problem when building something for older distributions that I just stumbled over. When calling "autoreconf -fi" as is commonly done in spec files, it happens (due to the -i) that the tarball's versions of config.sub, config.guess and ltmain.sh are replaced with the versions from the autoconf package of the target build platform. Which means that the files from the year 2007 are replaced with the 2005 versions when building for SLE10, for instance. This lead to a miscompile in my case (libapr1 when built on SLE10)... I'm now calling autoheader&&autoconf instead of autoreconf on targets < 10.3 (as I did in the past anyway...). So better watch out! Peter -- "WARNING: This bug is visible to non-employees. Please be respectful!" SUSE LINUX Products GmbH Research & Development

1 0

[opensuse-buildservice] Debian build example?
by Paul Elliott 12 Sep '07

12 Sep '07

Are there any good examples of a debian build? What is the answer to this question from the documentation? QUESTION: does the pristine tarball have to be in .gz format? (this seems to be requird for Debian packages normally) Suppose you have the 3 elements (known to work locally): 1) the pristine tarball 2) a diff file 3) a dsc file How do you setup a debian build? Thank You. -- Paul Elliott 1(512)837-1096 pelliott(a)io.com PMB 181, 11900 Metric Blvd Suite J http://www.io.com/~pelliott/pme/ Austin TX 78758-3117

3 2

[opensuse-buildservice] RFC: OBS repository security enhancements
by Adrian Schröter 12 Sep '07

12 Sep '07

We would like to increase the security level when using repository from the OBS by making the repository ownerships more visible. This is hardly possible atm (but not impossible) since we use the same gpg key for all projects. Here are our ideas (together with our security team), any input is appreciated. Requirements: * Make it obvious to the user that adding a repository from another project needs again to trust in it (because different people will have write access there). The installer should point the user to this and ask for his trust on it. * It should work with existing distributions best as possible, of course esp. with openSUSE distris and YaST installer. But of course it should work as good as possible with any other package manager. What we plan to do is * Each project will get an own gpg key, which is used to sign the packages and repository meta files. * The new generated public key gets signed with a global OBS key, so people can check, if the the repository got build indeed for the OBS (this means you can trust that the binaries come from the sources hosted on OBS). * We do not sign any repository anymore with the global OBS key, but generate a key for each existing project Known problems: * People who currently use repositories from OBS will need to import the new gpg key(s). Otherwise the package managers will report errors. Possible future enhancements: * YaST should show which keys signed a pubkey about to get imported. * Allow upload of privates to be used to sign repos ? These keys *must not* get signed by the global OBS key, since they can be used elsewhere. * Does it make sense allow to reuse one key for multiple projects ? Does anyone want to have this at all ? Implementation: * the signing instance stays to be read - only. * The global OBS key remains to be on the signing instance only. * Generated private keys get stored encrypted (with OBS global key) on general storage server to keep signing host an instance without needed backup. bye adrian -- Adrian Schroeter SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) email: adrian(a)suse.de ------------------------------------------------------- -- 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

5 14

[opensuse-buildservice] Request new project for Intel ethernet drivers
by Scott Bahling 11 Sep '07

11 Sep '07

Hi, I need a project for Intel ethernet drivers. There is already a generic project drivers:nic but I need an Intel specific project. drivers:Intel:nic or drivers:nic:Intel sound reasonable to me. I am open to other suggestions. Thanks, 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] Variables in RPM
by Dirk Stoecker 10 Sep '07

10 Sep '07

Hello, I would like to have the output of "pkg-config --variable=pluginsdir gstreamer-0.10" in a variable, so I can use it in %files section. How can I do this? Everything I tried failed. 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] CentOS repositories
by Donavan Pantke 10 Sep '07

10 Sep '07

Has anybody attempted to create standard respoitories for CentOS 4.4 or CentOS 5? If not, what's involved in creating a new repository without having the template XML to go with? Thanks! Donavan --------------------------------------------------------------------- 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] Installing local OBS?
by Rauch Christian 10 Sep '07

10 Sep '07

Hi list, today I tried installing my local OBS here according to [1]. System is the following: VMWare Server running on 10.2 machine (Athlon 64 X2, 2 gig ram) Suse 10.2 installed in VMWare, minimal setup, no zmd, all updates installed. Installed mysql, obs-api, obs-worker, obs-server from [2], created database, started worker and so on. Then it comes to calling "rake migrate" in /srv/www/obs/frontend/, which fails completely. At first the following comes up: ---------------------------------------------------------------------------- obs:/srv/www/obs/frontend/config # rake migrate /usr/bin/rake:17:Warning: require_gem is obsolete. Use gem instead. (in /srv/www/obs/frontend) Cannot find gem for Rails ~>1.2.3.0: Install the missing gem with 'gem install -v=1.2.3 rails', or change environment.rb to define RAILS_GEM_VERSION with your desired version. rake aborted! exit /srv/www/obs/frontend/Rakefile:4 (See full trace by running task with --trace) ---------------------------------------------------------------------------- So i checked to see which rails version I have and changed RAILS_GEM_VERSION to 1.1.6, which changes the error to the following: ---------------------------------------------------------------------------- obs:/srv/www/obs/frontend # rake --trace migrate /usr/bin/rake:17:Warning: require_gem is obsolete. Use gem instead. (in /srv/www/obs/frontend) ** Invoke migrate (first_time) ** Invoke db:migrate (first_time) ** Invoke environment (first_time) ** Execute environment >>>>>>>>>>>>>>>>>>>>>>> /srv/www/obs/common/lib <<<<<<<<<<<<<<<<<<<<<<<<<< Using global environment /srv/www/obs/frontend/config/../config/environments/development_base.rb Using global environment /srv/www/obs/frontend/config/../config/environments/development_base.rb rake aborted! uninitialized constant DynamicSegment /usr/lib64/ruby/gems/1.8/gems/activesupport-1.3.1/lib/active_support/dependencies.rb:123:in `const_missing' /srv/www/obs/frontend/config/../lib/rails_unescape_fix.rb:7 /usr/lib64/ruby/vendor_ruby/1.8/rubygems/custom_require.rb:27:in `gem_original_require' /usr/lib64/ruby/vendor_ruby/1.8/rubygems/custom_require.rb:27:in `require' /usr/lib64/ruby/gems/1.8/gems/activesupport-1.3.1/lib/active_support/dependencies.rb:147:in `require' /srv/www/obs/frontend/config/../config/environment.rb:90 /usr/lib64/ruby/vendor_ruby/1.8/rubygems/custom_require.rb:27:in `gem_original_require' /usr/lib64/ruby/vendor_ruby/1.8/rubygems/custom_require.rb:27:in `require' /usr/lib64/ruby/gems/1.8/gems/rails-1.1.6/lib/tasks/misc.rake:3 /usr/lib64/ruby/gems/1.8/gems/rake-0.7.1/lib/rake.rb:387:in `call' /usr/lib64/ruby/gems/1.8/gems/rake-0.7.1/lib/rake.rb:387:in `execute' /usr/lib64/ruby/gems/1.8/gems/rake-0.7.1/lib/rake.rb:387:in `each' /usr/lib64/ruby/gems/1.8/gems/rake-0.7.1/lib/rake.rb:387:in `execute' /usr/lib64/ruby/gems/1.8/gems/rake-0.7.1/lib/rake.rb:357:in `invoke' /usr/lib64/ruby/1.8/thread.rb:135:in `synchronize' /usr/lib64/ruby/gems/1.8/gems/rake-0.7.1/lib/rake.rb:350:in `invoke' /usr/lib64/ruby/gems/1.8/gems/rake-0.7.1/lib/rake.rb:364:in `invoke_prerequisites' /usr/lib64/ruby/gems/1.8/gems/rake-0.7.1/lib/rake.rb:999:in `each' /usr/lib64/ruby/gems/1.8/gems/rake-0.7.1/lib/rake.rb:999:in `send' /usr/lib64/ruby/gems/1.8/gems/rake-0.7.1/lib/rake.rb:999:in `each' /usr/lib64/ruby/gems/1.8/gems/rake-0.7.1/lib/rake.rb:363:in `invoke_prerequisites' /usr/lib64/ruby/gems/1.8/gems/rake-0.7.1/lib/rake.rb:356:in `invoke' /usr/lib64/ruby/1.8/thread.rb:135:in `synchronize' /usr/lib64/ruby/gems/1.8/gems/rake-0.7.1/lib/rake.rb:350:in `invoke' /usr/lib64/ruby/gems/1.8/gems/rake-0.7.1/lib/rake.rb:364:in `invoke_prerequisites' /usr/lib64/ruby/gems/1.8/gems/rake-0.7.1/lib/rake.rb:999:in `each' /usr/lib64/ruby/gems/1.8/gems/rake-0.7.1/lib/rake.rb:999:in `send' /usr/lib64/ruby/gems/1.8/gems/rake-0.7.1/lib/rake.rb:999:in `each' /usr/lib64/ruby/gems/1.8/gems/rake-0.7.1/lib/rake.rb:363:in `invoke_prerequisites' /usr/lib64/ruby/gems/1.8/gems/rake-0.7.1/lib/rake.rb:356:in `invoke' /usr/lib64/ruby/1.8/thread.rb:135:in `synchronize' /usr/lib64/ruby/gems/1.8/gems/rake-0.7.1/lib/rake.rb:350:in `invoke' /usr/lib64/ruby/gems/1.8/gems/rake-0.7.1/lib/rake.rb:1906:in `run' /usr/lib64/ruby/gems/1.8/gems/rake-0.7.1/lib/rake.rb:1906:in `each' /usr/lib64/ruby/gems/1.8/gems/rake-0.7.1/lib/rake.rb:1906:in `run' /usr/lib64/ruby/gems/1.8/gems/rake-0.7.1/bin/rake:7 /usr/bin/rake:18:in `load' /usr/bin/rake:18 ---------------------------------------------------------------------------- >From there I am really lost now. Any hints anyone? Regards, Chris [1]http://en.opensuse.org/Build_Service/Build_Service_Installation_Tutorial/… [2]http://ftp5.gwdg.de/pub/opensuse/repositories/openSUSE:/Tools/openSUSE_10.2/ --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 3