[opensuse-buildservice] automatic release numbering
Hi, I know this is frequently asked and I pretty much understand how it works but I currently see one issue: The example is the avahi package in project openSUSE:Evergreen:11.1 All spec files in the package have Release: 9.<RELEASE12> But the build logs show: I have the following modifications for avahi.spec: 36c36 < Release: 9.<RELEASE12> ---
Release: 9.6.1
Could somebody please explain or rather tell me how to fix it? The other following issue has been an issue for a long time but I'm not sure I reported it in detail yet. I regularly notice that in devel:tools:scm/mercurial: It gets patch level updates pretty often and currently has (according to the specfile) Version: 1.8.1 Release: 1 as it was updated a few days ago with the new 1.8.1 version. Still OBS internally always increases the "source change" count: I have the following modifications for mercurial.spec: 32c32 < Release: 1 ---
Release: 42.1
It _seems_ to me that it's happening only for branched/linked packages against openSUSE:Factory (or probably any other link target) but still it looks wrong to me. Wolfgang -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Sun, Apr 3, 2011 at 14:02, Wolfgang Rosenauer <wolfgang@rosenauer.org> wrote:
Hi,
I know this is frequently asked and I pretty much understand how it works but I currently see one issue:
The example is the avahi package in project openSUSE:Evergreen:11.1
All spec files in the package have Release: 9.<RELEASE12>
But the build logs show:
I have the following modifications for avahi.spec: 36c36 < Release: 9.<RELEASE12> ---
Release: 9.6.1
Could somebody please explain or rather tell me how to fix it?
The other following issue has been an issue for a long time but I'm not sure I reported it in detail yet.
I regularly notice that in devel:tools:scm/mercurial: It gets patch level updates pretty often and currently has (according to the specfile) Version: 1.8.1 Release: 1 as it was updated a few days ago with the new 1.8.1 version. Still OBS internally always increases the "source change" count:
I have the following modifications for mercurial.spec: 32c32 < Release: 1 ---
Release: 42.1
It _seems_ to me that it's happening only for branched/linked packages against openSUSE:Factory (or probably any other link target) but still it looks wrong to me.
This happens to every package built in the openSUSE Build Service. The build service always replaces the Release with <CI_CNT>.<B_CNT> which expands to (commit count).(build count). You can modify what Release expands out to in the prjconf. (In my prjconf, I use "Release: <CI_CNT>" only.) -- later, Robert Xu -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Hi, Am 03.04.2011 20:28, schrieb Robert Xu:
This happens to every package built in the openSUSE Build Service. The build service always replaces the Release with <CI_CNT>.<B_CNT> which expands to (commit count).(build count). You can modify what Release expands out to in the prjconf.
(In my prjconf, I use "Release: <CI_CNT>" only.)
as I wrote in my initial mail I understand most of the Release counting and one feature of it is to reset to 0 when the Version increases. As written that applies at least to non-linked packages but seems to fail for linked ones. Wolfgang -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Sun, Apr 03, 2011 at 08:02:51PM +0200, Wolfgang Rosenauer wrote:
I know this is frequently asked and I pretty much understand how it works but I currently see one issue:
The example is the avahi package in project openSUSE:Evergreen:11.1
All spec files in the package have Release: 9.<RELEASE12>
But the build logs show:
I have the following modifications for avahi.spec: 36c36 < Release: 9.<RELEASE12> ---
Release: 9.6.1
Could somebody please explain or rather tell me how to fix it?
That's because your avahi package is a link, and the "RELEASE" hint (which actually just is a crude workaround that will be removed some day) does not work for links. (The check in count is reset when the version changes, but links do not have a fixed version.) Cheers, Michael. -- Michael Schroeder mls@suse.de SUSE LINUX Products GmbH, GF Markus Rex, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
participants (3)
-
Michael Schroeder -
Robert Xu -
Wolfgang Rosenauer