openSUSE Build Service July 2009

buildservice@lists.opensuse.org

60 participants
83 discussions

[opensuse-buildservice] Linking to other projects

by Dave Plater

Hi, I'm trying to build a yast2-qt-pkg in my home project but it fails on libzypp needs satsolver-tools = 0.14.1, I see that zypper head contains version 0.14.2 and two home projects have 0.14.1. I'm a complete newbie to build service but I notice a link package from other project function, is this for my subprojects or can it safely be used to link to a package from somebody else's home? Also if this is so is there any sort of etiquette involved? Regards Dave P -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

11 years, 6 months

[opensuse-buildservice] osc: packaging fix for the stupid ubuntu 9.04 dist-packages bug

by Martin Mohring

Hi Adrian, could you please apply the ubuntu 9.04 bugfix inside debian.tar.gz for the osc package also to regular openSUSE:Tools/osc package. In openSUSE:Tools:Devel/osc-svn/debian.tar.gz there is inside "rules" a line: if [ x"$$(python -c 'from distutils.sysconfig import get_python_lib; print get_python_lib()' | grep dist-packages)" == x"" ]; then python setup.py install --prefix=$(CURDIR)/debian/tmp/usr; else python setup.py install --root=$(CURDIR)/debian/tmp --install-layout=deb; fi that applies the special treatment for the borked ubuntu 9.04 site-packages library stuff. Cheers, Martin -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

11 years, 6 months

[opensuse-buildservice] Need a build service tutorial

by Dave Plater

Hi, I have a build service account but I need a little bit of assistance in building my first package. Can anybody help. Regards Dave P -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

11 years, 6 months

[opensuse-buildservice] osc: borked in svn trunk

by Martin Mohring

Hi, in the current svn chunk, osc code seems to be borked.... when i call osc, it get: > osc Traceback (most recent call last): File "/usr/bin/osc", line 11, in <module> sys.setdefaultencoding(locale.getdefaultlocale()[1]) TypeError: setdefaultencoding() argument 1 must be string, not None That is on openSUSE 11.0 x86_64 bit host. Cheers, Martin -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

11 years, 6 months

[opensuse-buildservice] best practices advice

by Jon Nelson

I was hoping to get some advice about how to arrange things in a local build service. Let's say we have a series of developers. Sometimes they work on stuff that's really only interesting to them, othertimes (more often) they are working on projects which will eventually make it into production. Let's also say that you want to allow a two- or three- tiered environment, where individual developers will have their own projects, where there will be a shared development environment (like staging), and then production. What I'd like to know is how people set things up so that developers can say something like "OK, production manager, package FOO version BAR is ready to go" and have that person (the production manager) place package FOO (version BAR) into the production environment. Ditto for all appropriate dependencies, etc... Basically, how do you set things up so that there can be several internally consistent environments (projects), such that a person that manages the production environment get acquire packages without lots of hoop jumping. At first blush, it seems that linking or aggregating would work, but it seems as though if the source package changes then it gets rebuilt everywhere it is linked. That is not desirable in this case. Obviously, one could just do something like a "copy" but is there a better way? Can links work with a specific (build service) version? How are others cracking this particular nut? -- Jon -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

11 years, 6 months

[opensuse-buildservice] local OBS installation problems

by Peter Czanik

