July 2012 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] Open Build Service(OBS) 2.3.3 released
by Adrian Schröter 11 Jul '12

11 Jul '12

Open Build Service(OBS) 2.3.3 just got released =============================================== This is a pure bugfix release. It fixes an issue when using project links to remote instances and the diff support of requests when the source got cleaned up on accept. Also a regression from 2.3.2 when running an appliance the first time got fixed. OBS 2.3.2 is published in "openSUSE:Tools" project: http://download.opensuse.org/repositories/openSUSE:Tools/ Appliances can be used as usual: http://en.opensuse.org/openSUSE:Build_Service_Appliance Release Notes: ============== Updaters from any OBS 2.3 release can just ugrade the packages and restart all services. Updaters from former releases should read the README.UPDATERS file. Feature backports: ================== * none Changes: ======== * none Bugfixes: ========= * Fix initial database setup on appliances (regression in 2.3.2) * New packages got not detected, when using project project links to a remote OBS instance. Either a scheduler cold start is needed or an # obs_admin --deep-check-project ... for a propper recalculation of the project. * Request diffs were broken when the source got removed. * removed a sleep on each package build -- Adrian Schroeter SUSE Linux Products GmbH email: adrian(a)suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0

[opensuse-buildservice] [gsoc] osc2 client - summary of week 7
by Marcus Hüwe 11 Jul '12

11 Jul '12

Hi, here's a small summary of the 7th (coding) week. Last week I was really busy with university stuff (it was the second last week in the lecture period so I had to recap quite some stuff) and didn't manage to work much on the GSoC project. I'm going work off the TODO this weekend. Marcus -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0

[opensuse-buildservice] build-test.opensuse.org
by Adrian Schröter 10 Jul '12

10 Jul '12

Hi, JFYI, we have now a test instance of OBS running our current openSUSE:Tools:Unstable (git master branch) packages. Everybody can connect and browse there. You can even login with your standard credentials, however by default your account will be unconfirmed and not be able to create your home project. You can ask for getting a confirmed account when you want to test something there. However, the data on this instance can * go away at any time without any warning * build results do not get publish at an public available place. Analog the api exists also as api-test.opensuse.org . Kudos to coolo and Max for getting the instance up. We hope that we can switch soon to git master also with our productive instance. The biggest gripes we have are some webui regressions, but you may want to browse on our test instance and give use feedback about the new interfaces. bye adrian -- Adrian Schroeter SUSE Linux Products GmbH email: adrian(a)suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0

[opensuse-buildservice] Rebuild time broken in OBS 2.3.1
by Malcolm Fernandes 09 Jul '12

09 Jul '12

