June 2011 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] unresolvable confusion
by Robert Schweikert 21 Jun '11

21 Jun '11

Hi, In the OpenNebula project ( https://build.opensuse.org/project/show?project=Virtualization%3ACloud%3AOp… ) I pulled in pwgen to satisfy a dependency. I disabled the package build for openSUSE targets and have it enabled for the SLES 11 SP1 target. The package build is successful ( https://build.opensuse.org/package/show?package=pwgen&project=Virtualizatio… ), yet the SLES 11 SP1 target shows a build failure with "unresolvable" for pwgen. What am I missing? Thanks, Robert -- Robert Schweikert MAY THE SOURCE BE WITH YOU SUSE-IBM Software Integration Center LINUX Tech Lead rschweikert(a)novell.com rschweikert(a)ca.ibm.com 781-464-8147 -- 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] Build Team Meeting
by Michael Schroeder 21 Jun '11

21 Jun '11

present: mls, saschpe, lars * service script quality * build flags implementation * product builder host Service Script Quality ====================== Many service scripts have bad error reporting or fail with strange messages when something goes wrong. Thus we're going to review the scripts and the setup code to improve the robustness and error handling. Build Flags =========== Currently API and backend have different ideas of how the build flags work, leading to confusion. We'll unify this (and also fix a bug in the backend code). The algorithm will be: - each matching enable/disable line gets a score, defined by: +1 if it's a disable flag +2 if the arch is specified +4 if the repo is specified Thus <disable arch="i586"> has a score of 1+2 = 3, <enable repo="openSUSE_Factory" arch="x86_64"> has a score of 6 - the entry with the highest score wins. ISO Builder Host ================ Lars is setting up a new host dedicated for product building. Products are currrently built in the hosts where the schedulers are running, leading to a noticable slowdown. Cheers, Michael. -- Michael Schroeder mls(a)suse.de SUSE LINUX Products GmbH, GF Jeff Hawn, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- 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] problem while commiting
by Johannes Weberhofer 21 Jun '11

21 Jun '11

Do you have an hint, what's going wrong here? # osc commit Sending php5-pear-pel.changes Sending php5-pear-pel.spec Transmitting file data ..Server returned an error: HTTP Error 400: Bad Request Can't use string ("server:php:applications/php5-pea") as a HASH ref while "strict refs" in use at /root/bs//bs_srcserver line 274. https://build.opensuse.org/package/show?package=php5-pear-pel&project=home%… I see the message "Files could not be expanded: service in progress", and a huge error message in the sources. 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

1 0

[opensuse-buildservice] Specifying different debian.control files for different Ubuntu versions
by David Jarvie 20 Jun '11

20 Jun '11

Is it possible to specify different versions of debian.control for building for different Ubuntu versions? For RPM distros, it's possible to provide project-openSUSE_11.3.spec which will be used in preference to project.spec for openSUSE 11.3 - is there a similar possibility for debian.control? Alternatively, can conditionals be specified inside debian.control in the same manner as %if ... %endif in .spec file? -- David Jarvie.

2 2

[opensuse-buildservice] Specification for OBS light project concept
by Dominig ar Foll 20 Jun '11

20 Jun '11

Hello, those who have discussed with me during the MeeGo Conference in San Francisco, know that I have started a small project to create a Light version of OBS. The goal of the project is to ease the access to OBS for embedded developers and initial investigation team which have to select an embedded OS, by creating a tool which follows their traditional development process (working locally in chroot) but keeps the compatibility with the OBS. Some of the module that we are planning could potentially be of interest for the real OBS (called Full OBS in my spec). In particular the the automatic creation of patch files from a modified chroot and the UI for MIC2 could become generic features. All created new code will be GPL2. Your feedback is welcome. All discussion will take place on the MeeGo distribution-tools mailing list. http://lists.meego.com/listinfo/meego-distribution-tools The file is on the MeeGo Wiki. http://wiki.meego.com/images/SpecOBSLight-1_V-0-6.pdf -- 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

6 8

[opensuse-buildservice] OBS junit tests support
by Antonio Cavallo 20 Jun '11

20 Jun '11

Hi, I was wondering if there's any support junit style test support during a package build. My scenario case is: * a build is performed * as part of the build xml files are emitted (junit style) * there'll be a report page for such results This is a widely used scenario on several companies. Thanks Antonio -- 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] Importing rubygem-json to my project
by Robert Riemann 20 Jun '11

