June 2011 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] Setup OBS to point on MeeGo repo (or any remote repo)
by Dominig ar Foll (Intel OTC) 15 Jun '11

15 Jun '11

Hi, I have installed a local OBS and I try to get it to offer to its user the option to build against the MeeGo repo.<br> Under Admin login, I use the Setup OBS button to create a link to the public MeeGo api.<br> My project is well created but when I try to build against the MeeGo project I do not see the list of the project which are available on the MeeGo OBS. In my case the Raw config shows : <project name="Meego-official"> <title>Link to public MeeGo OBS</title> <description>This project is representing a remote build service instance or official MeeGo</description> <remoteurl>https://api.meego.com/public</remoteurl> <person userid="Admin" role="maintainer"/> <person userid="Admin" role="bugowner"/> </project> I can manually create a build on any project hosted on MeeGo.com but I would like to create an easy web page in which list the various projects from MeeGo.com Where could I find the instruction to add MeeGo distro on the landing page when the user click on select build target ? Thanks. -- Dominig -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 5

[opensuse-buildservice] [Seeking Feedback] OBS mobile: request page makeover
by Justine Leng 14 Jun '11

14 Jun '11

Greetings, Hope all is well. :) I'm a GSoC'11 student working on the OBS mobile client for Android, and I have a few ideas about improving the Request page. I figured some feedback from the community would be very helpful, especially from those who use OBS regularly. (A blog discussion & more vivid visual illustration of this can be found at: http://obsforandroid.wordpress.com/2011/06/09/obs-mobile-request-page -makeover/ ) At this moment, when we open up the OBS mobile and click on Requests, it takes us directly to the list of requests (http://img.susepaste.org/64883370) How would it look if we were to replace the list with some buttons on this page, e.g., View All Requests, Add Request, Search (http://img.susepaste.org/48027969)? Do you think this is a good place to Add Requests? I heard that new requests were often related to packages, so I wonder if it might make more sense to place "Add Requests" on the Package view page. Would it be useful to have a Search button here? So, when a user taps "View All Requests," the screen would slide over to display the entire list of requests (http://img.susepaste.org/95818729) I was thinking about adding some sorting functions here to show an ordered list of requests. Should the list be automatically sorted alphabetically or chronologically upon loading, or should there be some buttons on the page which the user could tap and sort himself/herself? How about a sort based on the request's status, e.g., accepted, declined, pending? Then, when the user taps on a specific request, instead of showing the original 3 collapsible functions (http://img.susepaste.org/77504424) the screen displays 4 collapsible buttons: Actions, Info, History, and Diff. (http://img.susepaste.org/95372228) Tapping the Actions button will expand it to display the 4 possible actions on a request: Accept, Decline, Modify, and Delete. (http://img.susepaste.org/67877982) How does this look? Is it more convenient & user-friendly? Also, do you think we should implement a mobile view for https://build.opensuse.org/home/my_work, for a better makeover of this Request page? Your comments and suggestions are always welcome! :) Best regards, ~ Justine -- 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] ERROR: source-validator failed
by Ciro Iriarte 14 Jun '11

14 Jun '11

Hi, is it possible to disable the source validator?, I'm referencing a source file included in another package using a _link file and because of this the validator is complaining at commit time... Regards, -- Ciro Iriarte http://cyruspy.wordpress.com -- -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 2

[opensuse-buildservice] error in OBS security:chipcard/libchipcard
by Nico Kruber 13 Jun '11

13 Jun '11

The following error occurred after my sr got accepted - the package was building fine in my branch though... security:chipcard/libchipcard/94e09d942cf1e858a76f855df686cef8: not in repository. Either not existing or misconfigured server setting for '$nosharedtrees' setting in BSConfig.pm Can somebody check and fix whatever happened there? see https://build.opensuse.org/package/show?package=libchipcard&project=securit… Regards Nico Kruber

1 0

[opensuse-buildservice] Virtualizing OBS worker build environment with OpenVZ or LXC
by Ville.Seppanen＠tieto.com 13 Jun '11

13 Jun '11

Greetings, Is there any work being done for OpenVZ, LXC or other OS-level virtualization support for the build environment in OBS? I am doing my Master's thesis on extending OBS to the cloud. Seeing that Amazon Web Services uses Xen for virtualization (and thus does not support Xen/KVM inside it), and that building without a sandboxed environment is not safe, OpenVZ and LXC would seem promising. There's also much talk about using these technologies in AWS, so I would see it possible. Best Regards, Ville Seppänen Tieto Corporation -- 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] latest api migration fails
by Robert Xu 13 Jun '11

