On Dienstag, 12. Januar 2021, 16:37:11 CET Axel Braun wrote:

Hi,

as a prerequsite to the nightly build, I'm struggeling with the source service. I guess its a no-brainer for somebody who worked already with it... I have pulled the latest commit using obs_scm:

<service name="obs_scm"> <param name="url">https://mygitpage.com/myproject.git</param> <param name="scm">git</param> <param name="versionformat">VERSIONgit.%ci~%h</param> </service>

and end up with .obscpio file in my build repo. How can I conver this to a .tar file? I tried recompress-service, but that gives me a .obscpio.gz :-)

<service name="tar" mode="buildtime"> creates it during build. Btw, just try osc add $GIT_URL and it writes a _service file with all the needed steps (4 in total)

I have searched the wiki https://en.opensuse.org/ openSUSE:Build_Service_Concept_SourceService#All_OBS_services_available and OBS manuals, and I feel it needs some love: - obs_scm is not mentioned at all in the above list - the documentation mostly points to the github page - and the github page is not very helpful either (unless 'The code is the documentation' is considered as approach) Example: https://en.opensuse.org/ openSUSE:Build_Service_Concept_SourceService#recompress

https://en.opensuse.org/Category:Build_Service gives some insights as well, but misses proper documentation

Just seen: osc api /service (will look further into that)

Thanks Axel

-- Adrian Schroeter Build Infrastructure Project Manager SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany (HRB 247165, AG München), Geschäftsführer: Felix Imendörffer

Am Dienstag, 12. Januar 2021, 16:37:11 CET schrieb Axel Braun:

Hi,

as a prerequsite to the nightly build, I'm struggeling with the source service. I guess its a no-brainer for somebody who worked already with it... I have pulled the latest commit using obs_scm:

<service name="obs_scm"> <param name="url">https://mygitpage.com/myproject.git</param> <param name="scm">git</param> <param name="versionformat">VERSIONgit.%ci~%h</param> </service>

and end up with .obscpio file in my build repo. How can I conver this to a .tar file? I tried recompress-service, but that gives me a .obscpio.gz :-)

I have searched the wiki https://en.opensuse.org/ openSUSE:Build_Service_Concept_SourceService#All_OBS_services_available and OBS manuals, and I feel it needs some love: - obs_scm is not mentioned at all in the above list - the documentation mostly points to the github page - and the github page is not very helpful either (unless 'The code is the documentation' is considered as approach) Example: https://en.opensuse.org/ openSUSE:Build_Service_Concept_SourceService#recompress

https://en.opensuse.org/Category:Build_Service gives some insights as well, but misses proper documentation

Just seen: osc api /service (will look further into that)

Hi Axel, you might want to switch to tar_scm service. obs_scm isn't always an improvement. Of course, you can expand an cpio file manually: cpio -iduvm < _service:obs_scm:package.obscpio Cheers, Pete

On Dienstag, 12. Januar 2021, 17:18:22 CET Hans-Peter Jansen wrote:

Am Dienstag, 12. Januar 2021, 16:37:11 CET schrieb Axel Braun:

...

Hi,

as a prerequsite to the nightly build, I'm struggeling with the source service. I guess its a no-brainer for somebody who worked already with it... I have pulled the latest commit using obs_scm:

<service name="obs_scm"> <param name="url">https://mygitpage.com/myproject.git</param> <param name="scm">git</param> <param name="versionformat">VERSIONgit.%ci~%h</param> </service>

and end up with .obscpio file in my build repo. How can I conver this to a .tar file? I tried recompress-service, but that gives me a .obscpio.gz :-)

I have searched the wiki https://en.opensuse.org/ openSUSE:Build_Service_Concept_SourceService#All_OBS_services_available and OBS manuals, and I feel it needs some love: - obs_scm is not mentioned at all in the above list - the documentation mostly points to the github page - and the github page is not very helpful either (unless 'The code is the documentation' is considered as approach) Example: https://en.opensuse.org/ openSUSE:Build_Service_Concept_SourceService#recompress

https://en.opensuse.org/Category:Build_Service gives some insights as well, but misses proper documentation

Just seen: osc api /service (will look further into that)

Hi Axel,

you might want to switch to tar_scm service. obs_scm isn't always an improvement.

keep in mind that tar_scm may go away for server side execution.. (we can not store tar balls incremental only as entire file) -- Adrian Schroeter Build Infrastructure Project Manager SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany (HRB 247165, AG München), Geschäftsführer: Felix Imendörffer

On Wednesday 2021-01-13 08:28, Adrian Schröter wrote:

...

Hi Axel,

you might want to switch to tar_scm service. obs_scm isn't always an improvement.

keep in mind that tar_scm may go away for server side execution..

(we can not store tar balls incremental only as entire file)

But why? What is so fundamentally different between tar and cpio that would make this impossible?

On Wednesday 2021-01-13 10:31, Stephan Kulow wrote:

Am 13.01.21 um 10:05 schrieb Jan Engelhardt:

...

On Wednesday 2021-01-13 08:28, Adrian Schröter wrote:

...

...

Hi Axel,

you might want to switch to tar_scm service. obs_scm isn't always an improvement.

keep in mind that tar_scm may go away for server side execution..

(we can not store tar balls incremental only as entire file)

But why? What is so fundamentally different between tar and cpio that would make this impossible?

tar is not the problem, tar.xz is

Well in that case, let's use tar? Because that is the more established format (with regard to, for example, quilt) than cpio.

Am Mittwoch, 13. Januar 2021, 08:42:48 CET schrieb Adrian Schröter:

...

Thats what I took from Malcolms post as well, but - still obscpio: https://build.opensuse.org/package/show/Application:ERP:GNUHealth:3.6/ mygnuhealth

you get a tar ball there, just the spec file gets not the right version.

This is caused by using an rpm macro inside of the Version: line. The set_version service can not deal with that.

Given that you define the version anyway inside the _service file it is IMHO also relative pointless to do so. Just simplify that line and it should work.

Thanks for the final hint, Adrian! Build is running, now back to the nightly build..... Best, Axel