Am Saturday, 25. June 2011, 01:14:09 schrieb Sascha Manns:

Hello Mates,

i have a question. I'm thinking about to use our services to integrate downloadable Sources into the packages.

But which Services i need?

I thought "Create a tarball from SCM repository", "Update sources" and maybe "Validate Sources".

Can this be a good way? Or has anyone ideas/comments about that?

Usually "tar_scm" and "set_version". Check openSUSE:Tools:Unstable osc and build package for an example.

-- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org

Hello Mates, now home:saigkill/calligra runs perfectly. I have the SCM Service, then a recompress Service for making *.tar -> *.bz2 and the Service who changes the Version in the Spec. Now this all produces a package: calligra-1309689103-14.1. But the Enduser don't know if its the right thing. Is it possible to make a outputfile like: calligra-2.3.80-git1309689103? Have a nice day @ all Sascha -- Sincerely Yours Sascha Manns open-slx Community & Support Agent openSUSE Membership Comitee openSUSE Marketing Team Web: http://saigkill.homelinux.net German Community Portal: http://community.open-slx.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org

Hello Adrian, Adrian Schröter wrote at Sunday 03 July 2011:

...

Now this all produces a package: calligra-1309689103-14.1. But the Enduser don't know if its the right thing. Is it possible to make a outputfile like: calligra-2.3.80-git1309689103?

Yes, just define a "versionprefix" parameter in tar_scm service with "2.3.80" for example. Cool (*happy*). Where i can add this? My tar_scm looks like: http://www.pictureupload.de/originals/pictures/030711184150_Auswahl_005.png I think i can't edit more, or?

Have a nice evening... Sascha -- Sincerely Yours Sascha Manns open-slx Community & Support Agent openSUSE Membership Comitee openSUSE Marketing Team Web: http://saigkill.homelinux.net German Community Portal: http://community.open-slx.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org

Am Sonntag, 3. Juli 2011 schrieb Malcolm:

On Sun, 3 Jul 2011 17:47:22 +0200

Sascha Manns wrote:

...

Hello Mates,

now home:saigkill/calligra runs perfectly. I have the SCM Service, then a recompress Service for making *.tar -> *.bz2 and the Service who changes the Version in the Spec.

Now this all produces a package: calligra-1309689103-14.1. But the Enduser don't know if its the right thing. Is it possible to make a outputfile like: calligra-2.3.80-git1309689103?

Have a nice day @ all Sascha

Hi AFAIK, re-compressing the tarball is deprecated (you still get a warning), you should use the pristine source. you get no warning in factory. Older rpmlint may warn, but that's to be ignored.

Greetings, Stephan -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org

Am Monday, 4. July 2011, 11:55:04 schrieb Sascha Manns:

Hello Mates,

Sascha Manns wrote at Sunday 03 July 2011:

...

Adrian Schröter wrote at Sunday 03 July 2011:

...

...

Now this all produces a package: calligra-1309689103-14.1. But the Enduser don't know if its the right thing. Is it possible to make a outputfile like: calligra-2.3.80-git1309689103?

Yes, just define a "versionprefix" parameter in tar_scm service with "2.3.80" for example.

Cool (*happy*). Where i can add this? My tar_scm looks like: http://www.pictureupload.de/originals/pictures/030711184150_Auswahl_0 05.png I think i can't edit more, or? Found out: http://doc.opensuse.org/products/draft/OBS/obs-reference- guide_draft/cha.obs.source_service.html _service is the control file written in XML. So i just have added: <param name="versionprefix">2.3.80</param> And it just works.

Have we a List of possible params of the Services?

The api is providing this (since every service package provides a file defining the parameters with an explenation). The webui is showing these informations when clicking on source service parameter edit button. -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org