13 Jun '11

Hi all, running rake db:migrate on the latest obs-api yields this message: undefined method `pass' for #<ActiveRecord::ConnectionAdapters::MysqlAdapter:0x7effb0186198> /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.8/lib/active_record/migration.rb:352:in `send' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.8/lib/active_record/migration.rb:352:in `method_missing' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.8/lib/active_record/migration.rb:328:in `say_with_time' /usr/lib64/ruby/1.8/benchmark.rb:293:in `measure' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.8/lib/active_record/migration.rb:328:in `say_with_time' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.8/lib/active_record/migration.rb:348:in `method_missing' ./db/migrate//20110609083665_create_configurations.rb:7:in `up_without_benchmarks' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.8/lib/active_record/migration.rb:282:in `send' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.8/lib/active_record/migration.rb:282:in `migrate' /usr/lib64/ruby/1.8/benchmark.rb:293:in `measure' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.8/lib/active_record/migration.rb:282:in `migrate' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.8/lib/active_record/migration.rb:365:in `__send__' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.8/lib/active_record/migration.rb:365:in `migrate' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.8/lib/active_record/migration.rb:491 /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.8/lib/active_record/migration.rb:567:in `call' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.8/lib/active_record/migration.rb:567:in `ddl_transaction' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.8/lib/active_record/migration.rb:490:in `migrate' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.8/lib/active_record/migration.rb:477:in `each' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.8/lib/active_record/migration.rb:477:in `migrate' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.8/lib/active_record/migration.rb:401:in `up' /usr/lib64/ruby/gems/1.8/gems/activerecord-2.3.8/lib/active_record/migration.rb:383:in `migrate' /usr/lib64/ruby/gems/1.8/gems/rails-2.3.8/lib/tasks/databases.rake:112 /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:636:in `call' /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:636:in `execute' /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:631:in `each' /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:631:in `execute' /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:597:in `invoke_with_call_chain' /usr/lib64/ruby/1.8/monitor.rb:242:in `synchronize' /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:590:in `invoke_with_call_chain' /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:583:in `invoke' /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2051:in `invoke_task' /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in `top_level' /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in `each' /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in `top_level' /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2068:in `standard_exception_handling' /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2023:in `top_level' /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2001:in `run' /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2068:in `standard_exception_handling' /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:1998:in `run' /usr/lib64/ruby/gems/1.8/gems/rake-0.8.7/bin/rake:31 /usr/bin/rake:19:in `load' /usr/bin/rake:19 -- later, Robert Xu + rxu AT lincomlinux DOT org -- 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] can't access?
by Robert Xu 12 Jun '11

12 Jun '11

Anyone else getting this while accessing https://build.opensuse.org? Forbidden You don't have permission to access / on this server. Additionally, a 403 Forbidden error was encountered while trying to use an ErrorDocument to handle the request. Apache/2.2.10 (Linux/SUSE) Server at build-internal.opensuse.org Port 7002 -- later, Robert Xu + rxu AT lincomlinux DOT org -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 3

[opensuse-buildservice] Problem with a package...
by Nelson Marques 10 Jun '11

10 Jun '11

