August 2010 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] OBS and the competition
by Andreas Jaeger 24 Aug '10

24 Aug '10

I'd like to look a little bit out of the box and would like your help ;) What other software is available that can be compared with the openSUSE Build Service? I'm aware of Project Builder, Fedora Koji, Ubuntu Launchpad (Soyuz extended by groundcontrol). Which ones would you compare it with and how do they compare with OBS? Which features do you consider unique to OBS? My top three are: * Building for multiple distributions * Automatic rebuilding on dependency change * Open System – nice integration with IDEs, Forges and tools thanks for any comments, Andreas -- Andreas Jaeger, Program Manager openSUSE, aj(a){novell.com,opensuse.org} Twitter: jaegerandi | Identica: jaegerandi SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

3 3

[opensuse-buildservice] Build Team Meeting
by Adrian Schröter 24 Aug '10

24 Aug '10

present: mhuewe, coolo, mls, adrian, freitag Topics: * Status round * OBS 2.1 * scheduler blocked mode handling Status Round ============ adrian: * Worked on improving webui source handling. Also submit request creation is possible now. This offers simple wiki style source changes, esp. for non-technical users (who may still want to fix things like package descriptions) and for simple tasks without a local checkout. => to be presented via web cast after improving the ui a bit more. * OBS backend databases were corrupt after filesystem corruption ( caused by san storage failure ). Request db got restored, publish database still broken. source db to be checked. mhuewe: Welcome Marcus Huewe to his 1-month internship at Novell :) * Creating a test suite for osc * rewriting osc update handling (to avoid broken local data on abort in process) freitag: * Visited FrosCon, feedback was that it should be easier to not publish stuff => discussed we need to offer more pre set options on creating projects, needed * Worked on "Connect" as replacement for users.o.o. We discussed if this could be used by build.o.o to host all user related data and for authentification. In short, yes it can, but we must not loose plain http authentification via api (without openid-redirection handling need in client). Also openSUSE:Factory contributors may still need a novell account to keep the connection to bugzilla. OBS 2.1 ======= OBS 2.1 is behind the schedule and currently still in alpha state. Agreement in the MeeGo-OBS group was to focus only on source read-permission handling for 2.1 release. binary read-permission handling has to wait for 2.2 release. Scheduler blocked mode handling =============================== Adrian implemented a job cancel action with active build job kill when a job is switching back to blocked. We discussed that this may have bad impact during boot strap esp. We agree to modify the code to * remove only not active running jobs (scheduled, not building) * remove also jobs where package switched to "disabled" -- Adrian Schroeter SUSE Linux Products GmbH email: adrian(a)suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 0

[opensuse-buildservice] copying package files from one project to another?
by Robert Xu 24 Aug '10

24 Aug '10

Hi all, Don't know if I asked before, since my Gmail seems to be having problems. How can I copy package files - everything, such as the project config, the key, the built rpms over to another project (like copying opensuse:factory to opensuse:11.2 or something)? Is it just copying directories in /srv/obs/{repos,build,projects,sources}? Or do I have to run a script to do this/finish this? -- later, Robert Xu -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 2

[opensuse-buildservice] verify_file service fails
by Cristian Morales Vega 24 Aug '10

24 Aug '10

>From home:RedDwarf/libmms: service verify_file /root/bs/call-service-in-lxc.sh /usr/lib/obs/service//verify_file --file _service:download_url:libmms-0.6.tar.gz --verifier sha256 --checksum 1f894f33b5e0334bd7c75343480bdf3a9cf79232aa92085c03f1a67e7d4ceb9d --outdir /opt/ss//1013/.tmp failed: 'obs.service.jail.1051' does not exist 'obs.service.jail.1051' created lxc-start: failed to move '(null)' to the container lxc-start: failed to create the configured network lxc-start: failed to spawn '/lxc.tmp/inner.sh' lxc-start: Device or resource busy - failed to remove cgroup '/cgroup/obs.service.jail.1051' It failed four times. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 1

[opensuse-buildservice] change repository name?
by Robert Xu 23 Aug '10

23 Aug '10

Hi all, In OBS 1.7 it was easy to change the name of the repository. Is there any way to mimic that function in OBS 2.0? (I can't just change it in the Raw Config; It will be treated like a new repository) -- later, Robert Xu -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 1

[opensuse-buildservice] approved repository
by Kai-Uwe Behrmann 23 Aug '10

23 Aug '10

How to become a approved repository? Or is there already a repository around colour management packages? Background: the home:bekun [1] repository contains many colour management packages. But a search on openSUSE.org does not show them by default. One has to tweak search options before. After creating a LiveCD [2] I think the repository works out of the box :-) (ok, the later is tested only on two intel/nvidia machines) Now, what are the details to get a approved status or be recommended for openSUSE or any other distribution for colour management? kind regards Kai-Uwe Behrmann -- developing for colour management www.behrmann.name + www.oyranos.org PS: I am involved in most of the provided packages. [1] https://build.opensuse.org/project/packages?project=home%3Abekun [2] http://susegallery.com/a/8Kr6tw/oyranos -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 2

