I don't think you can do this directly, but for our instance of OBS we do Release: %%{?release_prefix}<CI_CNT>.<B_CNT>%%{?release_suffix} And then define %release_prefix as the release we want to be before the part that the BuildService writes. The Release: line is before the Macros section of the Project prjconf. On Thu, 2009-03-12 at 15:39 +0100, Michal Vyskocil wrote:

Hi,

I'd like to ask how is the Release Tag generated in a BuildService. My current problem with an automatic Release Tag handling is that we don't allow a usage of our rpms and those from jpackage.org, as Fedora does [2].

Is it possible to tell OBS that it should leave a Release Tag in specfile and just append it's output behind it instead of completely rewrite? I understood that this change will not appeared in Factory, because all jpackage RPMs in SUSE now has a larger Release Tag than jpackage.org RPMs, but this still should be applicable on Java:jpackage-5.0 (1.7) projects.

[1] https://fedoraproject.org/wiki/Packaging/JPackagePolicy

Regards Michal Vyskocil -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org