Hi all, I'm having a small issue with one package. I've made a test package on Banshee:Unstable/banshee with some changes that are required for this new release of banshee. One of it's dependencies is dbus-sharp-glib which is provided in the Banshee repository (Banshee:Unstable inherits those packages to build). Now I'm facing a very strange issue here... dbus-sharp-glib-devel does include a Requires in the spec to pull the original package which provides the libraries... but on OBS builds that package isn't pulled... And if I enter a BuildRequires: dbus-sharp-glib (to force it to install that package), the local build works (osc build Banshee_openSUSE_11.4 --local-package) without issues, but if I commit it, it fails with this error: + exec rpmbuild -ba --define '_srcdefattr (-,root,root)' --define 'disturl obs://build.opensuse.org/Banshee:Unstable/openSUSE_Factory+Banshee/18969219…' /usr/src/packages/SOURCES/banshee.spec error: Failed build dependencies: dbus-sharp-glib is needed by banshee-2.1.0-11.1.i586 Anyone has some ideas about this? For some strange reason OBS is unable to pick up that package. NM -- 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] ccache in the OBS somehow ?
by Cristian Rodríguez 10 Jun '11

10 Jun '11

Hi: I maintain and have seen some packages that may benefit from ccache installed in the OBS buildmachine, because the build process compiles in a loop different targets that share a large amount of code. Is there anyway to tell in the prjconf to "use ccache" ? -- 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] [gsoc] osc code cleanup - summary of week 3
by Marcus Hüwe 10 Jun '11

10 Jun '11

Hi, here's a small summary of the 3rd (coding) week. This week I spent most of my time with developing the remote model classes. The goal was to put most of the code into a base class from which all remote models will be derived (if you're interested how it works have a look at [1]). So far we have classes for: * a remote project (RemoteProject - manages project metadata) * a remote package (RemotePackage - manages package metadata) * a request (Request) TODO for this week: * add exception handling to the httprequest.py module * add a RemoteFile class which can be used to access a remote file like a buildlog, prjconf or a source file * add a BuildResult class: - get the build results for a project or package - get the buildlog of a package - get the binary/binaries from the api Marcus [1]: https://gitorious.org/osc2/osc2/blobs/master/osc/remote.py -- 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] changes to 'plaintext_passwd' in osc
by Jon Nelson 10 Jun '11

10 Jun '11

I noticed some changes to how (already encoded) passwords are handled in osc -- it appears the default ('plaintext_passwd': '1') *rewrites* the .osc file to contain a plaintext version of the already-encoded password. This seems backward -- shouldn't the default be the other way around? -- Jon -- 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] apache config?
by Jon Nelson 10 Jun '11

10 Jun '11

Can somebody supply a set of instructions / config files for an OBS instance using Apache2, please? -- Jon -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 5

[opensuse-buildservice] Re: [PATCH] [api] follow marketing team recommendation to make just the prefix of Open Build Service instance configurable
by Sascha Peilicke 10 Jun '11

10 Jun '11

Damn, you discovered it :-) I was about sure you wouldn't notice my interpretation of our marketing team's flash of genius. So let them other instances be known as '$FOO Open Build Service' then. Hooray for pidgin! -- Mit freundlichen Grüßen, Sascha Peilicke http://saschpe.wordpress.com

1 0

[opensuse-buildservice] Expired keys
by Fritz Elfert 10 Jun '11

10 Jun '11

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I got a notice from a user of my package on OBS about an expired key: # aptitude update W: GPG error: http://download.opensuse.org Release: The following signatures were invalid: KEYEXPIRED 1307152882 AFAIR, those keys are generated on OBS automatically (I don't even have a private key for signing here). Is there anything I have to do in order to fix this? Thanks -Fritz -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFN8fcVboM4mAMyprARAh7BAJ9F91LzB4vlUGvMC64giezJ+boULACfZdQa hJFDxINzm4+RERYajPgrATo= =AIZj -----END PGP SIGNATURE----- -- 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] new osc in opensuse-tools under ubuntu
by Paul Elliott 10 Jun '11

