April 2007 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] Strange Behavior in Project "CrossToolchain:sh4"
by Martin Mohring 17 Apr '07

17 Apr '07

After some work, I now managed to bootstrap a linux cross toolchain for sh4 from scratch without binaries here: http://build.opensuse.org/project/show?project=CrossToolchain%3Ash4 It uses binutiles, kernel headers, gcc and glibc from openSUSE:Factory sources. But now I have run into some strange behavior of the buildservice: - All packages build fine for openSUSE 10.2 and openSUSE Factory targets - on SUSE 10.0 and SUSE 10.1, I get some strange expansion errors: have choice for libgcc_s.so.1 needed by db: libgcc cross-sh4-gcc, have choice for libgcc_s.so.1(GCC_3.0) needed by db: libgcc cross-sh4-gcc, have choice for libstdc++.so.6 needed by db: libstdc++ cross-sh4-gcc, have choice for libstdc++.so.6(CXXABI_1.3) needed by db: libstdc++ cross-sh4-gcc, have choice for libstdc++.so.6(GLIBCXX_3.4) needed by db: libstdc++ cross-sh4-gcc, have choice for libgcc_s.so.1 needed by gettext: libgcc cross-sh4-gcc, have choice for libgcc_s.so.1(GCC_3.0) needed by gettext: libgcc cross-sh4-gcc, have choice for libstdc++.so.6 needed by gettext: libstdc++ cross-sh4-gcc, have choice for libstdc++.so.6(CXXABI_1.3) needed by gettext: libstdc++ cross-sh4-gcc, have choice for libstdc++.so.6(GLIBCXX_3.4) needed by gettext: libstdc++ cross-sh4-gcc Can anybody explain what this means in my context? What can I do to fix this (can I?)? Cheers, Martin --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 5

[opensuse-buildservice] Missing Postgresql package in openSUSE:Factory
by Peter Nixon 17 Apr '07

17 Apr '07

Does anyone know why there is no Postgresql package in openSUSE:Factory? Cheers -- Peter Nixon http://www.peternixon.net/ PGP Key: http://www.peternixon.net/public.asc --------------------------------------------------------------------- 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] Old kernel in sles9 environment
by Jeff Mahoney 17 Apr '07

17 Apr '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all - I just added the OCFS2 1.2.5 KMP package to the build service for use with sles9. Unfortunately, the build has failed due to missing include/linux/debugfs.h. It seems the kernel in the build environment is only 2.6.5-7.244 rather than the current 2.6.5-7.283. Is there any way we can get that updated? - -Jeff - -- Jeff Mahoney SUSE Labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFGI+UaLPWxlyuTD7IRAo54AJ9yjCAfNjepVFz4ZBxkOYmnhAnqfwCcDn1U raJLqAYDY1xQUIsE3CJGwiE= =6qGB -----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 2

[opensuse-buildservice] Kernel Module Package Oddity
by Troy Telford 16 Apr '07

16 Apr '07

I've been working on a kernel module package that builds on multiple distros (SLES9, SLES 10, openSUSE, RHEL, Fedora, etc.). I looked at the kernel module packages on the Build Service for some guidance, did some digging, etc. I finally came upon something that worked fine on a non-buildservice machine. In fact, it builds find on an actual <foo linux> install, but not so much with the build service. In particular, SLES 10. The 'offending' parts from the spec file are along the lines of: ******* for flavor in %{flavors_to_build}; do rm -rf obj/$flavor cp -r source obj/$flavor make -C %kernel_source $flavor ${MODULES_CONF_PARAMS} \ M=$PWD/obj/$flavor/ \ modules done ******* I receive an error to the extent of: ******* + make -C %kernel_source '%{flavors_to_build}' make: *** %kernel_source: No such file or directory. Stop. error: Bad exit status from /var/tmp/rpm-tmp.25150 (%build) ******* In the SuSE RPM Macros, %kernel_source is defined as part of the %_kernel_module_package macro (which is itself called by %suse_kernel_module_package). For that matter, so is %{flavors_to_build}. Since I'm calling %_kernel_module_package without a problem, why aren't some of the other values it defines available? The macros are installed as part of the 'rpm' package on SLES 10, which the log shows is installed. (And I'm aware on other distros it's released elsewhere...) When I run the RPM creation command from a SLES 10 box, it builds fine. Any ideas? -- Troy Telford --------------------------------------------------------------------- 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] Conditional %include?
by Troy Telford 14 Apr '07

14 Apr '07

Is it possible to do a conditional spec file include? ie. %if "%_vendor" == "suse" %include %SOURCE1 %else %include %SOURCE2 %endif I ask because it doesn't seem to care whether it's inside a conditional or not... -- Troy Telford --------------------------------------------------------------------- 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] OBS Error on many actions
by Dominique Leuenberger 13 Apr '07

13 Apr '07

