[opensuse-buildservice] ppc
Hello, I got now a bit stronger PPC machine standing next to my desk ( http://en.opensuse.org/MPC8610 ). This brought me the idea, that I should recompile some buildservice projects for PPC (like: http://download.opensuse.org/repositories/X11:/Enlightenment/ or http://download.opensuse.org/repositories/KDE:/KDE4:/UNSTABLE:/Desktop/ ). Before trying it myself I read some of the documentation, but I still have a couple of questions: - does the buildservice work at all on PPC? - if yes, is it a simple recompile of all files at http://ftp-1.gwdg.de/pub/opensuse/repositories/openSUSE:/Tools/openSUSE_11.0... on PPC? - is it possible to check out a project from BS, like KDE4:/Unstable:/Desktop and recompile it locally for PPC in one go? I mean, without needing to compile individual source rpms one by one and needing to figure out the build order... Bye, CzP --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Friday 13 June 2008 13:56:51 Peter Czanik wrote:
Hello,
I got now a bit stronger PPC machine standing next to my desk ( http://en.opensuse.org/MPC8610 ). This brought me the idea, that I should recompile some buildservice projects for PPC (like: http://download.opensuse.org/repositories/X11:/Enlightenment/ or http://download.opensuse.org/repositories/KDE:/KDE4:/UNSTABLE:/Desktop/ ). Before trying it myself I read some of the documentation, but I still have a couple of questions:
- does the buildservice work at all on PPC?
yes
- if yes, is it a simple recompile of all files at http://ftp-1.gwdg.de/pub/opensuse/repositories/openSUSE:/Tools/openSUSE_11. 0/src/ on PPC?
they should compile also on ppc. Tell us if not and we try to fix it.
- is it possible to check out a project from BS, like KDE4:/Unstable:/Desktop and recompile it locally for PPC in one go? I mean, without needing to compile individual source rpms one by one and needing to figure out the build order...
You can setup your own build service, create source links to our remote instance and compile it at your side. You would just need to import a ppc based distro into some own project first. bye adrian -- Adrian Schroeter SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) email: adrian@suse.de --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Hi, i have ppc working here and I am testing it regularily (Adrian knows it ...). Its only a matter of changing some 10 lines inside the code and config. Also you need to install also the ppc versions of the distro of interest in parallel to x86, which I in fact do to run it. I would write it down here if you whish. I have tested it with svn trunc -r 4170, which is more or lesst OBS 1.0 rc1 Martin Adrian Schröter wrote:
On Friday 13 June 2008 13:56:51 Peter Czanik wrote:
Hello,
I got now a bit stronger PPC machine standing next to my desk ( http://en.opensuse.org/MPC8610 ). This brought me the idea, that I should recompile some buildservice projects for PPC (like: http://download.opensuse.org/repositories/X11:/Enlightenment/ or http://download.opensuse.org/repositories/KDE:/KDE4:/UNSTABLE:/Desktop/ ). Before trying it myself I read some of the documentation, but I still have a couple of questions:
- does the buildservice work at all on PPC?
yes
- if yes, is it a simple recompile of all files at http://ftp-1.gwdg.de/pub/opensuse/repositories/openSUSE:/Tools/openSUSE_11. 0/src/ on PPC?
they should compile also on ppc. Tell us if not and we try to fix it.
- is it possible to check out a project from BS, like KDE4:/Unstable:/Desktop and recompile it locally for PPC in one go? I mean, without needing to compile individual source rpms one by one and needing to figure out the build order...
You can setup your own build service, create source links to our remote instance and compile it at your side. You would just need to import a ppc based distro into some own project first.
bye adrian
--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Martin Mohring írta:
Hi,
i have ppc working here and I am testing it regularily (Adrian knows it ...). Its only a matter of changing some 10 lines inside the code and config. Also you need to install also the ppc versions of the distro of interest in parallel to x86, which I in fact do to run it. Do I understand well, that you use x86 machines to compile PPC?
I would write it down here if you whish. I have tested it with svn trunc -r 4170, which is more or lesst OBS 1.0 rc1 Is http://download.opensuse.org/repositories/openSUSE:/Tools/openSUSE_11.0/src/... equal to OBS 1.0 rc1? This is the latest version available as far as I can see...
Anyway, I'm downloading it and trying to install it on my PPC machine... Bye, CzP
Martin
Adrian Schröter wrote:
On Friday 13 June 2008 13:56:51 Peter Czanik wrote:
Hello,
I got now a bit stronger PPC machine standing next to my desk ( http://en.opensuse.org/MPC8610 ). This brought me the idea, that I should recompile some buildservice projects for PPC (like: http://download.opensuse.org/repositories/X11:/Enlightenment/ or http://download.opensuse.org/repositories/KDE:/KDE4:/UNSTABLE:/Desktop/ ). Before trying it myself I read some of the documentation, but I still have a couple of questions:
- does the buildservice work at all on PPC?
yes
- if yes, is it a simple recompile of all files at http://ftp-1.gwdg.de/pub/opensuse/repositories/openSUSE:/Tools/openSUSE_11.
0/src/ on PPC?
they should compile also on ppc. Tell us if not and we try to fix it.
- is it possible to check out a project from BS, like KDE4:/Unstable:/Desktop and recompile it locally for PPC in one go? I mean, without needing to compile individual source rpms one by one and needing to figure out the build order...
You can setup your own build service, create source links to our remote instance and compile it at your side. You would just need to import a ppc based distro into some own project first.
bye adrian
--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Friday 13 June 2008 16:10:32 Peter Czanik wrote: ..
I would write it down here if you whish. I have tested it with svn trunc -r 4170, which is more or lesst OBS 1.0 rc1
Is http://download.opensuse.org/repositories/openSUSE:/Tools/openSUSE_11.0/src /obs-server-0.9.99-3.1.src.rpm equal to OBS 1.0 rc1? This is the latest version available as far as I can see...
yes, this is rc1 -- Adrian Schroeter SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) email: adrian@suse.de --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Peter Czanik wrote:
Martin Mohring írta:
Hi,
i have ppc working here and I am testing it regularily (Adrian knows it ...). Its only a matter of changing some 10 lines inside the code and config. Also you need to install also the ppc versions of the distro of interest in parallel to x86, which I in fact do to run it. Do I understand well, that you use x86 machines to compile PPC?
I would write it down here if you whish. I have tested it with svn trunc -r 4170, which is more or lesst OBS 1.0 rc1 Is http://download.opensuse.org/repositories/openSUSE:/Tools/openSUSE_11.0/src/... equal to OBS 1.0 rc1? This is the latest version available as far as I can see...
Anyway, I'm downloading it and trying to install it on my PPC machine... Bye, CzP Currently, you cross-compiling is not possible in the way everybody would whish it. I have one server for the repositories and MySQL, one for the webclient and some for the different workers (compiling the code).
Currently, you need to have powerpc workers (the compile machines) in order to generate ppc arch compilations. All the repositories/src can handle multiarch right now. Its only that you have to change some lines of code and also have to configure such a mixed setup (able to build x86-32 bit, x86-64 bit and ppc-32 bit, ppc-64 bit). Since the workers is only scripting code, they can run out of the box on ppc machines. But: You need about 2 GB of RAM currently on a machine if it runs webclient, api server, obs backend, mysql and the workers (2 GB == max 1-2 workers on the machine). If your PPC machine is not that powerful, I would opt for putting everything except the workers on some x86 pc and configure the ppc machine only for the workers. Martin --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Hello, Martin Mohring írta:
But: You need about 2 GB of RAM currently on a machine if it runs webclient, api server, obs backend, mysql and the workers (2 GB == max 1-2 workers on the machine). If your PPC machine is not that powerful, I would opt for putting everything except the workers on some x86 pc and configure the ppc machine only for the workers. My machine has only 512MB of RAM, but still wanted to give it a try with everything on the same machine. I tried to follow instructions from http://en.opensuse.org/Build_Service/Build_Service_Installation_Tutorial/ope... (as this seems to be the latest). This is how far I got. After logging in I get this 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>404 - Not Found</title> </head> <body> <h1>404 - Not Found</h1> </body> </html> Exception from Webclient: *ActiveXML::Transport::NotFoundError*: <?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>404 - Not Found</title> </head> <body> <h1>404 - Not Found</h1> </body> </html> Stack Trace: /srv/www/obs/common/lib/activexml/transport.rb:543: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' /usr/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/filters.rb:469:in `send!' /usr/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/filters.rb:469:in `call' /usr/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/filters.rb:441:in `run' /usr/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/filters.rb:716:in `run_before_filters' /usr/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/filters.rb:695:in `call_filters' /usr/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/filters.rb:689:in `perform_action_without_benchmark' /usr/lib/ruby/gems/1.8/gems/actionpack-2.0.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.0.2/lib/action_controller/benchmarking.rb:68:in `perform_action_without_rescue' /usr/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/rescue.rb:199:in `perform_action' /usr/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/base.rb:524:in `send' /usr/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/base.rb:524:in `process_without_filters' /usr/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/filters.rb:685:in `process_without_session_management_support' /usr/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/session_management.rb:123:in `process' /usr/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/base.rb:388:in `process' /usr/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/dispatcher.rb:171:in `handle_request' /usr/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/dispatcher.rb:115:in `dispatch' /usr/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/dispatcher.rb:126:in `dispatch_cgi' /usr/lib/ruby/gems/1.8/gems/actionpack-2.0.2/lib/action_controller/dispatcher.rb:9:in `dispatch' /usr/lib/ruby/gems/1.8/gems/rails-2.0.2/lib/fcgi_handler.rb:101:in `process_request' /usr/lib/ruby/gems/1.8/gems/rails-2.0.2/lib/fcgi_handler.rb:149:in `with_signal_handler' /usr/lib/ruby/gems/1.8/gems/rails-2.0.2/lib/fcgi_handler.rb:99:in `process_request' /usr/lib/ruby/gems/1.8/gems/rails-2.0.2/lib/fcgi_handler.rb:77: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.0.2/lib/fcgi_handler.rb:76:in `process_each_request' /usr/lib/ruby/gems/1.8/gems/rails-2.0.2/lib/fcgi_handler.rb:50:in `process!' /usr/lib/ruby/gems/1.8/gems/rails-2.0.2/lib/fcgi_handler.rb:24:in `process!' /srv/www/obs/webclient/public/dispatch.fcgi:24 Bye, CzP --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Hello, Peter Czanik írta:
*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>404 - Not Found</title> </head> <body> <h1>404 - Not Found</h1> </body> </html> OK, I worked around this. It started to work as soon, as I changed back to 127.0.42.1.
My next problem is: how do I add a repo? When I try based on the README.SETUP I get: suse8610-110:~ # obs_mirror_project openSUSE:11.0 standard ppc Server returned an error: HTTP Error 404: Not Found project has no architecture 'ppc' /usr/lib/ruby/1.8/rexml/source.rb:149:in `initialize': undefined method `[]' for nil:NilClass (NoMethodError) from /usr/lib/ruby/1.8/rexml/source.rb:16:in `new' from /usr/lib/ruby/1.8/rexml/source.rb:16:in `create_from' from /usr/lib/ruby/1.8/rexml/parsers/baseparser.rb:133:in `stream=' from /usr/lib/ruby/1.8/rexml/parsers/baseparser.rb:110:in `initialize' from /usr/lib/ruby/1.8/rexml/parsers/treeparser.rb:9:in `new' from /usr/lib/ruby/1.8/rexml/parsers/treeparser.rb:9:in `initialize' from /usr/lib/ruby/1.8/rexml/document.rb:205:in `new' from /usr/lib/ruby/1.8/rexml/document.rb:205:in `build' from /usr/lib/ruby/1.8/rexml/document.rb:42:in `initialize' from /usr/sbin/obs_mirror_project:48:in `new' from /usr/sbin/obs_mirror_project:48 suse8610-110:~ # The other I tried is based on the wiki: crate a project and add a repo. But that does not seem to work either. When I add openSUSE 11.0 I t uses the following URL, which does not mention PPC at all: http://127.0.42.1/project/save_target?arch[i586]=&arch[x86_64]=&platform=openSUSE.org%3AopenSUSE%3A11.0%2Fstandard&project=proba&targetname=openSUSE_11.0 and results in an error anyway: " OpenSUSE Webclient Error: Error Details: Errorcode: package_save_error Message: error saving project: unable to walk on path 'openSUSE.org:openSUSE:11.0/standard' " Martin: you mentioned, that you had to modify a few lines in OBS. Where/what? Bye, CzP --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Hi, first you select some ppc distro. Lets assume it is openSUSE 11.0 ppc. You download the packages, e.g. from some mirror server. The description is only for a x86 server and ppc workers. You are running openSUSE 11.0 ppc also on your machine, so you have the .rpm pkgs at hand, dont you? Then you need to install the following pkgs for openSUSE 11.0 on the x86 machine createrepo deb lzma python-gpgme python-kid python-setuptools repoview yum yum-metadata-parser Then you install the following pkgs from OBS: build obs-server obs-api obs-worker osc The ppc workers needs: obs-worker osc - take here the i586 version for a 32 bit ppc system build Then change the following lines of code (OBS server): Index: buildservice/src/webclient/app/views/project/add_target.rhtml =================================================================== --- buildservice/src/webclient/app/views/project/add_target.rhtml (revision 4179) +++ buildservice/src/webclient/app/views/project/add_target.rhtml (working copy) @@ -20,7 +20,7 @@ </td> <td valign="top"> <b>Architectures:</b><br/> - <% [:i586, :x86_64].each do |arch| %> + <% [:i586, :x86_64, :ppc].each do |arch| %> <%= check_box_tag "arch[#{arch}]", "", true %><%=arch%><br> <% end %> </td> Then add a project (you can also omit i586/x86_64, if not required) with osc: <project name="openSUSE:11.0"> <title>openSUSE 11.0 distribution</title> <description>The openSUSE 11.0 distribution.</description> <build> <disable/> </build> <publish> <disable/> </publish> <repository name="standard"> <arch>i586</arch> <arch>x86_64</arch> <arch>ppc</arch> </repository> </project> Then look for /srv/obs/build/openSUSE:11.0/standard, there should now be the 3 (or only ppc) directories: i586 ppc x86_64 Then you create inside ppc a new directory "ppc/:full", inside there you put the .noarch.rpm and .ppc.rpm. Then configure the scheduler also for ppc (on the OBS server): $ cat /etc/sysconfig/obs-server ## Path: Applications/OBS ## Description: define for which architectures the packages should get build ## Type: stringlist ## Default: "i586" ## Config: OBS # # This needs to be a space seperated list of all supported architectures OBS_SCHEDULER_ARCHITECTURES="i586 x86_64 ppc" Start the OBS machine, it should indicate a ppc scheduler in the monitor page. Peter Czanik wrote:
Hello,
Peter Czanik írta:
*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>404 - Not Found</title> </head> <body> <h1>404 - Not Found</h1> </body> </html> OK, I worked around this. It started to work as soon, as I changed back to 127.0.42.1.
My next problem is: how do I add a repo? When I try based on the README.SETUP I get:
suse8610-110:~ # obs_mirror_project openSUSE:11.0 standard ppc Server returned an error: HTTP Error 404: Not Found project has no architecture 'ppc' /usr/lib/ruby/1.8/rexml/source.rb:149:in `initialize': undefined method `[]' for nil:NilClass (NoMethodError) from /usr/lib/ruby/1.8/rexml/source.rb:16:in `new' from /usr/lib/ruby/1.8/rexml/source.rb:16:in `create_from' from /usr/lib/ruby/1.8/rexml/parsers/baseparser.rb:133:in `stream=' from /usr/lib/ruby/1.8/rexml/parsers/baseparser.rb:110:in `initialize' from /usr/lib/ruby/1.8/rexml/parsers/treeparser.rb:9:in `new' from /usr/lib/ruby/1.8/rexml/parsers/treeparser.rb:9:in `initialize' from /usr/lib/ruby/1.8/rexml/document.rb:205:in `new' from /usr/lib/ruby/1.8/rexml/document.rb:205:in `build' from /usr/lib/ruby/1.8/rexml/document.rb:42:in `initialize' from /usr/sbin/obs_mirror_project:48:in `new' from /usr/sbin/obs_mirror_project:48 suse8610-110:~ #
The other I tried is based on the wiki: crate a project and add a repo. But that does not seem to work either. When I add openSUSE 11.0 I t uses the following URL, which does not mention PPC at all: http://127.0.42.1/project/save_target?arch[i586]=&arch[x86_64]=&platform=openSUSE.org%3AopenSUSE%3A11.0%2Fstandard&project=proba&targetname=openSUSE_11.0
and results in an error anyway: " OpenSUSE Webclient Error:
Error Details: Errorcode: package_save_error Message: error saving project: unable to walk on path 'openSUSE.org:openSUSE:11.0/standard' "
Martin: you mentioned, that you had to modify a few lines in OBS. Where/what? Bye, CzP
--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Martin Mohring wrote:
Hi,
first you select some ppc distro. Lets assume it is openSUSE 11.0 ppc. You download the packages, e.g. from some mirror server. The description is only for a x86 server and ppc workers.
The reason is: I did not in detail look if all the packages (e.g. ruby rails etc.) all can run on ppc without rebuild for ppc. .noarch.rpm is unproblematic, and scripting like osc is also, athough these packages are packaged for i586/x86_64. And: the OBS needs ca. 1.5 GB RAM, esp. the scheduler. 512 MB is definitely too small to run OBS Server + Workers.
You are running openSUSE 11.0 ppc also on your machine, so you have the .rpm pkgs at hand, dont you?
Then you need to install the following pkgs for openSUSE 11.0 on the x86 machine createrepo deb lzma python-gpgme python-kid python-setuptools repoview yum yum-metadata-parser
Then you install the following pkgs from OBS: build obs-server obs-api obs-worker osc
The ppc workers needs: obs-worker osc - take here the i586 version for a 32 bit ppc system build
Then change the following lines of code (OBS server):
Index: buildservice/src/webclient/app/views/project/add_target.rhtml =================================================================== --- buildservice/src/webclient/app/views/project/add_target.rhtml (revision 4179) +++ buildservice/src/webclient/app/views/project/add_target.rhtml (working copy) @@ -20,7 +20,7 @@ </td> <td valign="top"> <b>Architectures:</b><br/> - <% [:i586, :x86_64].each do |arch| %> + <% [:i586, :x86_64, :ppc].each do |arch| %> <%= check_box_tag "arch[#{arch}]", "", true %><%=arch%><br> <% end %> </td>
Then add a project (you can also omit i586/x86_64, if not required) with osc:
<project name="openSUSE:11.0"> <title>openSUSE 11.0 distribution</title> <description>The openSUSE 11.0 distribution.</description> <build> <disable/> </build> <publish> <disable/> </publish> <repository name="standard"> <arch>i586</arch> <arch>x86_64</arch> <arch>ppc</arch> </repository> </project>
Then look for /srv/obs/build/openSUSE:11.0/standard, there should now be the 3 (or only ppc) directories: i586 ppc x86_64 Then you create inside ppc a new directory "ppc/:full", inside there you put the .noarch.rpm and .ppc.rpm.
Then configure the scheduler also for ppc (on the OBS server):
$ cat /etc/sysconfig/obs-server ## Path: Applications/OBS ## Description: define for which architectures the packages should get build ## Type: stringlist ## Default: "i586" ## Config: OBS # # This needs to be a space seperated list of all supported architectures
OBS_SCHEDULER_ARCHITECTURES="i586 x86_64 ppc"
Start the OBS machine, it should indicate a ppc scheduler in the monitor page.
Peter Czanik wrote:
Hello,
Peter Czanik írta:
*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>404 - Not Found</title> </head> <body> <h1>404 - Not Found</h1> </body> </html>
OK, I worked around this. It started to work as soon, as I changed back to 127.0.42.1.
My next problem is: how do I add a repo? When I try based on the README.SETUP I get:
suse8610-110:~ # obs_mirror_project openSUSE:11.0 standard ppc Server returned an error: HTTP Error 404: Not Found project has no architecture 'ppc' /usr/lib/ruby/1.8/rexml/source.rb:149:in `initialize': undefined method `[]' for nil:NilClass (NoMethodError) from /usr/lib/ruby/1.8/rexml/source.rb:16:in `new' from /usr/lib/ruby/1.8/rexml/source.rb:16:in `create_from' from /usr/lib/ruby/1.8/rexml/parsers/baseparser.rb:133:in `stream=' from /usr/lib/ruby/1.8/rexml/parsers/baseparser.rb:110:in `initialize' from /usr/lib/ruby/1.8/rexml/parsers/treeparser.rb:9:in `new' from /usr/lib/ruby/1.8/rexml/parsers/treeparser.rb:9:in `initialize' from /usr/lib/ruby/1.8/rexml/document.rb:205:in `new' from /usr/lib/ruby/1.8/rexml/document.rb:205:in `build' from /usr/lib/ruby/1.8/rexml/document.rb:42:in `initialize' from /usr/sbin/obs_mirror_project:48:in `new' from /usr/sbin/obs_mirror_project:48 suse8610-110:~ #
The other I tried is based on the wiki: crate a project and add a repo. But that does not seem to work either. When I add openSUSE 11.0 I t uses the following URL, which does not mention PPC at all: http://127.0.42.1/project/save_target?arch[i586]=&arch[x86_64]=&platform=openSUSE.org%3AopenSUSE%3A11.0%2Fstandard&project=proba&targetname=openSUSE_11.0
and results in an error anyway: " OpenSUSE Webclient Error:
Error Details: Errorcode: package_save_error Message: error saving project: unable to walk on path 'openSUSE.org:openSUSE:11.0/standard' "
Martin: you mentioned, that you had to modify a few lines in OBS. Where/what? Bye, CzP
--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Hello, Martin Mohring írta:
Martin Mohring wrote:
Hi,
first you select some ppc distro. Lets assume it is openSUSE 11.0 ppc. You download the packages, e.g. from some mirror server. The description is only for a x86 server and ppc workers.
The reason is: I did not in detail look if all the packages (e.g. ruby rails etc.) all can run on ppc without rebuild for ppc. .noarch.rpm is unproblematic, and scripting like osc is also, athough these packages are packaged for i586/x86_64.
I recompiled all the missing packages on PPC using lbuild without any problems. BTW: there are two rails versions, which is right?
And: the OBS needs ca. 1.5 GB RAM, esp. the scheduler. 512 MB is definitely too small to run OBS Server + Workers.
Well, until now it swapped only 72k when even firefox was running on the machine and I'm already looking for a RAM upgrade. I'd like to keep everything on the same machine - if possible. Bye, CzP
You are running openSUSE 11.0 ppc also on your machine, so you have the .rpm pkgs at hand, dont you?
Then you need to install the following pkgs for openSUSE 11.0 on the x86 machine createrepo deb lzma python-gpgme python-kid python-setuptools repoview yum yum-metadata-parser
Then you install the following pkgs from OBS: build obs-server obs-api obs-worker osc
The ppc workers needs: obs-worker osc - take here the i586 version for a 32 bit ppc system build
Then change the following lines of code (OBS server):
Index: buildservice/src/webclient/app/views/project/add_target.rhtml =================================================================== --- buildservice/src/webclient/app/views/project/add_target.rhtml (revision 4179) +++ buildservice/src/webclient/app/views/project/add_target.rhtml (working copy) @@ -20,7 +20,7 @@ </td> <td valign="top"> <b>Architectures:</b><br/> - <% [:i586, :x86_64].each do |arch| %> + <% [:i586, :x86_64, :ppc].each do |arch| %> <%= check_box_tag "arch[#{arch}]", "", true %><%=arch%><br> <% end %> </td>
Then add a project (you can also omit i586/x86_64, if not required) with osc:
<project name="openSUSE:11.0"> <title>openSUSE 11.0 distribution</title> <description>The openSUSE 11.0 distribution.</description> <build> <disable/> </build> <publish> <disable/> </publish> <repository name="standard"> <arch>i586</arch> <arch>x86_64</arch> <arch>ppc</arch> </repository> </project>
Then look for /srv/obs/build/openSUSE:11.0/standard, there should now be the 3 (or only ppc) directories: i586 ppc x86_64 Then you create inside ppc a new directory "ppc/:full", inside there you put the .noarch.rpm and .ppc.rpm.
Then configure the scheduler also for ppc (on the OBS server):
$ cat /etc/sysconfig/obs-server ## Path: Applications/OBS ## Description: define for which architectures the packages should get build ## Type: stringlist ## Default: "i586" ## Config: OBS # # This needs to be a space seperated list of all supported architectures
OBS_SCHEDULER_ARCHITECTURES="i586 x86_64 ppc"
Start the OBS machine, it should indicate a ppc scheduler in the monitor page.
Peter Czanik wrote:
Hello,
Peter Czanik írta:
*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>404 - Not Found</title> </head> <body> <h1>404 - Not Found</h1> </body> </html>
OK, I worked around this. It started to work as soon, as I changed back to 127.0.42.1.
My next problem is: how do I add a repo? When I try based on the README.SETUP I get:
suse8610-110:~ # obs_mirror_project openSUSE:11.0 standard ppc Server returned an error: HTTP Error 404: Not Found project has no architecture 'ppc' /usr/lib/ruby/1.8/rexml/source.rb:149:in `initialize': undefined method `[]' for nil:NilClass (NoMethodError) from /usr/lib/ruby/1.8/rexml/source.rb:16:in `new' from /usr/lib/ruby/1.8/rexml/source.rb:16:in `create_from' from /usr/lib/ruby/1.8/rexml/parsers/baseparser.rb:133:in `stream=' from /usr/lib/ruby/1.8/rexml/parsers/baseparser.rb:110:in `initialize' from /usr/lib/ruby/1.8/rexml/parsers/treeparser.rb:9:in `new' from /usr/lib/ruby/1.8/rexml/parsers/treeparser.rb:9:in `initialize' from /usr/lib/ruby/1.8/rexml/document.rb:205:in `new' from /usr/lib/ruby/1.8/rexml/document.rb:205:in `build' from /usr/lib/ruby/1.8/rexml/document.rb:42:in `initialize' from /usr/sbin/obs_mirror_project:48:in `new' from /usr/sbin/obs_mirror_project:48 suse8610-110:~ #
The other I tried is based on the wiki: crate a project and add a repo. But that does not seem to work either. When I add openSUSE 11.0 I t uses the following URL, which does not mention PPC at all: http://127.0.42.1/project/save_target?arch[i586]=&arch[x86_64]=&platform=openSUSE.org%3AopenSUSE%3A11.0%2Fstandard&project=proba&targetname=openSUSE_11.0
and results in an error anyway: " OpenSUSE Webclient Error:
Error Details: Errorcode: package_save_error Message: error saving project: unable to walk on path 'openSUSE.org:openSUSE:11.0/standard' "
Martin: you mentioned, that you had to modify a few lines in OBS. Where/what? Bye, CzP
--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
OK, you have pkgs all at hand, fine. Then start the OBS, including the scheduler (e.g. ppc scheduler) Then goto "create project", e.g. http://<your webclient ip>/project/new Give the project the name "openSUSE:11.0". You can leave everthing else blank. Then put this to a file: <project name="openSUSE:11.0"> <title>openSUSE 11.0 distribution</title> <description>The openSUSE 11.0 distribution.</description> <person userid="MartinMohring" role="maintainer"/> <person userid="MartinMohring" role="bugowner"/> <build> <disable/> </build> <publish> <disable/> </publish> <repository name="standard"> <arch>ppc</arch> </repository> </project> then call: $ osc -A <your local api ip> meta prj -F <filename you put this in> openSUSE:11.0 Control success by opening http://<your webclient ip>/project/show?project=openSUSE%3A11.0. Then stop the OBS, install the .noarch.rpm and ppc.rpm inside "/srv/obs/build/openSUSE:11.0/standard/ppc/:full", then restart the OBS and wait some minutes. Anyway, the OBS monitor http://<your local webclient ip>/monitor schould tell you that ppc: running for 38 minutes (last restart: ....) dispatcher: running for about 1 hour (last restart: ...) publisher: running for about 1 hour (last restart: ...) these 3 processes are running. You can follow progress by watching the logfiles inside: "/srv/obs/log" directory. Martin Peter Czanik wrote:
Hello,
Martin Mohring írta:
Martin Mohring wrote:
Hi,
first you select some ppc distro. Lets assume it is openSUSE 11.0 ppc. You download the packages, e.g. from some mirror server. The description is only for a x86 server and ppc workers.
The reason is: I did not in detail look if all the packages (e.g. ruby rails etc.) all can run on ppc without rebuild for ppc. .noarch.rpm is unproblematic, and scripting like osc is also, athough these packages are packaged for i586/x86_64.
I recompiled all the missing packages on PPC using lbuild without any problems. BTW: there are two rails versions, which is right?
And: the OBS needs ca. 1.5 GB RAM, esp. the scheduler. 512 MB is definitely too small to run OBS Server + Workers.
Well, until now it swapped only 72k when even firefox was running on the machine and I'm already looking for a RAM upgrade. I'd like to keep everything on the same machine - if possible. Bye, CzP
You are running openSUSE 11.0 ppc also on your machine, so you have the .rpm pkgs at hand, dont you?
Then you need to install the following pkgs for openSUSE 11.0 on the x86 machine createrepo deb lzma python-gpgme python-kid python-setuptools repoview yum yum-metadata-parser
Then you install the following pkgs from OBS: build obs-server obs-api obs-worker osc
The ppc workers needs: obs-worker osc - take here the i586 version for a 32 bit ppc system build
Then change the following lines of code (OBS server):
Index: buildservice/src/webclient/app/views/project/add_target.rhtml =================================================================== --- buildservice/src/webclient/app/views/project/add_target.rhtml (revision 4179) +++ buildservice/src/webclient/app/views/project/add_target.rhtml (working copy) @@ -20,7 +20,7 @@ </td> <td valign="top"> <b>Architectures:</b><br/> - <% [:i586, :x86_64].each do |arch| %> + <% [:i586, :x86_64, :ppc].each do |arch| %> <%= check_box_tag "arch[#{arch}]", "", true %><%=arch%><br> <% end %> </td>
Then add a project (you can also omit i586/x86_64, if not required) with osc:
<project name="openSUSE:11.0"> <title>openSUSE 11.0 distribution</title> <description>The openSUSE 11.0 distribution.</description> <build> <disable/> </build> <publish> <disable/> </publish> <repository name="standard"> <arch>i586</arch> <arch>x86_64</arch> <arch>ppc</arch> </repository> </project>
Then look for /srv/obs/build/openSUSE:11.0/standard, there should now be the 3 (or only ppc) directories: i586 ppc x86_64 Then you create inside ppc a new directory "ppc/:full", inside there you put the .noarch.rpm and .ppc.rpm.
Then configure the scheduler also for ppc (on the OBS server):
$ cat /etc/sysconfig/obs-server ## Path: Applications/OBS ## Description: define for which architectures the packages should get build ## Type: stringlist ## Default: "i586" ## Config: OBS # # This needs to be a space seperated list of all supported architectures
OBS_SCHEDULER_ARCHITECTURES="i586 x86_64 ppc"
Start the OBS machine, it should indicate a ppc scheduler in the monitor page.
Peter Czanik wrote:
Hello,
Peter Czanik írta:
*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>404 - Not Found</title> </head> <body> <h1>404 - Not Found</h1> </body> </html>
OK, I worked around this. It started to work as soon, as I changed back to 127.0.42.1.
My next problem is: how do I add a repo? When I try based on the README.SETUP I get:
suse8610-110:~ # obs_mirror_project openSUSE:11.0 standard ppc Server returned an error: HTTP Error 404: Not Found project has no architecture 'ppc' /usr/lib/ruby/1.8/rexml/source.rb:149:in `initialize': undefined method `[]' for nil:NilClass (NoMethodError) from /usr/lib/ruby/1.8/rexml/source.rb:16:in `new' from /usr/lib/ruby/1.8/rexml/source.rb:16:in `create_from' from /usr/lib/ruby/1.8/rexml/parsers/baseparser.rb:133:in `stream=' from /usr/lib/ruby/1.8/rexml/parsers/baseparser.rb:110:in `initialize' from /usr/lib/ruby/1.8/rexml/parsers/treeparser.rb:9:in `new' from /usr/lib/ruby/1.8/rexml/parsers/treeparser.rb:9:in `initialize' from /usr/lib/ruby/1.8/rexml/document.rb:205:in `new' from /usr/lib/ruby/1.8/rexml/document.rb:205:in `build' from /usr/lib/ruby/1.8/rexml/document.rb:42:in `initialize' from /usr/sbin/obs_mirror_project:48:in `new' from /usr/sbin/obs_mirror_project:48 suse8610-110:~ #
The other I tried is based on the wiki: crate a project and add a repo. But that does not seem to work either. When I add openSUSE 11.0 I t uses the following URL, which does not mention PPC at all: http://127.0.42.1/project/save_target?arch[i586]=&arch[x86_64]=&platform=openSUSE.org%3AopenSUSE%3A11.0%2Fstandard&project=proba&targetname=openSUSE_11.0
and results in an error anyway: " OpenSUSE Webclient Error:
Error Details: Errorcode: package_save_error Message: error saving project: unable to walk on path 'openSUSE.org:openSUSE:11.0/standard' "
Martin: you mentioned, that you had to modify a few lines in OBS. Where/what? Bye, CzP
--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Martin Mohring wrote:
OK, you have pkgs all at hand, fine.
Then start the OBS, including the scheduler (e.g. ppc scheduler)
Then goto "create project", e.g. http://<your webclient ip>/project/new Give the project the name "openSUSE:11.0". You can leave everthing else blank.
Then put this to a file:
<project name="openSUSE:11.0"> <title>openSUSE 11.0 distribution</title> <description>The openSUSE 11.0 distribution.</description> <person userid="MartinMohring" role="maintainer"/> <person userid="MartinMohring" role="bugowner"/>
Sorry, leave out the two lines with "<person userid=...>", copy and paste from my OBS
<build> <disable/> </build> <publish> <disable/> </publish> <repository name="standard"> <arch>ppc</arch> </repository> </project>
then call:
$ osc -A <your local api ip> meta prj -F <filename you put this in> openSUSE:11.0
Control success by opening http://<your webclient ip>/project/show?project=openSUSE%3A11.0.
Then stop the OBS, install the .noarch.rpm and ppc.rpm inside "/srv/obs/build/openSUSE:11.0/standard/ppc/:full", then restart the OBS and wait some minutes. Anyway, the OBS monitor http://<your local webclient ip>/monitor schould tell you that
ppc: running for 38 minutes (last restart: ....) dispatcher: running for about 1 hour (last restart: ...) publisher: running for about 1 hour (last restart: ...)
these 3 processes are running. You can follow progress by watching the logfiles inside: "/srv/obs/log" directory.
Martin
Peter Czanik wrote:
Hello,
Martin Mohring írta:
Martin Mohring wrote:
Hi,
first you select some ppc distro. Lets assume it is openSUSE 11.0 ppc. You download the packages, e.g. from some mirror server. The description is only for a x86 server and ppc workers.
The reason is: I did not in detail look if all the packages (e.g. ruby rails etc.) all can run on ppc without rebuild for ppc. .noarch.rpm is unproblematic, and scripting like osc is also, athough these packages are packaged for i586/x86_64.
I recompiled all the missing packages on PPC using lbuild without any problems. BTW: there are two rails versions, which is right?
And: the OBS needs ca. 1.5 GB RAM, esp. the scheduler. 512 MB is definitely too small to run OBS Server + Workers.
Well, until now it swapped only 72k when even firefox was running on the machine and I'm already looking for a RAM upgrade. I'd like to keep everything on the same machine - if possible. Bye, CzP
You are running openSUSE 11.0 ppc also on your machine, so you have the .rpm pkgs at hand, dont you?
Then you need to install the following pkgs for openSUSE 11.0 on the x86 machine createrepo deb lzma python-gpgme python-kid python-setuptools repoview yum yum-metadata-parser
Then you install the following pkgs from OBS: build obs-server obs-api obs-worker osc
The ppc workers needs: obs-worker osc - take here the i586 version for a 32 bit ppc system build
Then change the following lines of code (OBS server):
Index: buildservice/src/webclient/app/views/project/add_target.rhtml =================================================================== --- buildservice/src/webclient/app/views/project/add_target.rhtml (revision 4179) +++ buildservice/src/webclient/app/views/project/add_target.rhtml (working copy) @@ -20,7 +20,7 @@ </td> <td valign="top"> <b>Architectures:</b><br/> - <% [:i586, :x86_64].each do |arch| %> + <% [:i586, :x86_64, :ppc].each do |arch| %> <%= check_box_tag "arch[#{arch}]", "", true %><%=arch%><br> <% end %> </td>
Then add a project (you can also omit i586/x86_64, if not required) with osc:
<project name="openSUSE:11.0"> <title>openSUSE 11.0 distribution</title> <description>The openSUSE 11.0 distribution.</description> <build> <disable/> </build> <publish> <disable/> </publish> <repository name="standard"> <arch>i586</arch> <arch>x86_64</arch> <arch>ppc</arch> </repository> </project>
Then look for /srv/obs/build/openSUSE:11.0/standard, there should now be the 3 (or only ppc) directories: i586 ppc x86_64 Then you create inside ppc a new directory "ppc/:full", inside there you put the .noarch.rpm and .ppc.rpm.
Then configure the scheduler also for ppc (on the OBS server):
$ cat /etc/sysconfig/obs-server ## Path: Applications/OBS ## Description: define for which architectures the packages should get build ## Type: stringlist ## Default: "i586" ## Config: OBS # # This needs to be a space seperated list of all supported architectures
OBS_SCHEDULER_ARCHITECTURES="i586 x86_64 ppc"
Start the OBS machine, it should indicate a ppc scheduler in the monitor page.
Peter Czanik wrote:
Hello,
Peter Czanik írta:
*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>404 - Not Found</title> </head> <body> <h1>404 - Not Found</h1> </body> </html>
OK, I worked around this. It started to work as soon, as I changed back to 127.0.42.1.
My next problem is: how do I add a repo? When I try based on the README.SETUP I get:
suse8610-110:~ # obs_mirror_project openSUSE:11.0 standard ppc Server returned an error: HTTP Error 404: Not Found project has no architecture 'ppc' /usr/lib/ruby/1.8/rexml/source.rb:149:in `initialize': undefined method `[]' for nil:NilClass (NoMethodError) from /usr/lib/ruby/1.8/rexml/source.rb:16:in `new' from /usr/lib/ruby/1.8/rexml/source.rb:16:in `create_from' from /usr/lib/ruby/1.8/rexml/parsers/baseparser.rb:133:in `stream=' from /usr/lib/ruby/1.8/rexml/parsers/baseparser.rb:110:in `initialize' from /usr/lib/ruby/1.8/rexml/parsers/treeparser.rb:9:in `new' from /usr/lib/ruby/1.8/rexml/parsers/treeparser.rb:9:in `initialize' from /usr/lib/ruby/1.8/rexml/document.rb:205:in `new' from /usr/lib/ruby/1.8/rexml/document.rb:205:in `build' from /usr/lib/ruby/1.8/rexml/document.rb:42:in `initialize' from /usr/sbin/obs_mirror_project:48:in `new' from /usr/sbin/obs_mirror_project:48 suse8610-110:~ #
The other I tried is based on the wiki: crate a project and add a repo. But that does not seem to work either. When I add openSUSE 11.0 I t uses the following URL, which does not mention PPC at all: http://127.0.42.1/project/save_target?arch[i586]=&arch[x86_64]=&platform=openSUSE.org%3AopenSUSE%3A11.0%2Fstandard&project=proba&targetname=openSUSE_11.0
and results in an error anyway: " OpenSUSE Webclient Error:
Error Details: Errorcode: package_save_error Message: error saving project: unable to walk on path 'openSUSE.org:openSUSE:11.0/standard' "
Martin: you mentioned, that you had to modify a few lines in OBS. Where/what? Bye, CzP
--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Hello, Martin Mohring írta:
Then stop the OBS, install the .noarch.rpm and ppc.rpm inside "/srv/obs/build/openSUSE:11.0/standard/ppc/:full", then restart the OBS
You mean I should put source RPMs there? Bye, CzP --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Hello,
Martin Mohring írta:
Then stop the OBS, install the .noarch.rpm and ppc.rpm inside "/srv/obs/build/openSUSE:11.0/standard/ppc/:full", then restart the OBS
You mean I should put source RPMs there? No, just the normal build binary rpms .noarch.rpm and .ppc.rpm from your opensuse 11.0 mirror (or CD/DVD). I think the final .rpms for opensuse 11.0 are already out, arent they (I mirrored them here)? The OBS needs
Peter Czanik wrote: the binary rpms to build your pkgs against a distro like in this case opensuse 11.0. So not every project needs the sources to be put inside (would be a bit to much work for your node to rebuild all 4k source packages from a complete distro like opensuse 11.0). Also, I forgot to mention that you also have to put the meta data for opensuse 11.0 inside. E.g. do the following: $ osc -A api.opensuse.org meta prjconf openSUSE:11.0 >os110.conf $ osc -A <your local api ip> meta prjconf -F os110.conf openSUSE:11.0 Martin --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Hello, Martin Mohring írta:
And: the OBS needs ca. 1.5 GB RAM, esp. the scheduler. 512 MB is definitely too small to run OBS Server + Workers.
The machine swapped only 150MB at its worst moments, and firefox is also running from there using ssh -X :-) So it does not seem to be a disaster. I have a production server which swaps ~2GB constantly without any real performance penalty... Bye, CzP --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Hello, Martin Mohring írta:
first you select some ppc distro. Lets assume it is openSUSE 11.0 ppc. You download the packages, e.g. from some mirror server.
I have a local mirror of ftp trees for 10.2, 10.3 and 11.0 (yes, I'm also a mirror admin :-) ).
The description is only for a x86 server and ppc workers.
Well, I'll try that next, if ppc server does not work. But it should...
You are running openSUSE 11.0 ppc also on your machine, so you have the .rpm pkgs at hand, dont you?
Yes.
Then you need to install the following pkgs for openSUSE 11.0 on the x86 machine createrepo deb lzma python-gpgme python-kid python-setuptools repoview yum yum-metadata-parser
These are automagically installed as dependencies when installing the obs-* packages.
Then you install the following pkgs from OBS: build obs-server obs-api obs-worker osc
The ppc workers needs: obs-worker osc - take here the i586 version for a 32 bit ppc system build
Then change the following lines of code (OBS server):
I don't see any change, still only i586 and x86_64 are listed, even after restarting everything :-(
Index: buildservice/src/webclient/app/views/project/add_target.rhtml =================================================================== --- buildservice/src/webclient/app/views/project/add_target.rhtml (revision 4179) +++ buildservice/src/webclient/app/views/project/add_target.rhtml (working copy) @@ -20,7 +20,7 @@ </td> <td valign="top"> <b>Architectures:</b><br/> - <% [:i586, :x86_64].each do |arch| %> + <% [:i586, :x86_64, :ppc].each do |arch| %> <%= check_box_tag "arch[#{arch}]", "", true %><%=arch%><br> <% end %> </td>
Then add a project (you can also omit i586/x86_64, if not required) with osc:
What is the full osc command line?
<project name="openSUSE:11.0"> <title>openSUSE 11.0 distribution</title> <description>The openSUSE 11.0 distribution.</description> <build> <disable/> </build> <publish> <disable/> </publish> <repository name="standard"> <arch>i586</arch> <arch>x86_64</arch> <arch>ppc</arch> </repository> </project>
Then look for /srv/obs/build/openSUSE:11.0/standard, there should now be the 3 (or only ppc) directories: i586 ppc x86_64 Then you create inside ppc a new directory "ppc/:full", inside there you put the .noarch.rpm and .ppc.rpm.
Which files do I put there?
Then configure the scheduler also for ppc (on the OBS server):
$ cat /etc/sysconfig/obs-server ## Path: Applications/OBS ## Description: define for which architectures the packages should get build ## Type: stringlist ## Default: "i586" ## Config: OBS # # This needs to be a space seperated list of all supported architectures
OBS_SCHEDULER_ARCHITECTURES="i586 x86_64 ppc"
Start the OBS machine, it should indicate a ppc scheduler in the monitor page.
Bye, CzP
Peter Czanik wrote:
Hello,
Peter Czanik írta:
*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>404 - Not Found</title> </head> <body> <h1>404 - Not Found</h1> </body> </html>
OK, I worked around this. It started to work as soon, as I changed back to 127.0.42.1.
My next problem is: how do I add a repo? When I try based on the README.SETUP I get:
suse8610-110:~ # obs_mirror_project openSUSE:11.0 standard ppc Server returned an error: HTTP Error 404: Not Found project has no architecture 'ppc' /usr/lib/ruby/1.8/rexml/source.rb:149:in `initialize': undefined method `[]' for nil:NilClass (NoMethodError) from /usr/lib/ruby/1.8/rexml/source.rb:16:in `new' from /usr/lib/ruby/1.8/rexml/source.rb:16:in `create_from' from /usr/lib/ruby/1.8/rexml/parsers/baseparser.rb:133:in `stream=' from /usr/lib/ruby/1.8/rexml/parsers/baseparser.rb:110:in `initialize' from /usr/lib/ruby/1.8/rexml/parsers/treeparser.rb:9:in `new' from /usr/lib/ruby/1.8/rexml/parsers/treeparser.rb:9:in `initialize' from /usr/lib/ruby/1.8/rexml/document.rb:205:in `new' from /usr/lib/ruby/1.8/rexml/document.rb:205:in `build' from /usr/lib/ruby/1.8/rexml/document.rb:42:in `initialize' from /usr/sbin/obs_mirror_project:48:in `new' from /usr/sbin/obs_mirror_project:48 suse8610-110:~ #
The other I tried is based on the wiki: crate a project and add a repo. But that does not seem to work either. When I add openSUSE 11.0 I t uses the following URL, which does not mention PPC at all: http://127.0.42.1/project/save_target?arch[i586]=&arch[x86_64]=&platform=openSUSE.org%3AopenSUSE%3A11.0%2Fstandard&project=proba&targetname=openSUSE_11.0
and results in an error anyway: " OpenSUSE Webclient Error:
Error Details: Errorcode: package_save_error Message: error saving project: unable to walk on path 'openSUSE.org:openSUSE:11.0/standard' "
Martin: you mentioned, that you had to modify a few lines in OBS. Where/what? Bye, CzP
--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Hello, Martin Mohring írta:
Currently, you need to have powerpc workers (the compile machines) in order to generate ppc arch compilations. All the repositories/src can handle multiarch right now. Its only that you have to change some lines of code and also have to configure such a mixed setup (able to build x86-32 bit, x86-64 bit and ppc-32 bit, ppc-64 bit). Well, I'm not that interested in x86, as all I want to do is to recompile existing packages from the build.opensuse.org on PPC. As all my machines are 32bit, I suppose, I can only build 32bit packages (which does not really make a difference, as only a couple of database and scientific applications gain anything from 64bit...). BS is up and running now, all what seems to be lacking is arch PPC :-) Bye, CzP
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Hello, Adrian Schröter írta:
On Friday 13 June 2008 13:56:51 Peter Czanik wrote:
- is it possible to check out a project from BS, like KDE4:/Unstable:/Desktop and recompile it locally for PPC in one go? I mean, without needing to compile individual source rpms one by one and needing to figure out the build order...
You can setup your own build service, create source links to our remote instance and compile it at your side. You would just need to import a ppc based distro into some own project first.
I checked the web interface and also the wiki, but I could only find examples for individual packages. How can I link a complete repository in one go? For example everything from KDE:/KDE4:/UNSTABLE:/Desktop/ instead of individual packages in this repo? Bye, CzP --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Peter Czanik wrote:
Hello,
Adrian Schröter írta:
On Friday 13 June 2008 13:56:51 Peter Czanik wrote:
- is it possible to check out a project from BS, like KDE4:/Unstable:/Desktop and recompile it locally for PPC in one go? I mean, without needing to compile individual source rpms one by one and needing to figure out the build order... But not for ppc from the official OBS at the moment.
You can setup your own build service, create source links to our remote instance and compile it at your side. You would just need to import a ppc based distro into some own project first.
I checked the web interface and also the wiki, but I could only find examples for individual packages. How can I link a complete repository in one go? For example everything from KDE:/KDE4:/UNSTABLE:/Desktop/ instead of individual packages in this repo? You can do that, but not for ppc at the moment. The official build.o.o OBS does not provide ppc packages at all.
PS: I am not subscribed to ppc mailing list, so I cannot post there atm. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Hello, Martin Mohring írta:
You can setup your own build service, create source links to our remote instance and compile it at your side. You would just need to import a ppc based distro into some own project first.
I checked the web interface and also the wiki, but I could only find examples for individual packages. How can I link a complete repository in one go? For example everything from KDE:/KDE4:/UNSTABLE:/Desktop/ instead of individual packages in this repo?
You can do that, but not for ppc at the moment. The official build.o.o OBS does not provide ppc packages at all.
That is what I want to do. This was the original reason to get started with BS at all. I don't mind, if the packages end up on my FTP server next to my compilation of the Packman packages and not in the BS for now. But I don't want to compile packages one by one with Packman, but do it automated, that is the whole idea of the BS. So, what I would like to do is to import repositories from build.o.o, compile them on PPC, and publish them somewhere, so I could provide the PPC community not only with the most important Packman packages, but also with some of the most interesting BS repositories. Bye, CzP --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Hello,
Martin Mohring írta:
You can setup your own build service, create source links to our remote instance and compile it at your side. You would just need to import a ppc based distro into some own project first.
I checked the web interface and also the wiki, but I could only find examples for individual packages. How can I link a complete repository in one go? For example everything from KDE:/KDE4:/UNSTABLE:/Desktop/ instead of individual packages in this repo?
You can do that, but not for ppc at the moment. The official build.o.o OBS does not provide ppc packages at all.
That is what I want to do. This was the original reason to get started with BS at all. I don't mind, if the packages end up on my FTP server next to my compilation of the Packman packages and not in the BS for now. But I don't want to compile packages one by one with Packman, but do it automated, that is the whole idea of the BS. So, what I would like to do is to import repositories from build.o.o, compile them on PPC, and publish them somewhere, so I could provide the PPC community not only with the most important Packman packages, but also with some of the most interesting BS repositories. I am not sure what you mean. The OBS can be used to build a complete
Peter Czanik wrote: project without manually doing dependencies and without installing all the pkgs all the time. And a local OBS is used if you want: - some local projects not published - use it in a way the original OBS is not configured yet (e.g. ppc) - use an own codebase for OBS - do not have any other restriction currently imposed But a local OBS needs compute power to do the compile jobs, the more packages you want to compile at a time the better. Do you mean the remoteurl feature (e.g. reference a remote OBS system). The problem with remote projects and build.o.o is that the main OBS currently does not support ppc. Martin --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Hello, First of all: I just finished my first compile, thanks for all the help! It is 'mad' from PackMan, this is always the first software I compile for a new release :-) Martin Mohring írta:
- use it in a way the original OBS is not configured yet (e.g. ppc)
This is exactly what I want: recompile projects for PPC.
But a local OBS needs compute power to do the compile jobs, the more packages you want to compile at a time the better.
The MPC8610 I use is quite powerful, at least for a 32bit PPC machine. And it will be even better, when I move the server to another machine and add some RAM.
Do you mean the remoteurl feature (e.g. reference a remote OBS system). The problem with remote projects and build.o.o is that the main OBS currently does not support ppc.
Even if I have PPC locally? Then can I check out a project from the build.o.o, check it in locally and rebuild? That would be still better, than to build each package in a project by hand... Bye, CzP --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Hello,
First of all: I just finished my first compile, thanks for all the help! It is 'mad' from PackMan, this is always the first software I compile for a new release :-) Congratulations.
Martin Mohring írta:
- use it in a way the original OBS is not configured yet (e.g. ppc)
This is exactly what I want: recompile projects for PPC. Then we head for the right way.
But a local OBS needs compute power to do the compile jobs, the more packages you want to compile at a time the better.
The MPC8610 I use is quite powerful, at least for a 32bit PPC machine. And it will be even better, when I move the server to another machine and add some RAM. Was just asking...
Do you mean the remoteurl feature (e.g. reference a remote OBS system). The problem with remote projects and build.o.o is that the main OBS currently does not support ppc.
Even if I have PPC locally? Then can I check out a project from the build.o.o, check it in locally and rebuild? That would be still better, than to build each package in a project by hand... remoteurl is just a feature to remotely address the binary packages and
Peter Czanik wrote: the meta data in a project (e.g. you do not need to keep all the compiled pkgs for Debian, Fedora, RHEL, SLES etc on you local OBS, but you can compile against such a project). We discussed with Adrian already about putting also the ppc binaries on there server. He replied that it is intention to move the complete openSUSE Distro development to the OBS, which means they need to provide the complete service for ppc also on the build.o.o server. So providing the current distros with ppc binaries would not help very much, they also need a ppc compile cluster with appropriate power (the current x86 cluster has 128 compile nodes of AMD Opteron power - the ppc machine would need about the same). But I can provide you with a tool to copy complete projects with meta data from one OBS to another. I will send you in a separate e-mail. Martin --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Martin Mohring írta:
So providing the current distros with ppc binaries would not help very much, they also need a ppc compile cluster with appropriate power (the current x86 cluster has 128 compile nodes of AMD Opteron power - the ppc machine would need about the same).
Just to get a picture: are we talking original ~1.5GHz kind of Opterons or Dual Core 2.5GHz ones or Quad core 2.0GHz ones? Does 'node' refer to a complete machine or to a CPU core?
But I can provide you with a tool to copy complete projects with meta data from one OBS to another. I will send you in a separate e-mail.
Wow, thanks! So I'll be able to copy for example Education:/desktop from build.o.o and rebuild it for PPC. What happens if a software gets updated in the remote OBS? Is there an easy way to sync projects and only rebuild software when necessary? Staying with the above example: if only gcompris is updated, do I have to recompile only that or everything on the next copy? Bye, CzP --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Wednesday 18 June 2008 13:24:13 Peter Czanik wrote:
Martin Mohring írta:
So providing the current distros with ppc binaries would not help very much, they also need a ppc compile cluster with appropriate power (the current x86 cluster has 128 compile nodes of AMD Opteron power - the ppc machine would need about the same).
Just to get a picture: are we talking original ~1.5GHz kind of Opterons or Dual Core 2.5GHz ones or Quad core 2.0GHz ones? Does 'node' refer to a complete machine or to a CPU core?
But I can provide you with a tool to copy complete projects with meta data from one OBS to another. I will send you in a separate e-mail.
Wow, thanks! So I'll be able to copy for example Education:/desktop from build.o.o and rebuild it for PPC. What happens if a software gets updated in the remote OBS? Is there an easy way to sync projects and only rebuild software when necessary? Staying with the above example: if only gcompris is updated, do I have to recompile only that or everything on the next copy?
You can simply create source links to projects on remote systems. This needs to be done for each package atm, but we will project source links in future as well. Via this your service gets automatically notified on changes. -- Adrian Schroeter SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) email: adrian@suse.de --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Peter Czanik wrote:
Martin Mohring írta:
So providing the current distros with ppc binaries would not help very much, they also need a ppc compile cluster with appropriate power (the current x86 cluster has 128 compile nodes of AMD Opteron power - the ppc machine would need about the same).
Just to get a picture: are we talking original ~1.5GHz kind of Opterons or Dual Core 2.5GHz ones or Quad core 2.0GHz ones? Does 'node' refer to a complete machine or to a CPU core? One node at build.o.o is one single opteron core (since it used XEN virtualization, you do not exactly see the real hw behind). Maybe Adrian is willing to tell. I use 6 workers in the local OBS (2 x ppc 64 bit and 4 x x86-64 bit opteron cores). The storage is on another single x86-64 machine.
But I can provide you with a tool to copy complete projects with meta data from one OBS to another. I will send you in a separate e-mail.
Wow, thanks! So I'll be able to copy for example Education:/desktop from build.o.o and rebuild it for PPC. What happens if a software gets updated in the remote OBS? Is there an easy way to sync projects and only rebuild software when necessary? Staying with the above example: if only gcompris is updated, do I have to recompile only that or everything on the next copy? See my mail. Its OBS, so it recompiles only when changed.
Susanne said I should provide the script inside tools in OBS svn repository. I will before do some cosmetics. Martin --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Hello, Martin Mohring írta:
But I can provide you with a tool to copy complete projects with meta data from one OBS to another. I will send you in a separate e-mail.
Wow, thanks! So I'll be able to copy for example Education:/desktop from build.o.o and rebuild it for PPC. What happens if a software gets updated in the remote OBS? Is there an easy way to sync projects and only rebuild software when necessary? Staying with the above example: if only gcompris is updated, do I have to recompile only that or everything on the next copy?
See my mail. Its OBS, so it recompiles only when changed.
Susanne said I should provide the script inside tools in OBS svn repository. I will before do some cosmetics.
Thanks, I tested it and works. It would be nice, if it would print some help text, if started without any parameters. This script also brought up a new round of questions :-) I tested it with the LCD project, as I plan to buy a little LCD when I got a bit more time to play with it. It seems to me, that the local build service is more strict, than the one used on build.o.o. Some of the packages (nxml, libftdi) compiled without any problem, but 'failed' after all, due to RPMLINT. Is it possible to turn rpmlint off, or make it less strict? This way third of the packages failed due to expansion error. Another problem is libetpan11. It is a link to libetpan11 in openSUSE:Factory. I only have openSUSE:11.0 and that has libetpan13, so I rewrote the link. It still did not work. I looked at openSUSE:11.0 and found this: suse8610-110:~ # osc ls openSUSE:11.0 suse8610-110:~ # All binaries are there in /srv/obs/build/openSUSE:11.0/standard/ppc/:full , including libetpan13. Does it fail, because these are just the binaries, but build data (like sources, spec files) are missing from this repo? And a bonus: it was not the case with the LCD packages, but the one I uploaded from PackMan (mad) had an interesting side effect: suse8610-110:/srv/obs/repos/bla/standard # find . | grep mad ./ppc/mad-devel-0.15.1b-1.1.ppc.rpm ./ppc/mad-0.15.1b-1.1.ppc.rpm ./src/mad-0.15.1b-1.1.src.rpm ./ppc64/mad-32bit-0.15.1b-1.1.ppc64.rpm Why was this last package (./ppc64/mad-32bit-0.15.1b-1.1.ppc64.rpm) created here, and not for the other packages? Actually, I would like to turn it off completely, as generating these packages without the 64bit version does not make any sense. And as my build machine is 32bit, I can't build 64bit packages... Bye, CzP --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
participants (3)
-
Adrian Schröter
-
Martin Mohring
-
Peter Czanik