openSUSE Build Service September 2010

buildservice@lists.opensuse.org

57 participants
82 discussions

[opensuse-buildservice] Re: [PATCH] [api] readded _aggregate permission checks corrected
by Adrian Schröter 30 Sep '10

30 Sep '10

This STILL can not work. And this is still a design problem. Really. Why do you blindly re-apply the removed stuff without to face the design problems in any way with it ? This is not a productive way and will not get us any step nearer to the 2.2 release. Am Mittwoch, 29. September 2010, 23:39:27 schrieb OBS build-service: > From: Martin Mohring <martinmohring(a)linuxfoundation.org> > > --- > src/api/app/controllers/source_controller.rb | 45 ++++++++++++++++++++++++- > 1 files changed, 43 insertions(+), 2 deletions(-) > > diff --git a/src/api/app/controllers/source_controller.rb b/src/api/app/controllers/source_controller.rb > index bbc7325..9009fe9 100644 > --- a/src/api/app/controllers/source_controller.rb > +++ b/src/api/app/controllers/source_controller.rb > @@ -985,8 +985,49 @@ class SourceController < ApplicationController > validator.validate(request) > end > > - # ACL(file): the following code checks if link or aggregate, kiwi file or product definition opens a hole > - if params[:file] == "_link" > + # ACL(file): the following code checks if link or aggregate > + if params[:file] == "_aggregate" > + data = REXML::Document.new(request.raw_post.to_s) > + data.elements.each("aggregatelist/aggregate") do |e| > + # ACL(file) TODO: check if the _aggregate check cannot be circumvented somehow > + tproject_name = e.attributes["project"] > + tprj = DbProject.find_by_name(tproject_name) > + if tprj.nil? > + if not DbProject.find_remote_project(tproject_name) > + render_error :status => 404, :errorcode => 'not_found', > + :message => "The given #{tproject_name} does not exist" > + return > + end > + else > + # ACL(file): _aggregate access behaves like project not existing > + if tprj.disabled_for?('access', nil, nil) and not @http_user.can_access?(tprj) > + render_error :status => 404, :errorcode => 'not_found', > + :message => "The project #{tproject_name} does not exist" > + return > + end > + > + # ACL(file): _aggregate binarydownload denies access to repositories > + if tprj.disabled_for?('binarydownload', nil, nil) and not @http_user.can_download_binaries?(tprj) > + render_error :status => 403, :errorcode => "download_binary_no_permission", > + :message => "No permission to _aggregate binaries from project #{params[:project]}" > + return > + end > + > + # ACL(file): check that user does not aggregate an unprotected project to a protected project > + if prj > + if (tprj.disabled_for?('access', nil, nil) and prj.enabled_for?('access', nil, nil)) or > + (tprj.disabled_for?('binarydownload', nil, nil) and prj.enabled_for?('access', nil, nil) and > + prj.enabled_for?('binarydownload', nil, nil)) > + render_error :status => 403, :errorcode => "binary_download_no_permission" , > + :message => "aggregate with an unprotected project #{project_name} to a protected project #{tproject_name}" > + return > + end > + end > + end > + > + logger.debug "_aggregate checked for #{tproject_name} project permission" > + end > + elsif params[:file] == "_link" > data = REXML::Document.new(request.raw_post.to_s) > data.elements.each("link") do |e| > tproject_name = e.attributes["project"] > -- 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] DEB builds locally without error, OBS throws error about duplicate field section in control file
by Nicholas Peterson 30 Sep '10

30 Sep '10

Hi Debian/Ubuntu users of OBS, On my local computer (ubuntu) I can build my deb package using 'dpkg-buildpackage -rfakeroot' without errors, but when I move the package to OBS, I get the following error. dpkg-checkbuilddeps: error: syntax error in debian/control at line 27: duplicate field Section found Link to Package: https://build.opensuse.org/package/show?package=clapack&project=home%3Anrp36 Full Build Log: https://build.opensuse.org/package/live_build_log?arch=i586&package=clapack… Any idea why OBS is complaining about the control file when I can build it locally just fine? Thanks, Nick -- 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] osc.core.get_user_projpkgs() function returns strange data
by Michal Smrž 29 Sep '10

29 Sep '10

Hello, I am playing with osc and tried to get list of involved projects and packages. I used osc.core.get_user_projpkgs(apiurl, user) but it is still returning me: {'package_id': <Element 'collection' at 0xbe1c00>, 'project_id': <Element 'collection' at 0xc2a750>} and i'am not sure, what to do with it. Thank you Michal Smrž -- 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] "Not specified origin package via oproject and opackage parameter"
by Karl Eichwalder 29 Sep '10

29 Sep '10

I want to update yast2-trans (project: YaST-Head) and receive this error message at checkin: Not specified origin package via oproject and opackage parameter That's what I did: osc co YaST\:Head yast2-trans cd YaST:Head/yast2-trans/ # cp new tar.bz2 files, update .changes osc ci -m "Updated languages: af am ar be bg bn bs ca cs cy da de el es et fa fi fr gl gu he hi hr hu id it ja jv ka km kn ko ku lo lt mk mr ms my nb nl pa pl pt ro ru si sk sl sr sv sw ta tg th tk tr uk vi wa xh zu en_GB en_US pt_BR zh_CN zh_TW ast." ==> Not specified origin package via oproject and opackage parameter What is going wrong, please? -- Karl Eichwalder R&D / Documentation SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 1

[opensuse-buildservice] OBS-related blog posts at Dell Techcenter
by Michael E Brown 28 Sep '10

28 Sep '10