Gi, on my own OBS installation, on many things I do (like adding a repo, deleting a repo), I get the message stated below. The computer is not busy at all at this moment (so no workers running, CPU at 0 - 2 %, and out of the 4Gig of Ram, there is also plenty available. Is there anything I can do? The message is: OpenSUSE Webclient Error: Error Details: Errorcode: 500 Message: execution expired Exception from Webclient: Timeout::Error: execution expired Stack Trace: /usr/lib64/ruby/1.8/timeout.rb:54:in `rbuf_fill' /usr/lib64/ruby/1.8/timeout.rb:56:in `timeout' /usr/lib64/ruby/1.8/timeout.rb:76:in `timeout' /usr/lib64/ruby/1.8/net/protocol.rb:132:in `rbuf_fill' /usr/lib64/ruby/1.8/net/protocol.rb:116:in `readuntil' /usr/lib64/ruby/1.8/net/protocol.rb:126:in `readline' /usr/lib64/ruby/1.8/net/http.rb:2017:in `read_status_line' /usr/lib64/ruby/1.8/net/http.rb:2006:in `read_new' /usr/lib64/ruby/1.8/net/http.rb:1047:in `request' /usr/lib64/ruby/1.8/net/http.rb:854:in `put' /srv/www/obs/common/lib/activexml/transport.rb:449:in `http_do' /usr/lib64/ruby/1.8/net/http.rb:543:in `start' /usr/lib64/ruby/1.8/net/http.rb:440:in `start' /srv/www/obs/common/lib/activexml/transport.rb:437:in `http_do' /srv/www/obs/common/lib/activexml/transport.rb:343:in `save' /srv/www/obs/common/lib/activexml/base.rb:90:in `save' /srv/www/obs/webclient/public/../config/../app/controllers/project_controller.rb:356:in `save_target' /usr/lib64/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/base.rb:941:in `send' /usr/lib64/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/base.rb:941:in `perform_action_without_filters' /usr/lib64/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/filters.rb:368:in `perform_action_without_benchmark' /usr/lib64/ruby/gems/1.8/gems/actionpack-1.12.5/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.5/lib/action_controller/benchmarking.rb:69:in `perform_action_without_rescue' /usr/lib64/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/rescue.rb:82:in `perform_action' /usr/lib64/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/base.rb:408:in `send' /usr/lib64/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/base.rb:408:in `process_without_filters' /usr/lib64/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/filters.rb:377:in `process_without_session_management_support' /usr/lib64/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/session_management.rb:117:in `process' /usr/lib64/ruby/gems/1.8/gems/rails-1.1.6/lib/dispatcher.rb:38:in `dispatch' /usr/lib64/ruby/gems/1.8/gems/rails-1.1.6/lib/fcgi_handler.rb:150:in `process_request' /usr/lib64/ruby/gems/1.8/gems/rails-1.1.6/lib/fcgi_handler.rb:54:in `process!' /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-1.1.6/lib/fcgi_handler.rb:53:in `process!' /usr/lib64/ruby/gems/1.8/gems/rails-1.1.6/lib/fcgi_handler.rb:23:in `process!' /srv/www/obs/webclient/public/dispatch.fcgi:24 -- 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

3 2

[opensuse-buildservice] building 32bit packages on x86_64?
by Mathias Homann 13 Apr '07

13 Apr '07

Hi, in the buildservice tutorial, it says: "Normally the build service produces 32bit packages for 64bit architectures automatically." Seems that we're in some not-normal state, since it doesn't do that. Or was there something i have to put in the spec files that isn't mentioned in the tutorial? bye, MH --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

4 9

[opensuse-buildservice] Removal request
by Matthias Hopf 13 Apr '07

13 Apr '07

Please remove the project Compiz-Quinn, on both build.opensuse.org and software.opensuse.org. The project is completely empty, and many people are stumbling over it. Compiz in both versions can be downloaded from project X11:XGL. Thanks Matthias -- Matthias Hopf <mhopf(a)suse.de>, SuSE R&D, Zimmer 3.2.06, Tel. 74053-715 --------------------------------------------------------------------- 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] Apache Server Modules and PHP5 repositories 'possibility for confusion'
by Oliver Pawellek 13 Apr '07

13 Apr '07

Greetings: One small question, is it truly necessary to have such alternative sub-packages (as shown below) within the Apache Server Modules, PHP5 and PHP5 Extensions repositories for the same OS version without perhaps bewildering the majority of downloaders, I have noticed at this early stage persons are asking what is the "real" difference between each sub-repository (other than the vague hinting title as to what might be different). For example (on viewing the openSUSE 10.2 , x86_64, repositories) we have: ../download/Apache:/Modules ./openSUSE_10.2 ./Apache_openSUSE_10.2 * * the above latter repository for unknown reason is not openSUSE build-service authenticated/singed. Again for PHP5, and the PHP5 extensions (two, and three sub-repositories for Extension): ../download/server:/php ./openSUSE_10.2 ./server_apache_openSUSE_10.2 ../download/server:/php:/extensions ./openSUSE_10.2 ./server_apache_openSUSE_10.2 ./server_php_openSUSE_10.2 At first glance, there appears to be very little difference between each sub-repository, so if one is indeed utilizing an Apache server, why would one not be content to apply the sub-repository marked simply openSUSE_10.2. However, if such specific sub-repositories are indeed required or beneficial, then would it not prove helpful (since the majority of downloaders will not have inside knowledge of the specifics a packager is compiling with/in each sub-repository) for the packager of such additional sub-repositories to provide a clear and concise repository 'content description' to aid/assist the downloader or systems administrator. Or perhaps bundle sub-repositories in a more concise fashion together with a short but informative description. -- Oliver --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 6

[opensuse-buildservice] obsworker TCP ports
by Troy Telford 12 Apr '07

12 Apr '07

I've been building my own buildservice server for some internal development work. I've been successful in getting the obsworker daemon set up on a few nodes, but I've got a fairly large pool on a different network, so it seems reasonable to use SSH to tunnel through. Other than TCP ports 6362 and 6262, are there any TCP ports I need to be aware of if I want to use ssh to tunnel through to a set of worker nodes (that are on a different network)? -- Troy Telford --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 1