20 Jun '11

Hi all, my project (kubeplayer) needs th ruby json gem installed, which is available as rubygem-json in a foreign home repo, but not in the official repos of opensuse. How can I import this package to my repo to fullfil its dependency? Json belongs to the std libs from ruby 1.9.x on. I was really suprised, that a modern distro like opensuse still delivers ruby 1.8.x! Kind regards, Robert -- 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] [gsoc] osc code cleanup - summary of week 4
by Marcus Hüwe 19 Jun '11

19 Jun '11

Hi, here's a small summary of the 4th (coding) week. I spent most of the time with writing the RemoteFile classes and the BuildResult class (+ testcases of course:) ). TODO for this week: * improve RemoteFile classes * add APIInfo class: - resolve url-like parameters (api://foo/bar repo/arch) - raise an exception if required parameters are missing - initialize optional parameters with the config default - encapsulate "context-sensitivity" logic (sometimes parameters should be read from the working copy (like apiurl, project or package)) Marcus -- 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] Solution for Tagging a version of a project and copying from an OBS with Anonymous login only
by Dominig ar Foll (Intel OTC) 18 Jun '11

18 Jun '11

Hi, I had to solve the problem of delivering software from an OBS instance to an other OBS instance in a controlled fashion. In particular I needed to provid a coherent set of the packages without being affected by possible changes which could take place between the snapshot validation and the actual time when the customer will actually do the copy. I also needed a solution which would manage time out an error with out having to restart the copy all the project at every network error. My proposed solution consists in creating a Tag for the project that I want to deliver. The Tag contains the list of all the packages as well as their revision number at the time of creation. The Tag file is created with a script called "obstag" and the tag file can be delivered to the customer by mail. With that Tag file the customer can at it's leisure (at least as long as the project is not deleted from your source OBS) collect the packages version that you wanted him to receive directly from your OBS (you need to have the public API open or give a login to the customer). To copy from a remote OBS with the obs2obscopy script, the customer will have to create of a local project which is a link to the remote OBS public API. I have tested the solution with the https://api.meego.com/public public API and it works. Limit: The public API of an OBS does not let extract the log for a packages and so obstag will create a tag file which only contains the package name when activated on a remote project via a link using a remote public API. Bug Surely but not seen yet :-) The code is available here. http://wiki.meego.com/images/ObsTagCopy.tgz -- 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

1 0

[opensuse-buildservice] OBS 2.3 Beta 2
by Adrian Schröter 17 Jun '11

17 Jun '11

