Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Passing version to DEBTRANSFORM-TAR #956

Open
KottV opened this issue Oct 4, 2023 · 3 comments
Open

Passing version to DEBTRANSFORM-TAR #956

KottV opened this issue Oct 4, 2023 · 3 comments

Comments

@KottV
Copy link

KottV commented Oct 4, 2023

Hi,

Is there a way to pass package version to DEBTRANSFORM-TAR tag?
My package have a bunch of source provided by _service with setversion.
So without DEBTRANSFORM it can't pick up a proper source. But with every service run increasing the version I have to set that manually in .dsc.

@ighvh
Copy link

ighvh commented Dec 15, 2023

I have a similar issue. Using obs_scm with set_version and debtransform only works if you have debian.tar.gz and the source tarball provided by _service.

Currently I'm packaging a library for both Qt5 and Qt6, but both packages should share a common header package. So I used the same approach as kernel-source, e.g. I have one Package with two spec files. The second package has just a link to the first one with cicount="copy".

For debian, I have two .dsc files (one named after each package) and two archives with the remaining debian files. Choosing these archives is easy, DEBTRANSFORM-FILES-TAR. But debtransform fails to find the source archive:

Too many files looking like a usable source tarball (would not know which to pick): QtPdCom1.debian.tar.gz QtPdCom1-1.3.0.14.g03aa11b.tar.bz2

Maybe extend debtransform that DEBTRANSFORM-TAR could also be a regex or wildcard?

@ighvh
Copy link

ighvh commented Dec 15, 2023

related: openSUSE/obs-service-set_version#29

@gleichdick
Copy link

With openSUSE/obs-service-set_version#88 it works for me well. My .dsc file contains

DEBTRANSFORM-TAR: QtPdCom1-@[email protected]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants