openSUSE Build Service July 2011

buildservice@lists.opensuse.org

46 participants
65 discussions

[opensuse-buildservice] [PATCH] [obs-service-tar_scm]

by Troy Telford

In my own testing of the '--exclude' option for the tar_scm source service, I found that nothing was being excluded. Running the tar_scm script manually produced the same result(s) - the exclusion had no effect. After some head scratching, we found that the single quotes in the command-line parser appear to be the culprit; removing the single quotes results in correct operation of the exclude option. --- tar_scm 2011-07-14 17:42:08.000000000 -0600 +++ tar_scm 2011-07-14 17:42:26.000000000 -0600 @@ -45,7 +45,7 @@ shift ;; *-exclude) - EXCLUDES="$EXCLUDES --exclude='${2#/}'" + EXCLUDES="$EXCLUDES --exclude=${2#/}" shift ;; *-filename) -- Troy Telford -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

9 years, 9 months

[opensuse-buildservice] [PATCH] [obs-service-tar_scm] - Exclude SCM files by default

by Troy Telford

In my own testing of the tar_scm 'exclude' feature, I found that the 'tar' command grabs all of the scm's metadata (.svn, .git, etc.) Tar has the option --exclude-vcs, which excludes these files from the tarball. These seems to make the most sense for the way I think tar_scm is supposed to be used. An alternative (possibly better) way would be to have an option to the source service that allows the user to toggle this option on/off; however I don't currently know of any use cases where it would be useful to have the version control system's metadata in the tarball. @@ -258,7 +258,7 @@ mv "$FILE/$MYSUBDIR" "${FILE}-${VERSION}" || exit 1 -tar cf "$MYOUTDIR/${FILE}-${VERSION}.tar" $EXCLUDES "${FILE}-${VERSION}" || exit 1 +tar cf "$MYOUTDIR/${FILE}-${VERSION}.tar" --exclude-vcs $EXCLUDES "${FILE}-${VERSION}" || exit 1 rm -rf "${FILE}-${VERSION}" "$FILE" exit 0 -- Troy Telford -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

9 years, 9 months

[opensuse-buildservice] Package is not used for building in my project

by Andreas Jaeger