OBS 2.3 Beta 2 is out! ====================== This OBS 2.3 release is now feature complete. We changed a bit more then expected: * New source service mode handling is default now. Server side services get applied when listing in expand mode, like with source links. * Configuration UI to setup OBS instance name and description. * MeeGo.com is pre-configured now. * backend daemons have integrated runtime management * A large number of bugfixes Current State ============= Open tasks for next weeks are: * Get documentation in a better shape so that we can switch openSUSE maintenance using the new mechanisms. * There are absolute zero known regressions known atm. So really everything should be at least as good as in OBS 2.1.x :) Feel free to run it on your production system, we do it also on build.opensuse.org :) The call for help ================= There are still a number of areas where some clean up is needed. For example we have * 20 FIXME2.2 lines in the code (means that read access handling code needs checking) * 10 FIXME2.3 lines in the code (maintenance code needs a revisit here) * Unknown state of Cross architecture builds. It would be nice if someone can help so that the OBS Appliance can build for arm architectures out of the box. You can stop here when you read already Beta 1 announcement ,) OBS 2.3 main features ===================== The main features of this release are * Full distribution maintenance support. This includes support for the workflow in OBS and also the patch channel generation. This functionality can be used at full glance with coordination and review teams or just in parts. * Read access protection for projects (as planned for OBS 2.2) Apart from that we have many smaller improvements, esp. in the area of request handling and the webui integration. Download it =========== As usual, you find current packages or an appliance in openSUSE:Tools:Unstable project. OBS 2.3 Beta 2 is tagged as version 2.2.84. Please read here for usage details for the appliance: http://en.opensuse.org/openSUSE:Build_Service_Appliance Please find the full Release Notes below: ========================================= # # Open Build Service 2.3 # Please read the README.SETUP file for initial installation instructions or use the OBS Appliance from http://en.opensuse.org/Build_Service/OBS-Appliance There is also an install medium with installs OBS on hard disc now. README.UPDATERS file has informations for updaters. OBS Appliance users who have setup their LVM can just replace their appliance image without data loss. The migration will happen automatically. Main Features ============= The main topic of OBS 2.3 is to deliver a number of features to allow product maintenance handling with OBS. No external build or tracking tool is needed to do the typical maintenance workflow of a distribution team. The usage of these features are documented in the OBS book: http://doc.opensuse.org/products/draft/OBS/obs-reference-guide_draft/ OBS 2.3 comes also with a feature which was planned for the not released OBS 2.2 version. New created projects can set to hidden. That means no source or binary read access is possible. Please read the following for details: To be considered regarding read access checks ============================================= * "access" flag is hiding and protecting entire project. This includes binaries and sources. It can only be used at project creation time and can just be globally enabled (aka make it public again) afterwards. This flag can only be used on projects. * "sourceaccess" flag is hiding the sources to non maintainers, this includes also debug packages in case the distribution is supporting this correctly. This flag can also only be used at package creation time. There is no code yet which is checking for possible references to this package. This flag can be used on projects or packages. * "downloadbinary" permission still exists like before. However, unlike "access" and "sourceaccess" this is not a security feature. It is just a convinience feature, which makes it impossible to get the binaries via the API directly. But it still possible to get the binaries via build time in any case. Security aspects ================ Former OBS releases lack protection against XSS attacks. Esp. public instances should update to OBS 2.3, which is using rails plugins to protect against XSS attempts. This fixes (CVE-2011-0462). Building in "chroot" environments is known to be unsecure. XEN and KVM is considered to be a secure environment. However KVM is known to be unstable, it leads to build failures. Apache & mod_rails switch ========================= Former OBS versions used lighttpd as default web server. We have switched to apache with mod_rails (known as passenger) as default web server. We have also added an mod_xforward apache module to allow unloading the rails stack with long running requests to the backend. Please note that current apache2 versions have a known bug which cuts the http headers regardless to it's configuration. Please use apache2 from openSUSE:Tools project to get this fixed for now. Also the patched version of rubygem-passenger from openSUSE:Tools project is recommended. Known Regressions to 2.1: ========================= * none yet Features: ========= * web interface improvements: - package filtering - Generic authentification proxy support - delete request dialogs - request and review handling improvements - social features, i.e. show other user's projects and requests * api - review of requests by project or package maintainers is possible now (FATE #310806) - better Cross-Site Scripting (XSS) protection - larger number of request handling improvements * backend: Changes: ======== * web interface - bug reporting for projects/packages is only possible if a bugowner is set - XSS protection plugins are used now (CVE-2011-0462) * api - It was not possible so far to create submit requests from packages where no write access exists. This is possible now, but the source package maintainer will get asked for review the request. - the route /group/$GROUP is showing correct xml description and no directory anymore * new source service handling - Source services do not generate an extra commit for the result. Instead they work like source links, this means the generated files become visible with expand=1 parameter. - The state of the service is visible via serviceinfo element in package file list. * The backend is only accepting write access from the localhost by default. Build results can be still delivered from any host. This can be changed in BSConfig.pm Deprecated: =========== The following calls have been marked as deprecated, they will get removed in OBS 3.0 * api - /person/$LOGIN/group -> use /group?login=$LOGIN instead Requirements: ============= * The OBS server should not run on a system with less than 2GB memory. 4GB is recommended, esp. when the same system is also building packages. * Use osc 0.132 or later to get access to the new features. * Usage of Ruby on Rails version 2.3.11 is recommended. -- 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] OBS scheduler downtime
by Michael Schroeder 17 Jun '11

