How to use _service file to remove .obscpio and leave only .tar.gz ?

Hello,

I am using _service file to download brunsli locally on my PC.
With the content below, I have the files as follow.

brunsli-0.1.tar.xz
brunsli-0.1.obscpio
brunsli.obsinfo

Those having 2 archive allow to be submit to factory?
Can I remove .obscpio and leave only .tar.xz?

Thank you.

Code:

---

<services>
  <service name="obs_scm" mode="localonly">
    <param name="url">https://github.com/google/brunsli.git</param>
    <param name="scm">git</param>
    <param name="submodules">enable</param>
    <param name="revision">v0.1</param>
    <param name="versionformat">0.1</param>
  </service>
  <service name="tar" mode="localonly" />
  <service name="recompress" mode="localonly">
    <param name="file">*.tar</param>
    <param name="compression">xz</param>
  </service>
  <service name="set_version" mode="buildtime" />
</services>

---

Hi
You should only have the obsXXXX files, no tarball...

If you look at the log for the build you see it create the tarball during the build to use, that's the whole point... ;)

For example, here's the vkmark package in factory;
https://build.opensuse.org/package/s...Factory/vkmark

Quote:

---

Originally Posted by malcolmlewis

Hi
You should only have the obsXXXX files, no tarball...

If you look at the log for the build you see it create the tarball during the build to use, that's the whole point... ;)

For example, here's the vkmark package in factory;
https://build.opensuse.org/package/s...Factory/vkmark

---

Thanks for reply.
Is it ok to use _service for package version that is not master? Can it be use for a package version point release?

Quote:

---

Originally Posted by andythe_great

Thanks for reply.
Is it ok to use _service for package version that is not master? Can it be use for a package version point release?

---

Hi
AFAIK, yes (eg develop etc) but might as well just use the version and tarball as provided...?

In my examples I have this one....

Code:

---

services>
  <service name="obs_scm">
    <param name="url">https://github.com/strukturag/libheif.git</param>
    <param name="scm">git</param>
    <param name="versionrewrite-pattern">v(.*)</param>
    <param name="versionformat">@PARENT_TAG@+@TAG_OFFSET@</param>
    <param name="changesgenerate">enable</param>
    <param name="changesauthor">email@example.com</param>
  </service>
  <service mode="buildtime" name="tar" />
  <service mode="buildtime" name="recompress">
    <param name="file">*.tar</param>
    <param name="compression">xz</param>
  </service>
  <service mode="buildtime" name="set_version" />
</services>

---

Quote:

---

Originally Posted by malcolmlewis

Hi
AFAIK, yes (eg develop etc) but might as well just use the version and tarball as provided...?

In my examples I have this one....

Code:

---

services>
  <service name="obs_scm">
    <param name="url">https://github.com/strukturag/libheif.git</param>
    <param name="scm">git</param>
    <param name="versionrewrite-pattern">v(.*)</param>
    <param name="versionformat">@PARENT_TAG@+@TAG_OFFSET@</param>
    <param name="changesgenerate">enable</param>
    <param name="changesauthor">email@example.com</param>
  </service>
  <service mode="buildtime" name="tar" />
  <service mode="buildtime" name="recompress">
    <param name="file">*.tar</param>
    <param name="compression">xz</param>
  </service>
  <service mode="buildtime" name="set_version" />
</services>

---

---

Got it, thanks.