Re: [opensuse-packaging] problem with spec file for kdepim3
On Friday 04 January 2008 14:08:25 wrote Marcus Hüwe: > On 2008-01-04 12:10:36 +0100, Adrian Schröter wrote: > > On Thursday 03 January 2008 23:25:05 wrote Marcus Hüwe: > > > On 2008-01-03 15:49:23 +0100, Richard Guenther wrote: > > > > On Thu, 3 Jan 2008, Bernhard Walle wrote: > > > > > * Dirk Mueller <[EMAIL PROTECTED]> [2008-01-03 14:19]: > > > > > > "osc build" for building opensuse packages. > > > > > > > > > > Just a side question: Is it possible to use "osc build" without > > > > > importing that package into the Build Service? > > > > > > > > Only if you fix osc. > > > > > > Hmm it's not osc's fault. At the moment the api only supports: > > > > > > GET /build/_buildinfo > > > POST /build/_buildinfo > > > > > > I think something like: > > > > > > POST /build///_buildinfo [1] > > > > > > is needed to get the buildinfo without importing anything to the BS. > > > > This would also need to be added to the backend ... > > > > One open question is, which release numbers shall the backend use in that > > case ? Maybe simply falling back to "0" ... > > > > I think the package name is not needed for anything else atm. > > > > best is you create an enhancement bugreport in bugzilla for this. > > No need to create an enhancement report for the backend because it already > supports it;) > If you use "_repository" as a package name you can retrieve the buildinfo > for a package which doesn't exist in the BS (this feature is hidden in > "bs_repserver", sub getbuildinfo_post). > > Example: > curl -u : -X POST -d "$(cat )" \ > https://api.opensuse.org/build/openSUSE:10.3/standard/i586/_repository/_bui >ldinfo > > Maybe we should add this to the apidocs page? right I have added some lines to the api doc in svn (not yet online). your are the hero of the day (hotd :) adrian -- Adrian Schroeter SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-packaging] problem with spec file for kdepim3
On 2008-01-04 12:10:36 +0100, Adrian Schröter wrote: > On Thursday 03 January 2008 23:25:05 wrote Marcus Hüwe: > > On 2008-01-03 15:49:23 +0100, Richard Guenther wrote: > > > On Thu, 3 Jan 2008, Bernhard Walle wrote: > > > > * Dirk Mueller <[EMAIL PROTECTED]> [2008-01-03 14:19]: > > > > > "osc build" for building opensuse packages. > > > > > > > > Just a side question: Is it possible to use "osc build" without > > > > importing that package into the Build Service? > > > > > > Only if you fix osc. > > > > Hmm it's not osc's fault. At the moment the api only supports: > > > > GET /build/_buildinfo > > POST /build/_buildinfo > > > > I think something like: > > > > POST /build///_buildinfo [1] > > > > is needed to get the buildinfo without importing anything to the BS. > > This would also need to be added to the backend ... > > One open question is, which release numbers shall the backend use in that > case ? Maybe simply falling back to "0" ... > > I think the package name is not needed for anything else atm. > > best is you create an enhancement bugreport in bugzilla for this. > No need to create an enhancement report for the backend because it already supports it;) If you use "_repository" as a package name you can retrieve the buildinfo for a package which doesn't exist in the BS (this feature is hidden in "bs_repserver", sub getbuildinfo_post). Example: curl -u : -X POST -d "$(cat )" \ https://api.opensuse.org/build/openSUSE:10.3/standard/i586/_repository/_buildinfo Maybe we should add this to the apidocs page? Marcus - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-packaging] problem with spec file for kdepim3
On Thursday 03 January 2008 23:25:05 wrote Marcus Hüwe: > On 2008-01-03 15:49:23 +0100, Richard Guenther wrote: > > On Thu, 3 Jan 2008, Bernhard Walle wrote: > > > * Dirk Mueller <[EMAIL PROTECTED]> [2008-01-03 14:19]: > > > > "osc build" for building opensuse packages. > > > > > > Just a side question: Is it possible to use "osc build" without > > > importing that package into the Build Service? > > > > Only if you fix osc. > > Hmm it's not osc's fault. At the moment the api only supports: > > GET /build/_buildinfo > POST /build/_buildinfo > > I think something like: > > POST /build///_buildinfo [1] > > is needed to get the buildinfo without importing anything to the BS. This would also need to be added to the backend ... One open question is, which release numbers shall the backend use in that case ? Maybe simply falling back to "0" ... I think the package name is not needed for anything else atm. best is you create an enhancement bugreport in bugzilla for this. thanks adrian -- Adrian Schroeter SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