Did the build service change some defaults? I have packaged new systemd and new udev in my project - and systemd builds against the old udev and not the one in the project. This is project "home:a_jaeger:branches:openSUSE:Factory". "Use for build" is enabled in the webui. I cleaned the configs up already but it's not helping at all. What's wrong ? Andreas -- Andreas Jaeger, Program Manager openSUSE aj(a){suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

9 years, 9 months

[opensuse-buildservice] Re: [PATCH] [webui] Initial display of per-action-per-file diff request view.

by Stephan Kulow

Mittwoch, 13. Juli 2011 sent OBS build: > From: Sascha Peilicke <saschpe(a)suse.de> > > Needs some more visual refinement (i.e. github-like diff view). > --- > src/webui/app/controllers/request_controller.rb | 14 +++++++++++++- > src/webui/app/views/request/show.html.erb | 11 +++++++++-- > 2 files changed, 22 insertions(+), 3 deletions(-) > > diff --git a/src/webui/app/controllers/request_controller.rb > b/src/webui/app/controllers/request_controller.rb index b6746d8..a956ec4 > 100644 > --- a/src/webui/app/controllers/request_controller.rb > +++ b/src/webui/app/controllers/request_controller.rb > @@ -1,3 +1,5 @@ > +require 'base64' > + > class RequestController < ApplicationController > include ApplicationHelper > > @@ -101,7 +103,17 @@ class RequestController < ApplicationController > # get the entire diff from the api > begin > transport ||= ActiveXML::Config::transport_for :bsrequest > - @diff_text = transport.direct_http URI("/request/#{@id}?cmd=diff"), > :method => "POST", :data => "" + ret = > transport.direct_http(URI("/request/#{@id}?cmd=diff&view=xml"), :method => > 'POST', :data => '') + doc = XML::Parser.string(ret).parse.root > + @diff_per_action_hash = {} > + # Parse each action and get the it's diff (per file) > + doc.find('/action').each_with_index do |action_element, index| > + file_diff_hash = {} Direct usage of XML::Parser should be banned now and in the future. doc = ActiveXML::Base.new(ret) doc.each_with_index("/action") will do Greetings, Stephan -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

9 years, 9 months

[opensuse-buildservice] Re: [PATCH] [shared] No need to specify RuntimeError, it's the default exception type.

by Sascha Peilicke

On Thursday 14 July 2011 09:27:57 you wrote: > From: Sascha Peilicke <saschpe(a)suse.de> > > Avoids Ruby not being able to distinguish an exception from a function: > 'NoMethodError Exception: undefined method `RuntimeError' for > <ActiveXML::Base:...>' > --- > buildservice/lib/activexml/node.rb | 8 ++++---- > 1 files changed, 4 insertions(+), 4 deletions(-) > > diff --git a/buildservice/lib/activexml/node.rb > b/buildservice/lib/activexml/node.rb index 798ec1d..b877a62 100644 > --- a/buildservice/lib/activexml/node.rb > +++ b/buildservice/lib/activexml/node.rb > @@ -69,7 +69,7 @@ module ActiveXML > elsif stub.kind_of? LibXMLNode > self.raw_data = stub.dump_xml > else > - raise RuntimeError, "make_stub should return LibXMLNode or > String, was #{stub.inspect}" + raise "make_stub should return > LibXMLNode or String, was #{stub.inspect}" end > elsif data.kind_of? LibXMLNode > self.raw_data = data.dump_xml > @@ -144,7 +144,7 @@ module ActiveXML > > def each_with_index(symbol = nil) > unless block_given? > - raise RuntimeError "use each instead" > + raise "use each instead" Even though the fix is ok, the reasoning was wrong, there was simply a comma missing... > end > index = 0 > nodes = Array.new > @@ -246,10 +246,10 @@ module ActiveXML > > def delete_element( elem ) > if elem.kind_of? LibXMLNode > - raise RuntimeError, "NO GOOD IDEA!" unless self.internal_data.doc > == elem.internal_data.doc + raise "NO GOOD IDEA!" unless > self.internal_data.doc == elem.internal_data.doc > elem.internal_data.remove! > elsif elem.kind_of? LibXML::XML::Node > - raise RuntimeError, "this should be obsolete!!!" > + raise "this should be obsolete!!!" > elem.remove! > else > e = data.find_first(elem.to_s) -- With kind regards, Sascha Peilicke SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nuernberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer HRB 16746 (AG Nürnberg)

9 years, 9 months

[opensuse-buildservice] [GSoC] OBS Mobile Project: Mid-term Review

by Justine Leng

Hi all, Hope all has been well. Here's a quick mid-term summary of the OBS Mobile Project I've been working on: Completed: - Set up a local development instance of the build service webclient - Created a local branch of the project on Gitorious: https://gitorious.org/~justineleng/opensuse/justineleng-build-service ; - Accumulated community feedback on mobile view changes and enhancements, which provides general directions and specs for development for the next few weeks - Coded changes in views (code for mobile view UI is practically done; just need to implement actions for those views in controller) - Committed and pushed a batch of changes to master branch - Kept detailed documentation in project blog (http://obsforandroid.wordpress.com) and Wiki (http://en.opensuse.org/openSUSE:GSOC2011_OBS_Mobile) In the end, the OBS mobile request views will look probably like this: [ http://susepaste.org/42889315, http://susepaste.org/65424698, http://susepaste.org/93489293, http://susepaste.org/61005220 ], and the OBS mobile project/package views will look like this: [ http://susepaste.org/78654933, http://susepaste.org/55250449, http://susepaste.org/511431, http://susepaste.org/64294027, http://susepaste.org/30633884 ;]. Code for the views in jQuery is mostly done, and I will just need to polish them and make them "act." To be done: - Update jQuery Mobile to the latest release - Code and implement new methods for each view change in controller - Convert web-browser html views in project/package to mobile views - Create test-suites for the mobile interface - Continue with documentation The project seems to be in good shape. Thanks, Justine -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

9 years, 9 months

[opensuse-buildservice] Packaging Issue of Net::Z3950::ZOOM Perl module via osc

by Andi Sugandi

Hi developers, I'm trying to package Net::Z3950::ZOOM Perl module via osc, but I find an issue. This is what I've done as describe on the wiki[0]: > cd home\:andisugandi/ > osc mkpac perl-Net-Z3950-ZOOM A perl-Net-Z3950-ZOOM > cd perl-Net-Z3950-ZOOM/ > cpanspec -v Net::Z3950::ZOOM Get file Net::Z3950::ZOOM Updating /home/andi/.cpan/sources/modules/02packages.details.txt.gz... Fetching /home/andi/.cpan/sources/modules/02packages.details.txt.gz from http://www.cpan.org/modules/02packages.details.txt.gz... /home/andi/.cpan/sources/modules/02packages.details.txt.gz is up to date. parsing packages Use of uninitialized value in split at /usr/lib/perl5/vendor_perl/5.12.3/Parse/CPAN/Packages.pm line 69. done Failed to parse 'Net::Z3950::ZOOM' or find a module by that name, skipping... Exiting subroutine via next at /usr/bin/cpanspec line 392. What am I supposed to do? Thanks in advance. [0] http://en.opensuse.org/openSUSE:Packaging_Perl Best regards, -- Andi Sugandi. openSUSE-id Team, openSUSE Community Member. https://connect.opensuse.org/pg/profile/andisugandi -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

9 years, 9 months

[opensuse-buildservice] Abysmal performance of buildservice

by Cristian Rodríguez

Hi: I thought it was a temporary problem, but it seems now there is a permanent performance problem on the OBS instance. Packages take hours even for getting scheduled and I have seen for example, kernel packages taking from several days to a week to be published. It is reaching to point where creating packages manually and publishing with a home-made script is faster and more efficient. If it is lacking of build-power ..ok..then some sort of build-quota should be put in place, or maybe putting all "home" repositories disabled by default requiring the user to enable build in a per-repo or per-package basis. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

9 years, 9 months

[opensuse-buildservice] Build Team Meeting

by Adrian Schröter

present: mls, speilicke, lrupp, adrian, mmaier Topics: * build.opensuse.org speed issues. * Improved diff support. * OBS 2.3. build.opensuse.org speed issues =============================== Speed improvements for scheduler: * mls will rewrite the way built packages are handled after 2.3 release, to reduce the time jobs stay in "finished". This seems to be the cause for most of the complaints. * Backend servers upgrade still WIP, but new hardware is ready * build03 will become a dedicated product build host to unload the scheduler host * On the long run, we will cluster the scheduling hosts. api/mysql speed improvement due to different sorting algorithm. We are about to drop collection rules and use MySQL native sorting algorithm, which seems to be much faster. A db migration for that is planed, but we need to check if that conflicts with rails mechanisms. Improved diff support ===================== Maintenance review process requires an improved diff support. All actions of a request needs to be diffed. We nedd support in backend for: * diffing output format in XML which - defines new files - removed files - changed files, including the diff * support for diffing per request action webui and osc need to be able show these on maintenance incident and release requests. Sascha and mls will follow up. OBS 2.3 ======= We will branch 2.3 soon to allow new feature developments. But we will not release 2.3 as final until the openSUSE maintenance process has moved to it. We will roll a beta 3 this week. -- 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

9 years, 9 months

[opensuse-buildservice] Debian:backport-overlay and Ubuntu:backport-overlay

by Marcus Rueckert

hi, ever ran into the situation that your package would require a newer version of the debhelper package? this can be easily solved now: [[[ <repository name="xUbuntu_10.04"> <path project="Ubuntu:backport-overlay" repository="xUbuntu_10.04"/> <path project="Ubuntu:10.04" repository="standard"/> <arch>x86_64</arch> <arch>i586</arch> </repository> ]]] it is important that the path with the backport-overlay is before the normal distro path, otherwise it will pick up the debhelper from the base distro. you can see it live in the server:http project. hth darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

9 years, 9 months

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Build Service July 2011