Thought people might be interested in two blog posts that are up on Dell TechCenter blog that are relevant to OBS/Kiwi. I wrote the following blog post about how we use OBS to build Dell OpenManage. If people want to know more, I'm open to writing other blog posts. As long as they get readers, I'll keep writing them... :) http://en.community.dell.com/dell-blogs/enterprise/b/tech-center/archive/20… My co-worker, Praveen Paladugu, wrote the following post about Kiwi: http://en.community.dell.com/dell-blogs/enterprise/b/tech-center/archive/20… -- Michael Brown Linux OS Engineering Dell Inc

2 1

[opensuse-buildservice] status_histories
by Stephan Kulow 28 Sep '10

28 Sep '10

Hi, I just pushed a couple of migrations for the status_histories table. These can take a while if you have a lot of history. If you don't care about the correctness of it, feel free to use "delete from status_histories;" on your API database before migrating. These migrations took 90 minutes on my copy of the build.opensuse.org database - and this instance should have the longest history ;) 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] Re: [PATCH] git_pull service osc support
by Adrian Schröter 28 Sep '10

28 Sep '10

Please adapt this to use "tar_scm" service instead. I do not want to have two services by default for the same thing. (Please see my other mail). bye adrian Am Montag, 20. September 2010, 11:06:47 schrieb OBS osc: > From: brook hong <hzgmaxwell(a)hotmail.com> > > --- > osc/commandline.py | 5 ++++- > osc/core.py | 27 +++++++++++++++++++++++++++ > 2 files changed, 31 insertions(+), 1 deletions(-) > > diff --git a/osc/commandline.py b/osc/commandline.py > index 0e11913..d5432b3 100644 > --- a/osc/commandline.py > +++ b/osc/commandline.py > @@ -2880,7 +2880,10 @@ Please submit there instead, or use --nodevelproject to force direct submission. > # Do some magic here, when adding a url. We want that the server to download the tar ball and to verify it > for arg in parseargs(args): > if arg.startswith('http://') or arg.startswith('https://') or arg.startswith('ftp://'): > - addDownloadUrlService(arg) > + if arg.endswith('.git'): > + addGitSource(arg) > + else: > + addDownloadUrlService(arg) > else: > addFiles([arg]) > > diff --git a/osc/core.py b/osc/core.py > index 1bead66..47124ea 100644 > --- a/osc/core.py > +++ b/osc/core.py > @@ -301,6 +301,12 @@ class Serviceinfo: > r.append( s ) > return r > > + def addGitUrl(self, serviceinfo_node, url_string): > + r = serviceinfo_node > + s = ET.Element( "service", name="git_pull" ) > + ET.SubElement(s, "param", name="url").text = url_string > + r.append( s ) > + return r > > def execute(self, dir): > import tempfile > @@ -5169,6 +5175,27 @@ def stripETxml(node): > for child in node.getchildren(): > stripETxml(child) > > +def addGitSource(url): > + service_file = os.path.join(os.getcwd(), '_service') > + addfile = False > + if os.path.exists( service_file ): > + services = ET.parse(os.path.join(os.getcwd(), '_service')).getroot() > + else: > + services = ET.fromstring("<services />") > + addfile = True > + stripETxml( services ) > + si = Serviceinfo() > + s = si.addGitUrl(services, url) > + si.read(s) > + > + # for pretty output > + reparsed = minidom.parseString(ET.tostring(s)) > + f = open(service_file, 'wb') > + f.write(reparsed.toprettyxml(indent=" ")) > + f.close() > + if addfile: > + addFiles( ['_service'] ) > + > def addDownloadUrlService(url): > service_file = os.path.join(os.getcwd(), '_service') > addfile = False > -- 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

2 6

[opensuse-buildservice] Package versions used for build
by Esztermann, Ansgar 28 Sep '10

28 Sep '10

Hi, how does OBS determine which release of a given package to install? I've stumbled across a bug in gtkglext, but found out that it is already fixed in oS 11.3. However, osc still installs the old, buggy version: $ rpm -q gtkglext gtkglext-1.2.0-183.1.1.x86_64 $ rpm -q gtkglext --root=/var/tmp/build-root/ gtkglext-1.2.0-182.1.x86_64 Thanks, A. -- Ansgar Esztermann DV-Systemadministration Max-Planck-Institut für biophysikalische Chemie, Abteilung 105 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

4 4

[opensuse-buildservice] Re: [PATCH] [api] status controller comments about unused API
by Stephan Kulow 27 Sep '10

27 Sep '10

Am Samstag, 11. September 2010, 00:47:25 schrieben Sie: > From: Martin Mohring <martinmohring(a)linuxfoundation.org> > def history > - # ACL(history) TODO: check this leaks no information that is > prevented by ACL + # ACL(history) TODO: check this leaks no > information that is prevented by ACL. Seems to sent an empty list. API > call looks unused hours = params[:hours] || "24" How do you measure the use of an API call if I may ask? Your comment appears to me rather funny. Of course you get an empty list as history in a fresh installation, but you're invited to call osc api /status/history?key=blocked_i586&range=1 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] obs que's
by doiggl＠velocitynet.com.au 27 Sep '10

27 Sep '10

Hello, Is opensuse build service[obs] throughput of jobs restricted in any way e.g disk i/o bound, when obs gets a lot of packages to process eg 8000 in the 'Blocked by other packages' que. What is the one thing{if any} that would make the biggest improvement in the processing/turnaround of jobs in the 'Blocked by other packages' or 'Waiting to build' que's ? Im interested to know how to improve throughput of very busy systems. Glenn -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 0

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

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Build Service September 2010