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]
Re: [opensuse-packaging] problem with spec file for kdepim3
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. Marcus [1]: the spec file will be send via POST to the server and the BS calculates the dependencies etc. for this build-target. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-packaging] problem with spec file for kdepim3
2008/1/3, Bernhard Walle <[EMAIL PROTECTED]>:
> * Ladislav Michnovič <[EMAIL PROTECTED]> [2008-01-03 15:50]:
> > 2008/1/3, Bernhard Walle <[EMAIL PROTECTED]>:
> > > * 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?
> >
> > Yes, it is sufficient to have the source tarball, patches and spec
> > file on your local hard disk.
>
> But you have to create the package in the BS, right?
Yes. You have to create package in Build Service, but you don't need
to copy sources into BS.
Ladislav.
N�r��y隊Z)z{.��ZrF��x>�{.n�+���Ǩ�h��]�ب��\�i��� ��$j���^��)z{.�
Re: [opensuse-packaging] problem with spec file for kdepim3
* Ladislav Michnovič <[EMAIL PROTECTED]> [2008-01-03 15:50]: > 2008/1/3, Bernhard Walle <[EMAIL PROTECTED]>: > > * 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? > > Yes, it is sufficient to have the source tarball, patches and spec > file on your local hard disk. But you have to create the package in the BS, right? Thanks, Bernhard - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-packaging] problem with spec file for kdepim3
2008/1/3, Bernhard Walle <[EMAIL PROTECTED]>: > * 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? Yes, it is sufficient to have the source tarball, patches and spec file on your local hard disk. Regards Ladislav. > > > Thanks, >Bernhard > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [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 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. Richard. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-packaging] problem with spec file for kdepim3
* 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? Thanks, Bernhard - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-packaging] problem with spec file for kdepim3
On Monday 31 December 2007, Rajko M. wrote: > I tried to build source package for kdepim and rpmbuild complained on > missing dependencies. while it might work with rpmbuild, please use "build" (available from openSUSE:Tools iirc) or "osc build" for building opensuse packages. Greetings, Dirk -- RPMLINT information under http://en.opensuse.org/Packaging/RpmLint - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [opensuse-packaging] problem with spec file for kdepim3
Am Montag 31 Dezember 2007 schrieb Rajko M.: > I tried to build source package for kdepim and rpmbuild complained on > missing dependencies. > > # rpmbuild -bs kdepim3.spec > error: Failed build dependencies: > pilot-link-devel is needed by > kdepim3-3.5.7.enterprise.0.20070904.708012-9.i586 > gpgme-devel is needed by > kdepim3-3.5.7.enterprise.0.20070904.708012-9.i586 > > # zypper in pilot-link-devel gpgme-devel > package 'pilot-link-devel' not found > package 'gpgme-devel' not found use zypper install -C and it will install the packages providing it Greetings, Stephan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[opensuse-packaging] problem with spec file for kdepim3
I tried to build source package for kdepim and rpmbuild complained on missing dependencies. # rpmbuild -bs kdepim3.spec error: Failed build dependencies: pilot-link-devel is needed by kdepim3-3.5.7.enterprise.0.20070904.708012-9.i586 gpgme-devel is needed by kdepim3-3.5.7.enterprise.0.20070904.708012-9.i586 # zypper in pilot-link-devel gpgme-devel package 'pilot-link-devel' not found package 'gpgme-devel' not found I found replacements using YaST search for what provides them and installed them. After that source package was built without complains. # rpm -q --whatprovides pilot-link-devel gpgme-devel libpisock-devel-0.12.2-26 libgpgme-devel-1.1.5-31 I changed kdepim3.spec replacing nonexistant files with above 2. This is the 'diff -u' output: --- kdepim3.spec2007-09-25 16:59:15.0 -0500 +++ kdepim3.spec-new2007-12-31 14:51:35.0 -0600 @@ -18,10 +18,10 @@ BuildRequires: gnokii-devel %endif %if %suse_version > 1010 -BuildRequires: libopensync-devel pilot-link-devel +BuildRequires: libopensync-devel libpisock-devel %endif %if %suse_version > 1000 -BuildRequires: gpgme-devel +BuildRequires: libgpgme-devel %else BuildRequires: gpgme libgpg-error-devel %endif I hope this was correct way to change spec file. -- Regards, Rajko - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