10 Jun '11

I could not install the new osc in opensuse-tools in ubuntu 10.10 Here is the error: What is happening? ------ root@hrnowl:~# apt-get dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be upgraded: osc 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 214kB of archives. After this operation, 16.4kB of additional disk space will be used. Do you want to continue [Y/n]? y Get:1 http://download.opensuse.org/repositories/openSUSE:/Tools/xUbuntu_10.10/ ./ osc 0.132.0-1 [214kB] Fetched 215kB in 2s (95.6kB/s) Failed to fetch http://download.opensuse.org/repositories/openSUSE:/Tools/xUbuntu_10.10/./i… Size mismatch E: Unable to fetch some archives, maybe run apt-get update or try with --fix- missing? root@hrnowl:~# cd etc bash: cd: etc: No such file or directory root@hrnowl:~# cd /etc root@hrnowl:/etc# ls apt apt.conf.d preferences.d secring.gpg sources.list sources.list~ sources.list.d trustdb.gpg trusted.gpg trusted.gpg~ trusted.gpg.d root@hrnowl:/etc# ls apt/sources.list.d maitreya.list maverick-partner.list openastro.org.list opensuse-tools.list peless.list root@hrnowl:/etc# cat apt/sources.list.d/opensuse-tools.list ## This software is not part of Ubuntu, but is offered by third-party ## developers who want to ship their latest software. deb http://download.opensuse.org/repositories/openSUSE:/Tools/xUbuntu_10.10/ ./ root@hrnowl:/etc# -- 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 -- 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] Source services are broken
by Dave Plater 09 Jun '11

09 Jun '11

I've been trying to add source services to home:plater cdrtools all morning, even tried to edit the services file but I keep on getting this : OBS Web Interface Error: Permission denied The account that is logged into the system lacks proper permissions to perform the operation. Please contact the openSUSE admin to get proper permissions for the user account. Error Details: Errorcode: 403 Message: service still running When I created the first service "Download a file" it had downloaded the correct file when I clicked back and refreshed but as soon as I added "Change file compression" to create a tar.bz2 from the downloaded tar.gz the contents of "download_url" kept on getting wiped out. If I had any hair it would all be torn out :-( . Thanks Dave P -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 3

[opensuse-buildservice] debian | ubuntu, python fails
by peer 09 Jun '11

09 Jun '11

Hi, My Python packages seems to fail on OBS: https://build.opensuse.org/package/live_build_log?arch=x86_64&package=pytho… https://build.opensuse.org/package/live_build_log?arch=x86_64&package=pytho… What is going wrong here? Regards, ~P -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

3 5

[opensuse-buildservice] latest osc update (0.132.0-45.1) seems to break commits on obs 2.1.11
by Carsten Schoene 08 Jun '11

08 Jun '11

Hello List the latest osc update (0.132.0-45.1) from yesterday seems to break commits on my local OBS which is running 2.1.11. I get following message when i send a commit: Server returned an error: HTTP Error 400: Bad Request Unknown command 'getprojectservices' for path /source/multimedia:SL11/sox Is there a quick fix for this or do i have a local configuration problem? Cheers, Carsten

3 2

[opensuse-buildservice] [PATCH osc] osc co: print help instead of crashing if no arguments are given
by Petr Uzel 08 Jun '11

08 Jun '11

