openSUSE Build Service February 2011

buildservice@lists.opensuse.org

64 participants
57 discussions

[opensuse-buildservice] A bug of maintaining meta data of linked project?

by Zhu, Peter J

Hi, Currently MeeGo uses process of submitting change like devel->T:T->Trunk. T:T is a linked project of Trunk. So we maintain devel meta data in Trunk rather than in T:T. For those packages with no changes in T:T(it means exactly same as Trunk, physically not exist as well in T:T), its metadata is exactly same as Trunk , then everything would be fine; But once there are changes accepted into Trunk:Testing, the metadata was also changed so devel relationship get lost as well. Look at below metadata for connman and ofono in T:T: Connman has No queuted changes in T:T, even project is set Trunk <package project="Trunk" name="connman"> <title>Connection Manager</title> <description>Connection Manager provides a daemon for managing Internet connections within embedded devices running the Linux operating system. </description> <devel project="devel:connectivity" package="connman"/> <person role="maintainer" userid="nashif"/> <person role="bugowner" userid="martin"/> <url>http://connman.net/</url<http://connman.net/%3c/url>> Ofono has queued changes in T:T, now meta is like below <package project="Trunk:Testing" name="ofono"> <title>Open Source Telephony</title> <description>Description: %{summary} </description> <url>http://ofono.org</url<http://ofono.org%3c/url>> So seem sr acceptance get meta data ruined of T:T. I suggest sr acceptance just copy package data, not meta data. Comments? Peter

10 years, 7 months

[opensuse-buildservice] local OBS installation -> remote link to packman?

by Mathias Homann

Hi there, is there a way to link my local OBS server to packman so that i can build against packages from there? bye, MH -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

10 years, 7 months

[opensuse-buildservice] ACL errors

by Neil McGovern

