converting obscpio -> tar

Axel Braun

12 Jan 2021 12 Jan '21

15:37

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) Thanks Axel

Show replies by date

Malcolm

12 Jan 12 Jan

15:43

On Tue 12 Jan 2021 04:37:11 PM CST, 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 :-)

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

Hi Axel Have a look at what I use for cherrytree.... https://build.opensuse.org/package/view_file/GNOME:Apps/cherrytree/_service?... -- Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890) Tumbleweed 20210110 | GNOME Shell 3.38.2 | 5.10.5-1-default Intel DQ77MK MB | Xeon E3-1245 V2 X8 @ 3.40 GHz | Intel/Nvidia up 19:50, 2 users, load average: 1.25, 1.20, 0.71

Adrian Schröter

15:44

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

Axel Braun

16:14

Hello Adrian, Am Dienstag, 12. Januar 2021, 16:44:35 CET schrieb Adrian Schröter:

...

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

...

...
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.

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

...

Btw, just try

osc add $GIT_URL

and it writes a _service file with all the needed steps (4 in total)

No...just 2 services were added: download_url verify_file Cheers Axel

Adrian Schröter

13 Jan 13 Jan

07:42

On Dienstag, 12. Januar 2021, 17:14:31 CET Axel Braun wrote:

...

Hello Adrian,

Am Dienstag, 12. Januar 2021, 16:44:35 CET schrieb Adrian Schröter:

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

...
...
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.

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. -- 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

Axel Braun

11:15

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

Hans-Peter Jansen

12 Jan 12 Jan

16:18

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

Stefan Brüns

13 Jan 13 Jan

06:13

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, 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

No reason to switch away from obs_scm, just use $> osc service runall or $> osc service runall tar ; osc service runall recompress Kind regards, Stefan -- Stefan Brüns / Bergstraße 21 / 52062 Aachen phone: +49 241 53809034 mobile: +49 151 50412019

Adrian Schröter

07:28

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

Jan Engelhardt

09:05

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?

Stephan Kulow

09:31

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 Greetings, Stephan -- Lighten up, just enjoy life, smile more, laugh more, and don't get so worked up about things. Kenneth Branagh

Jan Engelhardt

09:46

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.

Brown, Nicholas

09:49

...

On 13 Jan 2021, at 09:31, Stephan Kulow wrote:

Am 13.01.21 um 10:05 schrieb Jan Engelhardt:

...
...
...
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

On Wednesday 2021-01-13 08:28, Adrian Schröter wrote: that would make this impossible? tar is not the problem, tar.xz is

I believe this is also one of the reasons that obs_scm does not support debian gbp by default. There was some discussion about attempting to get the gbp support working around .cpio files here: https://github.com/openSUSE/obs-service-tar_scm/pull/179#issuecomment-579772... As it would be great to have support for debian gbp packages on the main OBS service. Cheers, Nick

...

Greetings, Stephan

-- Lighten up, just enjoy life, smile more, laugh more, and don't get so worked up about things. Kenneth Branagh

1198

Age (days ago)

1199

Last active (days ago)

List overview

Download

12 comments

8 participants

participants (8)

Adrian Schröter
Axel Braun
Brown, Nicholas
Hans-Peter Jansen
Jan Engelhardt
Malcolm
Stefan Brüns
Stephan Kulow

converting obscpio -> tar

tags

participants (8)