On 8/14/19 8:31 PM, Frédéric LOUI wrote:
Hi (again :-) )
After analysing the log in my manually uploaded dsc file I have my printing file name set to « pi_0.8.orig.tar.gz » In the log file the tarball generated has the name pi-0.8.orig.1553891655.af0b089.tar.gz
A simple solution would be to generate a tarball that has a file name that map the one in the dsc file.
I managed to use « filename » and « versionprefix » but I do I prevent abs-service-tar_scm to generate a file name that uses « <filename>-<versionprefix>.<commit_timestamp>.tar, with <commit_timestamp> » Behaviour as documented here ? : -> https://en.opensuse.org/openSUSE:Build_Service_Concept_SourceService#Example...
Merci !
À bientôt, -- Frederic
As far as I known, you can decide in the _service file to use any file name for the generated tarball. You can have a look here what placeholders are supported (found via 'rpm -ql obs-service-obs_scm'): /usr/lib/obs/service/obs_scm.service I'm not at all an expert in this, but my wild guess is that you have to use versionformat instead of versionprefix. E.g. in [1] I'm following upstream GNU hello, and first build the distribution tarball via './bootstrap && ./configure && make dist' as one would in an upstream git-clone (for details see the spec file), and then do the actual build from that just-created distribution tarball (again via './configure && make'). I only had to work around 'bootstrap' being unable to download the PO files in OBS environment, so this has also done by the _service (see SOURCE* in spec). [1] <https://build.opensuse.org/package/view_file/home:berny:branches:fromgit/hello/_service?expand=1> Have a nice day, Berny -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org