Hi all, I'm having a little bit of trouble implementing ACLs in a 2.1. When trying to insert (into the project config): <group groupid="Amino" role="maintainer"/> <sourceaccess> <disable/> </sourceaccess> <binarydownload> <disable/> </binarydownload> osc complains that: Sending meta data... BuildService API error: change_project_protection_level (403) admin rights are required to raise the source protection level of a project Try again? ([y/N]): This also seems to occur with the webui. Interestingly, api/app/controllers/source_controller.rb contains the following snippet: p = Project.new(request_data, :name => project_name) if @project and not @project.disabled_for?('sourceaccess', nil, nil) if p.disabled_for? :sourceaccess render_error :status => 403, :errorcode => "change_project_protection_level", :message => "admin rights are required to raise the source protection level of a project" return end end This doesn't seem to check for if a user is an admin or not, but (if I'm reading the code right) simply checks to see if the sourceaccess flag is being added at all. So... commenting out section allows me to add the flag, but then more interesting problems occur. It doesn't seem to matter what 'group' you're actually in, you can view the spec file via the webui, the download links (for the source) fail with access denied errors, but the source can be downloaded via osc! I'm hoping some basic understanding is missing here, and I'm not going completely insane. Does anyone have any thoughts about what could be causing this? Thanks, Neil -- Neil McGovern, Software Development Team Lead, Amino Communications Ltd Buckingway Business Park, Anderson Road, Swavesey, Cambridge, CB24 4UQ, UK nmcgovern(a)aminocom.com http://www.aminocom.com Tel: +44 1954 234 100 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

10 years, 7 months

[opensuse-buildservice] opensc-devel missing from openSUSE 11.4?

by Fritz Elfert

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Subject says it all: Today, I added the openSUSE_11.4 repo to my project which buildrequires opensc-devel and got missing dependencies. osc ls -b -r standard -a i586 openSUSE:11.4 | grep opensc just gives me: opensc.rpm opensc-debuginfo.rpm opensc-debugsource.rpm Any explanation, why no opensc-devel package exists in 11.4? Thanks -Fritz -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFNY0V2boM4mAMyprARAoXKAJ0S74C3BSasHtitp29Kyu1a9Rs7QgCggMJN 2BXRip2NliuTCcWaaUyQ4d8= =wFI0 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

10 years, 7 months

[opensuse-buildservice] Help my package is blocked!

by Paul Elliott

Help my package has been blocked for over six hours. https://build.opensuse.org/package/show?package=rpm&project=home%3Apelliott… The status says source update running. I have not been using osc just the web interface. That web browser has been shutdown hours ago. How do I make it work again? Thank You. -- Paul Elliott 1(512)837-1096 pelliott(a)BlackPatchPanel.com PMB 181, 11900 Metric Blvd Suite J http://www.free.blackpatchpanel.com/pme/ Austin TX 78758-3117

10 years, 7 months

[opensuse-buildservice] 1-Click Installer: auto-adding the repository!

by Nelson Marques

Dear all, Yet another (maybe) simple question... The 1-Click installer I created is working properly and there's one tiny itch for which I would love some guidance... All the process is working ok, including the repository being added (which is awesome)... nevertheless I would love to add this repository not at default priority level (99), but instead in a much higher priority. Is this possible through the 1-click installer ? Practical case: 1. Someone clicks the 1-click installer and goes through the drill... - Current behavior: repository is installed with default priority 99. - Wanted behavior: repository is installed with higher priority, example: 40. Thanks, NM -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

10 years, 7 months

[opensuse-buildservice] setup trouble

by Robert Schweikert

Hi, I am having a little trouble getting the osc commands working on a laptop. AFAIK there's nothing special. Running openSUSE 11.3, x86-64, GNOME desktop -> rpm -qa | grep osc osc-0.127-1.3.noarch When I run "osc help" I am prompted to setup KDE wallet, not that big of a deal but I do not remember doing this previously when I setup osc on another machine. (I do not have an alias ala "osc --no-keyring" setup). So when KDE wallet starts I get Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) Then after I set it up I end up with a stupid popup to enter my wallet password everytime I run an osc command. I do not have kdewalletmanager installed (on either system). I also tried copying ~/.oscrc from the machine where things work to the machine that is giving me fits, but to no avail. When I installed kwalletmanager on the machine giving me trouble and set things such that the stupid popup does no longer appear I'd still get the annoying "Connecting to deprecated signal..." message. Somewhere along the line I probably messed something up, help in straightening things out is much appreciated. Thanks, Robert -- Robert Schweikert MAY THE SOURCE BE WITH YOU Novell-IBM Software Integration Center LINUX Tech Lead rschweikert(a)novell.com rschweikert(a)ca.ibm.com 781-464-8147 Novell Making IT Work As One -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

10 years, 7 months

[opensuse-buildservice] Debian 6.0 is there ... and 4.0 away

by Adrian Schröter

Debian:6.0 project exists now and can be used to build for that target. The openSUSE:Tools project is also building "osc" and "build" now for this distribution. Thanks go to Carsten Höger from open-exchange who debugged the configuration. The :NonFree part is not yet imported. I will do so on request. Debian:Etch has been moved to DISCONTINUED:Debian:4.0 project. have fun adrian -- Adrian Schroeter SUSE Linux Products GmbH email: adrian(a)suse.de

10 years, 7 months

[opensuse-buildservice] Problem with xz compressed debs on ubuntu 10.10

by Gerd Fleischer

Hi, I have a problem building a package for ubuntu 10.10 it needs libkdepim5-dev which seems to be compressed with xz, on setting up the vm it fails with error message below: installing gzip installing insserv installing install-info installing libakonadi-kabc4 dpkg-deb (subprocess): unable to execute data (xz): No such file or directory dpkg-deb: subprocess <decompress> returned error exit status 2 dpkg: error processing .init_b_cache/libakonadi-kabc4.deb (--install): subprocess dpkg-deb --fsys-tarfile returned error exit status 2 Errors were encountered while processing: .init_b_cache/libakonadi-kabc4.deb exit ... [ 78.273746] System halted. On irc it was suggested to add xz to build-depends. I added xz-utils but that does not help as the packages that need it for installing are installed earlier than xz-utils and so it fails. Any hints? Can this be added to the preinstalled packages? Project home:geflei, plasmoid-eventlist Debian 6.0 and ubuntu 10.04 build fine, btw. Thanks, Gerd -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

10 years, 7 months

[opensuse-buildservice] Re: osc-plugin-collab as source service?

by Cristian Morales Vega

Someone with a minimum of python understanding, that I lack, feels like porting http://www.gitorious.org/opensuse/osc-plugin-collab/blobs/master/server/ups… (new version detection logic) and http://www.gitorious.org/opensuse/osc-plugin-collab/blobs/master/osc-collab… (download and .spec file update logic) to a source service? It would be a more complete obs-service-update_source. It should not be a lot more than modify the main function so limits = parse_limits(limit_file) is converted to something like # If --outdir was received we are running as a source service if options.outdir: if options.max_version: limits = (options.name, options.max_version) elif not options.allow_unstable: limits = (options.name, 'no-odd-unstable') else: limits = parse_limits(limit_file) and the same for file = open(upstream_file) lines = file.readlines() that should be if options.outdir: if options.branch: lines = [ options.name + '|' + options.branch + ':' + options.method + ':' options.info + '\n' ] else: lines = [ options.name + ':' + options.method + ':' options.info + '\n' ] with a .service file similar to <service name="update_source2"> <summary>Update sources2</summary> <description>This service is tries to find a new version upstream and updates the sources.</description> <parameter name="name"> <description>the upstream module name found in tarball names</parameter> <required/> </parameter> <parameter name="branch"> <description>branch</parameter> </parameter> <parameter name="method"> <description>one of 'upstream', 'ftpls', 'httpls', 'dualhttpls', 'subdirhttpls', 'sf', 'google', 'lp'</parameter> <allowedvalue>ftpls</allowedvalue> <allowedvalue>httpls</allowedvalue> <allowedvalue>dualhttpls</allowedvalue> <allowedvalue>subdirhttpls</allowedvalue> <allowedvalue>sf</allowedvalue> <allowedvalue>google</allowedvalue> <allowedvalue>lp</allowedvalue> <required/> </parameter> <parameter name="info"> <description>info depends on method</parameter> <required/> </parameter> <parameter name="max_version"> <description>Not have a version greater or equal than a specified version</description> </parameter> <parameter name="allow_unstable"> <description>not have unstable versions (for modules following the x.y.z release scheme, where it's unstable when y is odd)</parameter> </parameter> </service> 2011/2/19 Vincent Untz <vuntz(a)opensuse.org>: > Le samedi 19 février 2011, à 10:58 +0100, Cristian Morales Vega a écrit : >> I just found obs-service-update_source >> (https://build.opensuse.org/package/view_file?file=update_source&package=obs…) >> and found it limited when compared to >> http://gitorious.org/opensuse/osc-plugin-collab/trees/master/server/upstream >> (no way to check sourceforge tarballs but set an specific mirror, >> etc.) >> >> Do you have any plans to convert the upstream update part of >> osc-plugin-collab to a source service? Any known problems? > > Ideally, yes, I'd do it. But I really am too short in time for this, so > it won't happen in the short term unless someone else does the job. > > It might make sense to suggest this on the opensuse-buildservice mailing > list -- I'm willing to help people who'd work on that, fwiw. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

10 years, 7 months

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Build Service February 2011