We are using a local OBS instance (2.3.1 appliance) and the rebuild_time feature seems to be broken when we upgraded from OBS 2.1. It worked for us in OBS 2.1 We have the perl-GD rpms installed. >From the webui production.log file, I see these errors: [ERROR|# 9687] rescue_action: caught Errno::ENOENT: No such file or directory - /tmp/d20120705-9687-11cssor/rebuild.png [INFO |# 9687] Rendering template within layouts/application [INFO |# 9687] Rendering error (400) [FATAL|# 9687] /!\ FAILSAFE /!\ Thu Jul 05 14:19:02 -0700 2012 Status: 500 Internal Server Error Mysql::Error: MySQL server has gone away: UPDATE `sessions` SET `data` = 'BAh7CjoKbG9naW4iDW1mZXJuYW5kOhBtb2JpbGVfdmlld0Y6C3Bhc3N3ZCIN\nbWZlcm5hbmQ6EF9jc3JmX3Rva2VuIjFNbGtaYTBybnZ6Ukpka3M4UXUyWmpX\nbEVwb3RDaWpVMnAzK2pRWU4yZ080PSIKZmxhc2hJQzonQWN0aW9uQ29udHJv\nbGxlcjo6Rmxhc2g6OkZsYXNoSGFzaHsABjoKQHVzZWR7AA==\n', `updated_at` = '2012-07-05 14:19:02' WHERE `id` = 4383 /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.14/lib/active_record/connection_adapters/abstract_adapter.rb:227:in `log' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.14/lib/active_record/connection_adapters/mysql_adapter.rb:324:in `execute' .... I tried running the rebuild time on the build.opensuse.org site and it does not produce the rebuild graph, it just states the rebuildtime and the longest paths. https://build.opensuse.org/project/rebuild_time?arch=x86_64&project=openSUS… Thanks, Mal -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 2

[opensuse-buildservice] obs services idle
by doiggl＠velocitynet.com.au 07 Jul '12

07 Jul '12

Hello, Today I noticed many obs services idle [1] https://build.opensuse.org/monitor/old Packages in waiting queue=0 and Packages in blocked queue=42. Question - Why 'Packages in waiting queue' not equal to 'Packages in blocked queue', when all unblocked Packages are built ? Cheers Glenn [1] Host Arch Packages in waiting queue Packages in blocked queue Average Job time i586 0 35 13 minutes x86_64 0 42 19 minutes Idle hosts 242 of 324 hosts idle. Host Arch build02/1 x86_64 build02/2 x86_64 build02/3 x86_64 build02/4 x86_64 build02/5 x86_64 build02/6 x86_64 build02/7 x86_64 build04/3 x86_64 build04/4 x86_64 build04/5 x86_64 build06/2 x86_64 build06/4 x86_64 build06/5 x86_64 build06/7 x86_64 build08/1 x86_64 build08/10 x86_64 build08/2 x86_64 build08/3 x86_64 build08/4 x86_64 build08/5 x86_64 build08/6 x86_64 build08/7 x86_64 build08/8 x86_64 build08/9 x86_64 build09/1 x86_64 build09/10 x86_64 build09/2 x86_64 build09/3 x86_64 build09/4 x86_64 build09/5 x86_64 build09/6 x86_64 build09/7 x86_64 build09/8 x86_64 build09/9 x86_64 build10/1 x86_64 build10/2 x86_64 build10/3 x86_64 build10/4 x86_64 build10/5 x86_64 build10/6 x86_64 build10/7 x86_64 build10/8 x86_64 build11/2 x86_64 build11/3 x86_64 build11/4 x86_64 build11/5 x86_64 build11/6 x86_64 build11/7 x86_64 build11/8 x86_64 build12/1 x86_64 build12/2 x86_64 build12/3 x86_64 build12/4 x86_64 build12/6 x86_64 build12/7 x86_64 build12/8 x86_64 build13/1 x86_64 build13/2 x86_64 build13/4 x86_64 build13/5 x86_64 build13/6 x86_64 build13/7 x86_64 build13/8 x86_64 build14/1 x86_64 build14/2 x86_64 build14/5 x86_64 build14/6 x86_64 build14/7 x86_64 build14/8 x86_64 build15/1 x86_64 build15/2 x86_64 build15/3 x86_64 build15/4 x86_64 build15/5 x86_64 build17/1 x86_64 build17/2 x86_64 build17/3 x86_64 build17/4 x86_64 build17/5 x86_64 build17/6 x86_64 build17/7 x86_64 build17/8 x86_64 build18/1 x86_64 build18/3 x86_64 build18/4 x86_64 build18/5 x86_64 build18/6 x86_64 build18/7 x86_64 build18/8 x86_64 build19/1 x86_64 build19/2 x86_64 build19/3 x86_64 build19/4 x86_64 build19/5 x86_64 build19/6 x86_64 build20/1 x86_64 build20/10 x86_64 build20/12 x86_64 build20/13 x86_64 build20/14 x86_64 build20/16 x86_64 build20/2 x86_64 build20/3 x86_64 build20/4 x86_64 build20/5 x86_64 build20/6 x86_64 build20/7 x86_64 build20/8 x86_64 build20/9 x86_64 build21/1 x86_64 build21/10 x86_64 build21/11 x86_64 build21/12 x86_64 build21/14 x86_64 build21/15 x86_64 build21/16 x86_64 build21/2 x86_64 build21/3 x86_64 build21/4 x86_64 build21/6 x86_64 build21/7 x86_64 build21/8 x86_64 build23/1 x86_64 build23/10 x86_64 build23/12 x86_64 build23/13 x86_64 build23/14 x86_64 build23/15 x86_64 build23/16 x86_64 build23/2 x86_64 build23/3 x86_64 build23/4 x86_64 build23/7 x86_64 build23/8 x86_64 build23/9 x86_64 build24/1 x86_64 build24/10 x86_64 build24/12 x86_64 build24/13 x86_64 build24/15 x86_64 build24/16 x86_64 build24/2 x86_64 build24/3 x86_64 build24/4 x86_64 build24/5 x86_64 build24/6 x86_64 build24/7 x86_64 build24/8 x86_64 build24/9 x86_64 build26/1 x86_64 build26/10 x86_64 build26/11 x86_64 build26/12 x86_64 build26/13 x86_64 build26/14 x86_64 build26/15 x86_64 build26/16 x86_64 build26/2 x86_64 build26/3 x86_64 build26/4 x86_64 build26/5 x86_64 build26/8 x86_64 build27/1 x86_64 build27/10 x86_64 build27/11 x86_64 build27/12 x86_64 build27/13 x86_64 build27/14 x86_64 build27/16 x86_64 build27/2 x86_64 build27/3 x86_64 build27/4 x86_64 build27/5 x86_64 build27/6 x86_64 build27/7 x86_64 build27/8 x86_64 build27/9 x86_64 build30/1 x86_64 build30/10 x86_64 build30/11 x86_64 build30/12 x86_64 build30/3 x86_64 build30/5 x86_64 build30/6 x86_64 build30/7 x86_64 build30/8 x86_64 build30/9 x86_64 build31/1 x86_64 build31/11 x86_64 build31/12 x86_64 build31/2 x86_64 build31/3 x86_64 build31/5 x86_64 build31/6 x86_64 build31/7 x86_64 build31/8 x86_64 build31/9 x86_64 build32/1 x86_64 build32/10 x86_64 build32/11 x86_64 build32/12 x86_64 build32/2 x86_64 build32/3 x86_64 build32/5 x86_64 build32/6 x86_64 build32/8 x86_64 build32/9 x86_64 build33/1 x86_64 build33/11 x86_64 build33/12 x86_64 build33/2 x86_64 build33/3 x86_64 build33/4 x86_64 build33/5 x86_64 build33/6 x86_64 build33/7 x86_64 build33/8 x86_64 build34/10 x86_64 build34/11 x86_64 build34/12 x86_64 build34/2 x86_64 build34/3 x86_64 build34/5 x86_64 build34/6 x86_64 build34/7 x86_64 build34/8 x86_64 build34/9 x86_64 build35/1 x86_64 build35/10 x86_64 build35/11 x86_64 build35/12 x86_64 build35/2 x86_64 build35/3 x86_64 build35/4 x86_64 build35/5 x86_64 build35/6 x86_64 build35/7 x86_64 build35/8 x86_64 build35/9 x86_64 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 1

[opensuse-buildservice] OBS private instance: download on demand trouble
by Martin Weber 07 Jul '12

07 Jul '12

Hi all, I have set up a company-wide yum repository which contains non-free third-party rpms. Following <http://web.archiveorange.com/archive/v/6r2m99UGJvpq5Wh5EajT>, I created a project to download these third party rpms in order to use them to build our own packages. The DoD configuration seems to be correct, the file :fill.solv ist created. But the scheduler log always shows a 'bad config' for that repo and the build of our own packages fails with unresolved packages from the DoD project. My guess is that the the resolution errors are caused by some kind of architecture mismatch: The third-party rpms are build for CentOS and have an arch=i386, whereas the arch in the DoD project is set to arch="i586" (since OBS complains when I set arch=i386). Is there anybody to confirm that? How do I set up DoD to work with CentOS repositories? TIA, Martin -- E-Mails sollten Text sein, Text und nur Text. Wenn Gott gewollt hätte, dass E-Mails in HTML geschrieben würden, endeten Gebete traditionell mit </amen>. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 3

[opensuse-buildservice] Installing local obs 2.3.2 getting problem connectiong to remote project via https://api.opensuse.org/public?
by Christian Nilsson 06 Jul '12

06 Jul '12

Hi all! So I'm struggling with the installation of obs 2.3.2 (from rpm packages). I have followed the /usr/share/doc/packages/obs-api/README.SETUP Now i have come to the point: 4.1 Reuse projects hosted on openSUSE.org build service So have done this: #curl -x "" -0 --user "Admin:opensuse" -X PUT -T /usr/share/doc/packages/obs-api/openSUSE.org.xml https://localhost:444 /source/openSUSE.org/_meta --insecure <?xml version="1.0" encoding="UTF-8"?> <status code="ok"> <summary>Ok</summary> <details></details> </status> Seems to work.. Then i try to "Branch package from other project" into my home project. Name of original project: openSUSE.org:openSUSE:11.4 Name of package in original project: at and then i press "Create Branch" button. after a while i get an error message: OBS Web Interface Error: Error Details: Errorcode: 400 Message: connect to api.opensuse.org:443: Connection timed out I have also tried to insert https://username:password@api.opensuse.org in /usr/share/doc/packages/obs-api/openSUSE.org.xml before posting it however same problem. I'm sitting behind a http proxy thats why i do -x on curl. In the /srv/obs/log/scheduler_i586.log i see this: <snip> updating meta for project 'openSUSE.org' from http://<my.hostname.domain>:5352 calculating project dependencies... sorting projects and repositories... fetching remote project data for openSUSE.org:openSUSE:11.4 connect to api.opensuse.org:443: Connection timed out </snip> Does anyone have any idea of what i'm doing wrong? Thanks Christian Nilsson -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 8

[opensuse-buildservice] x86_64 DVD iso build process broken ?
by doiggl＠velocitynet.com.au 05 Jul '12

05 Jul '12

Hello, The last build of the openSUSE-DVD-i586 is dated 02-Jul-2012 and the last build of the openSUSE-DVD-x86_64 is 28-Jun-2012 Details [1],[2]. Questions: - Can the build for the openSUSE-DVD-x86_64 series be fixed please. - What broke the x86_64 DVD iso build process ?. Sourced from [3] Thanks Glenn [1] openSUSE-DVD-i586-Build0009-Media.iso 02-Jul-2012 06:12 4.2G [2] openSUSE-DVD-x86_64-Build0002-Media.iso 28-Jun-2012 4.3G [3] http://openqa.opensuse.org/opensuse/www/htdocs/openqa/factory/iso/ -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0

[opensuse-buildservice] Problem with local install of obs: Errorcode: 503 Message: Unable to connect to API host. (localhost)
by Christian Nilsson 04 Jul '12

04 Jul '12

Hi all! I'm trying out the OBS for a customer and have tested the public opensuse build service which looks promising. However now I wan't to install it locally for different reasons. I have followed the "OBS 1 click install on SLES(SUSE Linux Enterprise Server) 11" (I'm installing on SLED 11 SP1) from http://www.open-build-service.org. The versions that i have tried is 1.7 and now also 2.3.2 but with same results. I have not changed anything from the defaults and only trying to reach the server from localhost. However when i login to the webui i get the error message "Errorcode: 503 Message: Unable to connect to API host. (localhost)" and in the /srv/www/obs/webui/log/production.log (obs! i have removed my ip adress from the snip <my ip>) : <snip> [^[[32mINFO ^[[0m|#28023] Processing MainController#index (for <my ip> at 2012-07-04 07:55:02) [GET] [^[[32mINFO ^[[0m|#28023] Parameters: {"action"=>"index", "controller"=>"main"} [^[[32mINFO ^[[0m|#28023] Anonymous request to / [^[[31mERROR^[[0m|#28023] Couldn't finish http connection: HTTP session not yet started [^[[31mFATAL^[[0m|#28023] ActiveXML::Transport::ConnectionError (Failed to establish connection for http://localhost:81/configuration.json: Connection refused - connect(2)): lib/activexml/transport.rb:523:in `http_do' lib/activexml/transport.rb:391:in `direct_http' app/controllers/application_controller.rb:423:in `require_configuration' app/controllers/application_controller.rb:422:in `require_configuration' </snip> When I go to the https://localhost:444 it works fine after logging in with the Admin user. If there Is someone who knows how to fix this I would be grateful! Thanks! Christian Nilsson -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 2

[opensuse-buildservice] [gsoc] osc2 client - summary of week 6
by Marcus Hüwe 03 Jul '12

03 Jul '12

Hi here's a small summary of the 6th (coding) week. Last week I continued working on the build module and developed a concept for the package fetcher (and discussed some parts with darix:) ). The main idea is to modularize the fetcher code, verify code etc. Thus we have a fetcher class which takes care of retrieving the packages. The fetcher class utilizes a "cache manager" which takes care of storing the fetched packages on the filesystem. The goal is that at some point in time one can exchange the "simple" cache manager with a more "clever" cache manager (which for instance cleans up the cache from time to time or only allows exactly one version of a package in the cache etc.). In order to achieve this no code in the fetcher has to be touched - instead it's sufficient to pass a different cache manager object to the fetcher. Additionally the fetcher provides some hooks like pre, pre_fetch, post_fetch and post. For instance a post_fetch hook can be used to verify the just fetched package etc. TODO: - write testcases and implement the concept from above If you have questions, suggestions etc. feel free to contact me:) Marcus -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0