This fixes: ~> osc checkout Traceback (most recent call last): File "/usr/bin/osc", line 21, in <module> r = babysitter.run(osccli) File "/usr/lib/python2.7/site-packages/osc/babysitter.py", line 52, in run return prg.main() File "/usr/lib/python2.7/site-packages/osc/cmdln.py", line 310, in main return self.cmd(args) File "/usr/lib/python2.7/site-packages/osc/cmdln.py", line 333, in cmd retval = self.onecmd(argv) File "/usr/lib/python2.7/site-packages/osc/cmdln.py", line 449, in onecmd return self._dispatch_cmd(handler, argv) File "/usr/lib/python2.7/site-packages/osc/cmdln.py", line 1179, in _dispatch_cmd return handler(argv[0], opts, *args) File "/usr/lib/python2.7/site-packages/osc/commandline.py", line 3386, in do_checkout m = re.match(r"obs://([^/]+)/(\S+)/([^/]+)/([A-Fa-f\d]+)\-(\S+)", args[0]) IndexError: tuple index out of range Signed-off-by: Petr Uzel <petr.uzel(a)suse.cz> --- osc/commandline.py | 4 ++++ 1 files changed, 4 insertions(+), 0 deletions(-) diff --git a/osc/commandline.py b/osc/commandline.py index e0981bb..adea1cf 100644 --- a/osc/commandline.py +++ b/osc/commandline.py @@ -3382,6 +3382,10 @@ Please submit there instead, or use --nodevelproject to force direct submission. else: expand_link = True + if not args: + raise oscerr.WrongArgs('Incorrect number of arguments.\n\n' \ + + self.get_cmd_help('checkout')) + # XXX: this too openSUSE-setup specific... # FIXME: this should go into ~jw/patches/osc/osc.proj_pack_20101201.diff # to be available to all subcommands via @cmdline.prep(proj_pack) -- 1.7.3.4 Petr -- Petr Uzel IRC: ptr_uzl @ freenode

2 1

[opensuse-buildservice] new osc user interface proposal
by Marcus Hüwe 08 Jun '11

08 Jun '11