[opensuse-buildservice] Re: [PATCH] [testsuite] corrected two testcases with ACL
by Adrian Schröter 23 Aug '10

23 Aug '10

That broke it: 1) Failure: test_get_projectlist_with_hidden_project(SourceControllerTest) [/test/functional/source_controller_test.rb:20]: </entry name="HiddenProject"/> expected to not match <"<directory count=\"24\">\n <entry name=\"Apache\"/>\n <entry name=\"BaseDistro\"/>\n <entry name=\"BaseDistro2\"/>\n <entry name=\"BaseDistro2:LinkedUpdateProject\"/>\n <entry name=\"BaseDistro3\"/>\n <entry name=\"BaseDistro:Update\"/>\n <entry name=\"BinaryprotectedProject\"/>\n <entry name=\"deleted\"/>\n <entry name=\"HiddenProject\"/>\n <entry name=\"home:adrian:BaseDistro\"/>\n <entry name=\"home:coolo\"/>\n <entry name=\"home:coolo:test\"/>\n <entry name=\"home:dmayr\"/>\n <entry name=\"home:Iggy\"/>\n <entry name=\"home:Iggy:branches:kde4\"/>\n <entry name=\"home:Iggy:OldProject\"/>\n <entry name=\"home:tom\"/>\n <entry name=\"kde\"/>\n <entry name=\"kde4\"/>\n <entry name=\"LocalProject\"/>\n <entry name=\"RemoteInstance\"/>\n <entry name=\"SourceprotectedProject\"/>\n <entry name=\"UseRemoteInstance\"/>\n <entry name=\"ViewprotectedProject\"/>\n</directory>\n">. And please speak about the correct access kind. The ACL implementation is not touched at all since a long time. It is the same ACL implementation for write and read access. On Monday 23 August 2010 14:13:56 OBS build-service wrote: > From: Martin Mohring <martinmohring(a)linuxfoundation.org> > > --- > src/api/test/functional/source_controller_test.rb | 8 ++++---- > 1 files changed, 4 insertions(+), 4 deletions(-) > > diff --git a/src/api/test/functional/source_controller_test.rb b/src/api/test/functional/source_controller_test.rb > index 1603f89..1086554 100644 > --- a/src/api/test/functional/source_controller_test.rb > +++ b/src/api/test/functional/source_controller_test.rb > @@ -13,11 +13,11 @@ class SourceControllerTest < ActionController::IntegrationTest > :children => { :only => { :tag => "entry" } } > end > > - def test_get_projectlist_read_acces_forbidden_project > + def test_get_projectlist_with_hidden_project > prepare_request_with_user "tom", "thunder" > get "/source" > assert_response :success > - assert_no_match /entry name="HiddenProject"/, @response.body if $ENABLE_BROKEN_TEST > + assert_no_match /entry name="HiddenProject"/, @response.body > #retry with maintainer > ActionController::IntegrationTest::reset_auth > prepare_request_with_user "adrian", "so_alone" > @@ -26,12 +26,12 @@ class SourceControllerTest < ActionController::IntegrationTest > assert_match /entry name="HiddenProject"/, @response.body > end > > - def test_get_projectlist_with_hidden_project > + def test_get_projectlist_with_privacy_protected_project > # visible, but no sources > prepare_request_with_user "tom", "thunder" > get "/source" > assert_response :success > - assert_match /entry name="ViewprotectedProject"/, @response.body if $ENABLE_BROKEN_TEST > + assert_match /entry name="ViewprotectedProject"/, @response.body > #retry with maintainer > ActionController::IntegrationTest::reset_auth > prepare_request_with_user "adrian", "so_alone" > -- Adrian Schroeter SUSE Linux Products GmbH email: adrian(a)suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 0

[opensuse-buildservice] [PATCH] Graphs in monitor page overflow from the main content area
by Srinidhi B 23 Aug '10

23 Aug '10