Hello, I'm trying to install OBS on my local workstation. First I tried the Devel version, but did not have much luck, so I went back to v1.6 from opensuse:Tools. Again, no luck, it has problems. Reaching http://127.0.42.2/ gives an "500 - Internal Error" from both an browser or from the command line: czanik@bigone111:~> curl -0 --user "Admin:opensuse" -X PUT -T /usr/share/doc/packages/obs-api/openSUSE.org.xml http://127.0.42.2/source/openSUSE.org/_meta <?xml version="1.0" encoding="iso-8859-1"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> <head> <title>500 - Internal Server Error</title> </head> <body> <h1>500 - Internal Server Error</h1> </body> </html> When I open any page from the web interface on http://127.0.42.1/ I get the following ugly message: OpenSUSE Webclient Error: Error Details: *Errorcode: *unknown *Message: *<?xml version="1.0" encoding="iso-8859-1"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> <head> <title>500 - Internal Server Error</title> </head> <body> <h1>500 - Internal Server Error</h1> </body> </html> Exception from Webclient: *ActiveXML::Transport::Error*: <?xml version="1.0" encoding="iso-8859-1"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> <head> <title>500 - Internal Server Error</title> </head> <body> <h1>500 - Internal Server Error</h1> </body> </html> Stack Trace: /srv/www/obs/common/lib/activexml/transport.rb:549:in `handle_response' /srv/www/obs/common/lib/activexml/transport.rb:534:in `http_do' /srv/www/obs/common/lib/activexml/transport.rb:346:in `find' /srv/www/obs/common/lib/activexml/base.rb:69:in `find' /srv/www/obs/webclient/app/controllers/application.rb:116:in `basic_auth' /srv/www/obs/webclient/app/controllers/application.rb:74:in `authorize' /srv/www/obs/webclient/app/controllers/main_controller.rb:8:in `index' /usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/base.rb:1166:in `send' /usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/base.rb:1166:in `perform_action_without_filters' /usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/filters.rb:579:in `call_filters' /usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/filters.rb:572:in `perform_action_without_benchmark' /usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/benchmarking.rb:68:in `perform_action_without_rescue' /usr/lib/ruby/1.8/benchmark.rb:293:in `measure' /usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/benchmarking.rb:68:in `perform_action_without_rescue' /usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/rescue.rb:201:in `perform_action' /usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/base.rb:529:in `send' /usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/base.rb:529:in `process_without_filters' /usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/filters.rb:568:in `process_without_session_management_support' /usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/session_management.rb:130:in `process' /usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/base.rb:389:in `process' /usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/dispatcher.rb:149:in `handle_request' /usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/dispatcher.rb:107:in `dispatch' /usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/dispatcher.rb:104:in `synchronize' /usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/dispatcher.rb:104:in `dispatch' /usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/dispatcher.rb:120:in `dispatch_cgi' /usr/lib/ruby/gems/1.8/gems/actionpack-2.1.2/lib/action_controller/dispatcher.rb:35:in `dispatch' /usr/lib/ruby/gems/1.8/gems/rails-2.1.2/lib/fcgi_handler.rb:103:in `process_request' /usr/lib/ruby/gems/1.8/gems/rails-2.1.2/lib/fcgi_handler.rb:153:in `with_signal_handler' /usr/lib/ruby/gems/1.8/gems/rails-2.1.2/lib/fcgi_handler.rb:101:in `process_request' /usr/lib/ruby/gems/1.8/gems/rails-2.1.2/lib/fcgi_handler.rb:78:in `process_each_request' /usr/lib/ruby/vendor_ruby/1.8/fcgi.rb:612:in `each_cgi' /usr/lib/ruby/vendor_ruby/1.8/fcgi.rb:609:in `each' /usr/lib/ruby/vendor_ruby/1.8/fcgi.rb:609:in `each_cgi' /usr/lib/ruby/gems/1.8/gems/rails-2.1.2/lib/fcgi_handler.rb:77:in `process_each_request' /usr/lib/ruby/gems/1.8/gems/rails-2.1.2/lib/fcgi_handler.rb:76:in `catch' /usr/lib/ruby/gems/1.8/gems/rails-2.1.2/lib/fcgi_handler.rb:76:in `process_each_request' /usr/lib/ruby/gems/1.8/gems/rails-2.1.2/lib/fcgi_handler.rb:50:in `process!' /usr/lib/ruby/gems/1.8/gems/rails-2.1.2/lib/fcgi_handler.rb:24:in `process!' /srv/www/obs/webclient/public/dispatch.fcgi:24 Any hints, how to fix these? Bye, CzP -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

11 years, 6 months

[opensuse-buildservice] local obs and create_package_description

by Christian

Hi, on my local obs I found this error. running create_package_descr Can't exec "create_package_descr": Permission denied at /usr/lib/obs/server//bs_publish line 99. create_package_descr: Permission denied create_package_descr failed: 256 where to find "create_package_descr" ? Installed obs packages: wdf-ux-0013 obs:/usr/lib/obs/server # rpm -qa | grep obs obs-api-1.6.0-9.1 obs-utils-1.6.0-9.1 obs-server-1.6.0-9.1 Regards Chris -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

11 years, 6 months

[opensuse-buildservice] HTML repo view

by Wolfgang Rosenauer

Hi, where is the HTML report gone which was in every OBS repo's repodata directory? I found that useful but it's apparently gone. Wolfgang -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

11 years, 6 months

[opensuse-buildservice] Some "Substitute"s

by Cristian Morales Vega

I don't know exactly what policy you use to add them (I suppose you don't add them for released/fixed products as openSUSE < 11.2), but anyway some I use... %if 0%{?fedora_version} Substitute: libexpat-devel expat-devel Substitute: libpulse-devel pulseaudio-libs-devel Substitute: pkg-config pkgconfig %endif %if 0%{?suse_version} %if 0%{?suse_version} < 1100 Substitute: gstreamer-0_10-devel gstreamer010-devel %endif %if 0%{?suse_version} < 1110 Substitute: libxine-devel xine-devel %endif %endif -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

11 years, 6 months

[opensuse-buildservice] bad line: supplements "packageand(<name>:pam-x86)"

by Lars Müller

Hi, we see a failing build of network:samba:STABLE and network:samba:TESTING for openSUSE 10.3 due to the following error: bad line: supplements "packageand(samba:pam-x86)" Might we ignore such a 'bad' line instead of resulting in a failing build? Or do we have to file the used baselibs.conf different? Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany

11 years, 6 months

← Newer
1
2
3
4
5
6
7
8
9
Older →

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Build Service July 2009