Hi, as a part of our Google Summer of Code Project to cleanup osc [1] our first task was to define a new commandline user interface for osc. The current user interface is quite "inconsistent" (with regard to the expected arguments for different commands) and has some other "flaws". Here are some examples to show some flaws of the current user interface: * inconsistent ui: - osc results project package --repo repo --arch arch - osc rebuild project package repo arch - osc build repo arch - osc ls project package repo arch -b - osc ls project package -r repo -a arch -b - osc undelete project package_1 ... package_N - osc rdelete project package_1 * counterintuitive commands: - osc abortbuild project package - osc abortbuild project package repo arch - osc abortbuild (in a package working copy) - osc abortbuild --repo repo --arch arch (in a package working copy) - osc abortbuild repo arch (in a package working copy) => treats "repo" "arch" as "project" "package" * "duplicated" commands: - diff, rdiff - buildlog, remotebuildlog, localbuildlog - delete, rdelete, rremove Additionally we support lots of commands and the output of "osc --help"is quite long. In order to tackle this problem we decided to introduce "groups" with subcommands, for instance: attribute list attribute create... attribute set... ... As a result we get rid of "god commands" (commands which supported lots of different options for different things (like osc meta)) and the new commands are easier to use because they support less arguments and/or options (note: this doesn't mean we lose functionality - the functionality is just moved to another command/command group). The attached files are just a _proposal_ for a new commandline user interface. Some additional explanations: The biggest change with regard to our current user interface is the introduction of an url-like syntax: For example: osc ls api://project/package instead of osc ls project package In this case "api" means that the request is issued to the default apiurl (in most cases https://api.opensuse.org) which can be configured in the ~/.oscrc. To issue the "list" request to a different obs instance one can use: osc ls https://api.somehost/project/package or osc ls alias://project/package "alias" is an alias for this apiurl which can be configured in the ~/.oscrc. If you see this url-like syntax for the first time you might think that it makes things much more complicated (and even more to type) but it is advantageous: - in most cases it is obvious if a command is a remote command or local working copy command - this way we get rid of ambiguities: Suppose we support the following command ("<foo>" indicate that "foo" is an optional argument): binaries get api://project/package <repo/arch> binaries get <repo/arch> (if $PWD is a package working copy the project and package arguments will be read from it) Possible invocations are: osc binaries get api://foo/bar standard/i586 # get all binaries for this repo and arch osc binaries get api://foo/bar # get all binaries for all repos and all arches # now suppose $PWD is a package working copy: osc binaries get standard/i586 # get all binaries for this repo and arch (project and package are read from the working copy) osc binaries get api://foo/bar # gets all binaries for all repos and all arches (project is "foo" and package is "bar") In the latter invocation we're still in a package working copy but ignore it and use the project and package arguments which were specified. Note: in this case a special (like the url-like) syntax is required otherwise osc is unable to distinguish between a project/package and repo/arch argument. Once again this is just a _proposal_ - feedback is very welcome! Marcus [1] http://www.google-melange.com/gsoc/project/google/gsoc2011/mhuewe/13001 The attached ui.html.gz file can be used to navigate easier through the list of commands (I just gzip'ed it to make mlmmj happy). The attached ui.txt file is just generated via "w3m -dump ui.html".

7 18

[opensuse-buildservice] Licenses
by Pavol Rusnak 07 Jun '11

07 Jun '11

Hi! I just saw the following OBS request from Ciaran: >> Correct syntax from http://spdx.org/licenses/ >> -License: BSD >> +License: BSD-3-Clause I noticed that there was licensing crossdistro summit at LinuxTag. Does that mean that all distributions agreed to use abbreviations from the mentioned document in their packages? (I recon we were using BSD3c for this particular license, also we use GPLv2+ while the document mentions GPL-2.0+). If yes, then it is really cool and you should do a blogpost about the results of the summit (which you should do anyway I guess ;-)). Also there should be a tool that fixes spec file entries in OBS automagically and we'll put the same replacement magic in our spec-cleaner ... Thanks for the clarification! -- Best Regards / S pozdravom, Pavol RUSNAK SUSE LINUX, s.r.o openSUSE Boosters Team Lihovarska 1060/12 PGP 0xA6917144 19000 Praha 9 prusnak[at]opensuse.org Czech Republic -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

4 3

[opensuse-buildservice] [gsoc] osc code cleanup - summary of week 2
by Marcus Hüwe 06 Jun '11

06 Jun '11

Hi, here's a small summary of the 2nd (coding) week. This week I spent most of my time with working on an OO-style class for doing http requests: * it's possible to switch the http(s) implementation without touching any library code * supports response validation (if a schema was specified for the request) Currently I'm still working on the "remote models": * decided to use lxml.objectify [1]: - goal is to encapsulate the xml logic solely into the object itself - example workflow: prj = RemoteProject('some_name') prj.title = 'dummy' prj.description = 'foo bar' repo = prj.add_repository(name='openSUSE_Factory') repo.add_path(project='openSUSE:Factory', repository='standard') repo.add_arch('i586') # change arch to x86_64 repo.arch[0] = 'x86_64' repo.save() Minor stuff: * decided to use the "logging" module: this way we can easily add "debug" and "info" etc. messages and it's up to the "client" which messages it wants to display (I'm not talking about the messages which are displayed when "osc up" is called or something like that) Marcus [1] http://lxml.de/objectify.html -- 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] python fails on obs
by peer 02 Jun '11

02 Jun '11

Hi, Looks like my previous message got rejected by the mailman... My python packages fails. They are just backports from Debian and so builds fine on Debian an Ubuntu, but they fail at OBS :( Because pretty some packages rely on python, I end up in a dependency hell for my project. Comments, support would be welcome. ~P https://build.opensuse.org/package/live_build_log?arch=i586&package=python-… -- 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] Random build failures
by Guido Berhoerster 01 Jun '11

01 Jun '11

Hello, I'm getting seemingly random build failures because of error: Couldn't exec /usr/lib/rpm/mimetypes.prov: No such file or directory Manually triggering a rebuild mostly results in a successful build. -- Guido Berhoerster -- 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] - add 'requestbugownership' command for setting the bugowner via request
by Sascha Peilicke 01 Jun '11

01 Jun '11

Just as a side note, this is not the first example, but one of those commits that made a total rewrite necessary. By quality, the last ones by Ludwig and Vincent aren't any better either. Ideally, fixing sth. shouldn't be only about adding lines but about re-factoring lines. Otherwise the next commiter might be tempted to add his personal 'osc scratchmyback' command w/o communication too. @suse-tux: For the osc rewrite, I strongly urge you to enforce peer-reviews for commits. Or even better, don't let anyone commit directly but let them file merge requests, which can be reviewed and commented appropriatly. Otherwise the new osc will end up exactly like the current one, as an unmaintainable pile of crap code. We also should think about adapting a similar policy for OBS code, but I fear this would break quite some odd habbits... On Wednesday 01 June 2011 09:28:33 OBS osc wrote: > From: Adrian Schröter <adrian(a)suse.de> > > --- > NEWS | 1 + > osc/commandline.py | 24 +++++++++++++++++++----- > 2 files changed, 20 insertions(+), 5 deletions(-) > > diff --git a/NEWS b/NEWS > index f9bb6a6..3002937 100644 > --- a/NEWS > +++ b/NEWS > @@ -1,5 +1,6 @@ > 0.132 > - rdelete and undelete command requesting now a comment > + - add 'requestbugownership' command for setting the bugowner via request > # > # Features which requires OBS 2.3 > # > diff --git a/osc/commandline.py b/osc/commandline.py > index 2090d7b..04c091f 100644 > --- a/osc/commandline.py > +++ b/osc/commandline.py > @@ -1533,18 +1533,23 @@ Please submit there instead, or use > --nodevelproject to force direct submission. > > @cmdln.option('-m', '--message', metavar='TEXT', > help='specify message TEXT') > - @cmdln.option('-r', '--role', metavar='role', default='maintainer', > + @cmdln.option('-r', '--role', metavar='role', > help='specify user role (default: maintainer)') > + @cmdln.alias("reqbugownership") > + @cmdln.alias("requestbugownership") > @cmdln.alias("reqmaintainership") > @cmdln.alias("reqms") > + @cmdln.alias("reqbs") > def do_requestmaintainership(self, subcmd, opts, *args): > - """${cmd_name}: requests to add user as maintainer > + """${cmd_name}: requests to add user as maintainer or bugowner > > usage: > osc requestmaintainership # for > current user in checked out package osc requestmaintainership USER > # for specified user in checked out package osc > requestmaintainership PROJECT PACKAGE # for current user osc > requestmaintainership PROJECT PACKAGE USER # request for specified > user + > + osc requestbugownership ... # accepts > same parameters but uses bugowner role > > ${cmd_option_list} > """ > @@ -1570,14 +1575,23 @@ Please submit there instead, or use > --nodevelproject to force direct submission. else: > raise oscerr.WrongArgs('Wrong number of arguments.') > > - if not opts.role in ('maintainer', 'bugowner'): > + role = 'maintainer' > + if subcmd in ( 'reqbugownership', 'requestbugownership', 'reqbs' > ): + role = 'bugowner' > + if opts.role: > + role = opts.role > + if not role in ('maintainer', 'bugowner'): > raise oscerr.WrongOptions('invalid \'--role\': either specify > \'maintainer\' or \'bugowner\'') if not opts.message: > opts.message = edit_message() > > r = Request() > - r.add_action('add_role', tgt_project=project, tgt_package=package, > - person_name=user, person_role=opts.role) > + if role == 'bugowner': > + r.add_action('set_bugowner', tgt_project=project, > tgt_package=package, + person_name=user) > + else: > + r.add_action('add_role', tgt_project=project, > tgt_package=package, + person_name=user, person_role=role) > r.description = cgi.escape(opts.message or '') > r.create(apiurl) > print r.reqid -- With kind regards, Sascha Peilicke SUSE Linux Products GmbH - GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer Maxfeldstraße 5, 90409 Nuernberg, Germany - HRB 16746 (AG Nuernberg)

3 4