Hi, In the OBS (2.0.5) monitor page, the graphs overflow from the main content area: https://build.opensuse.org/monitor Here's a small patch to define correct width and height so that they stay inside the content area. Srinidhi. diff --git a/src/webui/app/views/monitor/_graphs_arch.rhtml b/src/webui/app/views/monitor/_graphs_arch.rhtml index f9f0eb5..9d98455 100644 --- a/src/webui/app/views/monitor/_graphs_arch.rhtml +++ b/src/webui/app/views/monitor/_graphs_arch.rhtml @@ -2,15 +2,15 @@ <h1><%= title %></h1> <ul class="monitorgraphs"> <li> -<img class="monitorplot" src="<%= url_for(:controller => :monitor, :action => :plothistory, :set => prefix + 'waiting', :range => 24, :time => Time.now.to_i ) %>" alt='Waiting' width="400" height="300"/> +<img class="monitorplot" src="<%= url_for(:controller => :monitor, :action => :plothistory, :set => prefix + 'waiting', :range => 24, :time => Time.now.to_i ) %>" alt='Waiting' width="300" height="250"/> <span>Waiting to build</span> </li> <li> -<img class="monitorplot" src="<%= url_for(:controller => :monitor, :action => :plothistory, :set => prefix + 'blocked', :range => 24, :time => Time.now.to_i ) %>" alt='Blocked' width="400" height="300"/> +<img class="monitorplot" src="<%= url_for(:controller => :monitor, :action => :plothistory, :set => prefix + 'blocked', :range => 24, :time => Time.now.to_i ) %>" alt='Blocked' width="300" height="250"/> <span>Blocked by other packages</span> </li> <li> -<img class="monitorplot" src="<%= url_for(:controller => :monitor, :action => :plothistory, :set => prefix + 'workers', :range => 24, :time => Time.now.to_i ) %>" alt='Workers' width="400" height="300"/> +<img class="monitorplot" src="<%= url_for(:controller => :monitor, :action => :plothistory, :set => prefix + 'workers', :range => 24, :time => Time.now.to_i ) %>" alt='Workers' width="300" height="250"/> <span>Workers</span> </li> </ul> -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 1

[opensuse-buildservice] Re: [PATCH] [backend] kill also all build jobs which became "blocked" again
by Stephan Kulow 23 Aug '10

23 Aug '10

Montag 16 August 2010 sent OBS build: > From: Adrian Schröter <adrian(a)suse.de> > > --- > src/backend/bs_sched | 12 ++++++++++++ > 1 files changed, 12 insertions(+), 0 deletions(-) > > diff --git a/src/backend/bs_sched b/src/backend/bs_sched > index 189417e..2c255dd 100755 > --- a/src/backend/bs_sched > +++ b/src/backend/bs_sched > @@ -4592,6 +4592,18 @@ relsynccheck: > unlink("$reporoot/$prp/$myarch/:repostate"); > } > > + # building jobs may have changed back to blocked, kill the jobs > + my $prpjobs = jobname($prp, ''); > + for (grep {!/(?::dir|:status)$/} grep {/^\Q$prpjobs\E/} ls($myjobsdir)) > { + my $job = $_; > + if ($job =~ /^\Q$prpjobs\E(.*)-[0-9a-f]{32}$/) { > + if ($packstatus{$1} and $packstatus{$1} eq 'blocked') { > + print " killing old job, now in blocked state $job\n"; > + killjob($job); > + } > + } > + } > + > # notify remote build services of repository changes or block state > # changes > # we alse send it if we finish a prp to give linked aggregates a Hi, I think this change is bad if I understand it correctly. When Factory rebuilds, packages become blocked because of rebuild counter sync even though the running build jobs are not harmed - they are just displayed incorrectly. The scheduler will "unblock" as soon as the build is done. So I would propose only to remove scheduled jobs that became blocked, but do not kill running jobs. The harm appears larger than the benefit. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 0

[opensuse-buildservice] [OT] PathScale packaging bounty
by "C. Bergström" 23 Aug '10

23 Aug '10

Hi all Apologies for the OT post.. PathScale needs some packaging help (immediately or asap) 1) kernel-trace, kernel-default, kernel-sources , kernel-trace-sources (if they differ) , kernel-trace-sysm (if this needs to be different from, kernel-sysm) I've started a package [1] derived from Kernel:HEAD which gets close to doing what we need, but not quite. The kernel-trace package builds and boots, but I can't manage to get the corresponding kernel-trace-sources to correctly match. 2) pscnv (Built against the kernel-default and kernel-trace from above) http://github.com/pathscale/pscnv (There's existing nouveau packages which could possibly be a good base start.. https://build.opensuse.org/project/repositories?project=home%3Ajobermayr ) 3) valgrind-mmt http://kadu.net/~joi/valgrind-mmt.git/ <http://kadu.net/%7Ejoi/valgrind-mmt.git/> 4) envytools http://github.com/pathscale/envytools/ Q - Why the hassle and why Kernel:HEAD? A - We're not currently able to backport and test our compiler on the loads of different kernels so want a 2.6.35 kernel that we can get packaged everywhere. (Vanilla would be 2nd choice) Q - What's the benefit? A - The end result once these packages are done will be open source NVIDIA drivers across all the distributions that we can get this kernel package to build for. The kernel-trace packages will allow us to also have an officially supported developer kernel to make it easier for people to get us mmiotraces. Overall we hope it'll allow greater testing and developer interest. Q - What's pscnv? A - http://wiki.github.com/pathscale/pscnv/ Q - How much is the bounty? A - Contact me off list #pathscale - freenode (I'm codestr0m) Best, Christopher [1] https://build.opensuse.org/project/packages?project=home%3Apathscale -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 2