17 Jun '11

Hey OBS users, Adrian managed to kill the schedulers, so there'll be a downtime of about two hours until we're building packages again. Sorry, Michael. -- Michael Schroeder mls(a)suse.de SUSE LINUX Products GmbH, GF Jeff Hawn, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

5 13

[opensuse-buildservice] Re: [PATCH] [webui] minor design improvement
by Sascha Peilicke 17 Jun '11

17 Jun '11

On Friday 17 June 2011 13:57:38 you wrote: > From: Adrian Schröter <adrian(a)suse.de> > > --- > src/webui/app/views/package/_services.html.erb | 2 +- > 1 files changed, 1 insertions(+), 1 deletions(-) > > diff --git a/src/webui/app/views/package/_services.html.erb > b/src/webui/app/views/package/_services.html.erb index 1aad51f..6274011 > 100644 > --- a/src/webui/app/views/package/_services.html.erb > +++ b/src/webui/app/views/package/_services.html.erb > @@ -34,7 +34,7 @@ >  > <% if @serviceerror %> > <div id="error" class="error"> > - <h4> > + <br/><h4> > Source processing is currently broken: > </h4> > <pre id="code" class="text"> This looks like the <div> could've become a <p> to achieve the same? We really need to re-freshen our Bento theme... -- Mit freundlichen Grüßen, Sascha Peilicke SUSE Linux Products GmbH

1 0

[opensuse-buildservice] Search bar annoyance
by Cristian Rodríguez 17 Jun '11

17 Jun '11

Hi: In the webUI, there is a search bar next to the "watchlist", it would be great if it strips leading and trailing whitespaces " home:iexists" , "home:iexists " return no results even if those repos exist. Cheers. -- 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] [PATCH] Add config entry to allow permanent usage of ccache
by Cristian Rodríguez 17 Jun '11

17 Jun '11

Signed-off-by: Cristian Rodríguez <crrodriguez(a)opensuse.org> --- osc/build.py | 2 +- osc/conf.py | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/osc/build.py b/osc/build.py index c85be15..54dc6d2 100644 --- a/osc/build.py +++ b/osc/build.py @@ -399,7 +399,7 @@ def main(apiurl, opts, argv): buildargs.append('--icecream=%s' % num) xp.append('icecream') xp.append('gcc-c++') - if opts.ccache: + if opts.ccache or config['ccache'] != '0': buildargs.append('--ccache') xp.append('ccache') if opts.linksources: diff --git a/osc/conf.py b/osc/conf.py index 9494906..8c359a7 100644 --- a/osc/conf.py +++ b/osc/conf.py @@ -91,7 +91,7 @@ DEFAULTS = { 'apiurl': 'https://api.opensuse.org', 'build-jobs': _get_processors(), 'builtin_signature_check': '1', # by default use builtin check for verify pkgs 'icecream': '0', - + 'ccache': '0', 'debug': '0', 'http_debug': '0', 'http_full_debug': '0', -- 1.7.4.1 -- 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] Accepteted request results in empty package
by Johannes Weberhofer 16 Jun '11

16 Jun '11

Dear all, the request https://build.opensuse.org/request/show/73634 has been accepted but the resulting package is empty. How can the problem be solved? 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

3 5

[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