June 2011 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] Introducing 0install developers
by Jos Poortvliet 16 Jun '11

16 Jun '11

(sending again as it didn't end up on the OBS ML) Hi all, I'd like to introduce to you Thomas Leonard and Anders Björklund, two 0install [1] developers. I recently got in contact with them and suggested they might get OBS to support creating 0install packages/recepies/scripts. 0install is a different beast than the usual packages OBS builds, but it seemed to me quite awesome if OBS users could also opt to create 0install packages. Thomas has already submitted the zeroinstall-injector package [2] for inclusion in factory. Technically, 0install is different, but I understand from Anders that it should be possible: > There is no fundamental difference in making an RPM package from > a specfile, compared with making a XML+TBZ package with 0compile. > > In the .rpm, you have the metadata, signature and archive combined > into one file while in ZI you have them separated into two files. Anders, Thomas, here is the documentation on adding a build target: http://en.opensuse.org/openSUSE:Build_Service_adding_build_targets However I'm not sure this'll work for 0install. So, people on the OBS ML, could you tell the gents if you're interested in working with them on this and where they should start with getting a 0install build target? Cheers, Jos [1] http://0install.net/ [2] https://build.opensuse.org/project/show?project=home%3Atalex5

3 2

[opensuse-buildservice] Strange "_service:format_spec_file:" in branched package
by Johannes Weberhofer 16 Jun '11

16 Jun '11

Dear all, I have branched and modified a package https://build.opensuse.org/package/files?package=phpMyAdmin&project=home%3A… When I like to submit the changes back, the system likes me to submit a _service:format_spec_file:phpMyAdmin.spec file, too. What is that file for? Best regards, Johannes -- Johannes Weberhofer Weberhofer GmbH, Austria, Vienna -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

4 8

[opensuse-buildservice] Source services and recompression of tar balls
by Andreas Jaeger 16 Jun '11

16 Jun '11

My source tarballs was recompressed from tar.gz to tar.bz2 - how is this handle this? The spec file contains: Source3: http://fileschanged.sourceforge.net/fileschanged-%fc_version.tar.bz2 But this is wrong, since only the tar.gz is available there. What's the proper fix for this? Andreas -- Andreas Jaeger, Program Manager openSUSE aj(a){novell.com,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

3 4

[opensuse-buildservice] New Source Service mode actived!
by Adrian Schröter 16 Jun '11

16 Jun '11

build.opensuse.org is running now with the new source service mode. We recommend to upgrade to osc 0.132 version as available in openSUSE:Tools project if you work with source services. The difference to the old way source service were handled is that with the new mode, no "source service" commits are generated. This means, the history just contains the commits done by the user, which makes things like revision diffs much easier. The source service result is handled as an internal commit, like with source links. Builds are still done with those internal commits. A manual service run trigger is handled as commit by the user, so it is part of the history. This solves also the blocking of commits (403 errors) during a service run. Michael and Adrian -- Adrian Schroeter SUSE Linux Products GmbH email: adrian(a)suse.de

4 9

[opensuse-buildservice] Re: [PATCH] Align --no-service commit command parameter to build command param style.
by Adrian Schröter 16 Jun '11

16 Jun '11

Am Thursday, 16. June 2011, 11:44:02 schrieb OBS osc: > From: Sascha Peilicke <saschpe(a)suse.de> > > --- > osc/commandline.py | 2 +- > 1 files changed, 1 insertions(+), 1 deletions(-) > > diff --git a/osc/commandline.py b/osc/commandline.py > index 853199a..5fa720f 100644 > --- a/osc/commandline.py > +++ b/osc/commandline.py > @@ -3655,7 +3655,7 @@ Please submit there instead, or use --nodevelproject to force direct submission. > help='Skip the source validation') > @cmdln.option('-v', '--verbose', default=False, action="store_true", > help='Run the source services and validation with verbose information') > - @cmdln.option('--skip-local-service-run', default=False, action="store_true", > + @cmdln.option('--no-service', default=False, action="store_true", > help='Skip service run of \'localonly\' or \'trylocal\' configured source services') that is missleading, because remote service will still run. > def do_commit(self, subcmd, opts, *args): > """${cmd_name}: Upload content to the repository server > -- 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] openSUSE Conference and BoF sessions
by Jos Poortvliet 15 Jun '11

15 Jun '11

Hi all, A couple of days ago I wrote an article for news.o.o about BoF sessions for the openSUSE conference. As you know we're looking for more 'read-write' sessions, as opposed to the traditional one-way-talk style. A BoF is one of such a session, others would be workshops (to teach some skill) and hack sessions (get coding or packaging or other work done). If you want to know what we mean by BoF and what we are looking for in that area, read http://bit.ly/lIzf5E A short synopsis follows. A BoF (Birds of a Feather) meeting is an informal, open session which brings together people with a comon interest. An example topic would be "improve the package submission process for Factory" or "discuss what software to include in the GNOME liveCD". Organizing a BoF is VERY easy: a good title (problem description) will make sure the right people turn up and then the work is half done. You don't need more than pen and paper to ensure an effective meeting: make sure the discussion doesn't wander off in all directions, but results in written-down decisions with actions and names attached if possible. Afterwards, send a report to the mailinglist to inform those not at the meeting! Note that you do NOT have to be a core developer of a team to organize a BoF! Anyone can do it. If you're not entirely sure you'll make it to the conference, just talk to the team about it. In case you can't be there, someone can take over! You don't have to be an openSUSE community member to organize a BoF at the openSUSE conference either. We are more than happy if a Fedora member wants to talk about the Fedora support in OBS or if the KDE team wants to discuss the educational applications with the EDU team. Planning a BoF is similarly easy. Send a proposal with the title and rough outline via the conference website: http://bit.ly/j9TtUe It does not need a nailed down agenda, not even a super concrete topic - for example, if you feel the Medical team needs to get together to talk about what's part of the DVD and what not, that's concrete enough. Planning a BoF now is important: we (the conference team) can ensure there is no overlap between BoF's and talks. While we will leave room to schedule BoF's at the conference, there's a good chance the only spots left will be early in the morning and nobody likes those :D So, go to http://bit.ly/j9TtUe and shoot in a proposal!

1 0

[opensuse-buildservice] OSC access in anonymous
by Dominig ar Foll (Intel OTC) 15 Jun '11

15 Jun '11

Hi, I need to copy package from an OBS where I have no login. The Web UI accept anonymous connection and I can create a link on my private OBS to point on that remote OBS anonymously. What I do not know ho wto do, is to run an osc ls command on the remote OBS anonymously to extract the package name and create a loop in my script. Any idea how to do so ? Thanks. -- Dominig ar Foll MeeGo TV Open Source Technology Centre Intel SSG -- 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] Fwd: Wrong link to OBS forums
by Rupert Horstkötter 15 Jun '11

15 Jun '11

Fwding. Have been unsubscribed from the list previously. Best, R ---------- Forwarded message ---------- From: Rupert Horstkötter <rhorstkoetter(a)opensuse.org> Date: 2011/6/15 Subject: Wrong link to OBS forums To: opensuse-buildservice(a)opensuse.org Cc: Kim Groneman <kgroneman(a)novell.com>, Henne Vogelsang <hvogel(a)opensuse.org> Hi there, at https://build.opensuse.org/ there is a link (in the footer) to the OBS forums. Unfortunately the link is invalid and should point to http://forums.opensuse.org/english/other-forums/development/open-build-serv… Currently it links to http://forums.opensuse.org/english/other-forums/development/opensuse-build-… May you please fix that accordingly? CC:ing Kim and Henne for their reference. Thanks, R -- Rupert Horstkötter open-slx Community Manager openSUSE Board Member http://open-slx.com/ -- Rupert Horstkötter open-slx Community Manager openSUSE Board Member http://open-slx.com/ -- 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 build --local-package broken in 0.132.3
by Michal Marek 15 Jun '11

15 Jun '11

Hi, this worked until recently: $ osc --version 0.131 $ osc co openSUSE:Factory hello ... $ cd openSUSE:Factory/hello $ rm -rf .osc/ $ osc build --local-package --alternative-project=openSUSE:Factory standard x86_64 hello.spec Building hello.spec for standard/x86_64 ... But it doesn't work anymore: $ osc --version 0.132.3 $ osc build --local-package --alternative-project=openSUSE:Factory standard x86_64 hello.spec Error: "/home/mmarek/openSUSE:Factory/hello" is not an osc package working copy. We use this option regularly to build kernel packages from git, that do not have any .osc metadata. Michal -- 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] [Seeking Feedback] OBS mobile: request page makeover
by Justine L. 15 Jun '11

15 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

2 1