May 2009 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] update repo with delta RPM
by Christian 07 May '09

07 May '09

Hi, just wondering how you create an Update Repo with delta RPMs. (openSUSE:11.1 and openSUSE:11.1:Update) Is/could this done with obs ? How does this work ? Kind Regards Chris -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

2 4

[opensuse-buildservice] Re: [opensuse-svn] r7266 - trunk/buildservice/src/clientlib/python/osc/osc
by Peter Poeml 07 May '09

07 May '09

Hi Michal, On Wed, May 06, 2009 at 05:46:20AM -0600, Novell Forge SVN wrote: > Author: mcihar > Date: 2009-05-06 05:46:17 -0600 (Wed, 06 May 2009) > New Revision: 7266 > > Modified: > trunk/buildservice/src/clientlib/python/osc/osc/cmdln.py > Log: > Add support for generating a man page. > > > Modified: trunk/buildservice/src/clientlib/python/osc/osc/cmdln.py > =================================================================== > --- trunk/buildservice/src/clientlib/python/osc/osc/cmdln.py 2009-05-06 10:08:08 UTC (rev 7265) > +++ trunk/buildservice/src/clientlib/python/osc/osc/cmdln.py 2009-05-06 11:46:17 UTC (rev 7266) > @@ -43,6 +43,8 @@ > import cmd > import optparse > from pprint import pprint > +from core import get_osc_version > +from datetime import date It looks as if the change is principally a very nice thing, but puts osc-specific code and documentation inside the cmdln module. [1] I think it would be better (if not brilliant) if you would enhance the cmdln module in a way that the change is generically useful. At the same time, it would mean that we won't have problems upgrading our in-tree cmdln module when upstream releases a new version. Right now, somebody would need to forward port your changes. Do you think you could leave out just the osc-specific text (providing it to the functionality from somewhere else), so we can achieve the same (great) functionality in a way that's not totally bound to osc? I'm sure that upstream would be interested in this feature. [1] http://code.google.com/p/cmdln/ (The module also exists as python-cmdln package in the buildservice, and it would also be possible to use that instead of an in-tree copy. The package is not on any product though, I think.) Thanks, Peter -- Contact: admin(a)opensuse.org (a.k.a. ftpadmin(a)suse.com) #opensuse-mirrors on freenode.net Info: http://en.opensuse.org/Mirror_Infrastructure SUSE LINUX Products GmbH Research & Development

2 2

[opensuse-buildservice] Querying package revision
by Cornelius Schumacher 07 May '09

07 May '09

Is there a way to query the RPM revision of a package via the API? -- Cornelius Schumacher <cschum(a)suse.de> -- 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] network:/utilities for SLES9
by Andreas Vetter 07 May '09

07 May '09

Hi, is it possible to have the network:/utilities also built for SLES9? Or is there a major problem with that? -- Mit freundlichen Gruessen, Andreas Vetter -- 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] automatic removal of merged branches / temporary packages and projects
by Stanislav Brabec 07 May '09

07 May '09

Hallo. I just spent some time with purging of my obsolete home:sbrabec:branches:anything and got an idea: What about possibility of making some packages and projects as temporary? Such packages could silently disappear whenever request is accepted in the parent project and it becomes just a plain link. Such projects could silently disappear whenever it becomes empty. I guess it may be a default behavior of osc branch. You rarely need something different. -- Best Regards / S pozdravem, Stanislav Brabec software developer --------------------------------------------------------------------- SUSE LINUX, s. r. o. e-mail: sbrabec(a)suse.cz Lihovarská 1060/12 tel: +420 284 028 966, +49 911 740538747 190 00 Praha 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz/ -- 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] Notifications for special/_myrequests
by Klaas Freitag 06 May '09

06 May '09

Hi, I just changed the Hermes filter rules for the special/_myrequests filter that is used for submit requests. The filter was true (== sent a message) if a user with a subscription was either in the source- or targetproject fo the submitrequest. It was changed to: The user is either maintainer in the target project or -package. That means you should get less messages about submitrequests which are more useful. Please let me know if something unexpected happens, Klaas -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

1 0

[opensuse-buildservice] Re: [opensuse-svn] r7264 - trunk/buildservice/src/clientlib/python/osc
by Peter Poeml 06 May '09

06 May '09

On Wed, May 06, 2009 at 03:33:21AM -0600, Novell Forge SVN wrote: > Author: mcihar > Date: 2009-05-06 03:33:18 -0600 (Wed, 06 May 2009) > New Revision: 7264 > > Modified: > trunk/buildservice/src/clientlib/python/osc/setup.py > Log: > Add some metainformation to setup.py and also include correct version > there (it is later used in generated egg file). Cool. This is among the things that I never really took the time to figure out. Thanks a lot! Peter -- Contact: admin(a)opensuse.org (a.k.a. ftpadmin(a)suse.com) #opensuse-mirrors on freenode.net Info: http://en.opensuse.org/Mirror_Infrastructure SUSE LINUX Products GmbH Research & Development

1 0

[opensuse-buildservice] submitreq's are carelessly handled
by Christian 06 May '09

06 May '09

Hi, obs is amazing, and gives us a great chance to contribute to opensuse. I'm using SuSE since 6.4 and I love it, no question. In the past I had to modify/improve my packages to meet my needs. Now there is the possibility to get this improvements not only to opensuse via obs. This is great. But the way submitreq's are handled is much more poor. I have several submitreq's with no reaction for weeks or months. This is really poor. A simple reaction of the package maintainer 'Hi, thanks, will review your mods' will be enough in first, but no feedback for weeks/months is not acceptable IMO. some of my REQ's: 8029 8894 8896 8902 8933 8958 Kind Regards Chris -- 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] Problems with local osc build for debian
by Dennis Sieben 06 May '09

06 May '09

Hi, we have problems doing a local build against our own OBS. It seems like osc tries to fetch the base packages from a location which is not available on our OBS. See below: osc build --alternative-project open-xchange-snapshot DebianEtch i586 *.dsc Building open-xchange-admin-soap_6.9.0.0-0.dsc for DebianEtch/i586 Getting buildinfo from server Updating cache of required packages Trying upstream server for perl-base (Debian:Etch), since it is not on buildservice.netline.de. Trying upstream server for perl-base (Debian:Etch), since it is not on buildapi.netline.de. Error: No more mirrors to try. Failed to retrieve perl-base-5.8.8-7etch4.i386.deb from the following locations (in order): file:///var/tmp/osbuild-packagecache/Debian:Etch/standard/i386/perl-base-5.8.8-7etch4.i386.deb/ http://buildservice.netline.de/repositories/Debian:Etch/standard/i386/perl-… http://buildapi.netline.de//build/Debian:Etch/standard/i586/_repository/per… Can anybody tell me how this must be configured? I've already searched the websides, but I don't find a solution to this. Thanks in advance, Dennis

2 1

[opensuse-buildservice] how to unpublish already published packages ?
by Christian 06 May '09

06 May '09

Hi, I have several branches and noticed that those packages are automatically published. So I considered to disable Publishing for those packages because there is no need to have them published. This was 2 days ago, and those packages are still published. Didn't they get automatically removed when "disabling" publish ? And another thing a found out: I had a branch of "openSUSE:Tools:Unstable" > home:computersalat:branches:openSUSE:Tools:Unstable I deleted this branch some weeks or month ago but published DIR's still there on http://download.opensuse.org/repositories/home:/computersalat:/branches:/op… So is this a feature or a bug ? Kind Regards Chris -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org

4 4