On Thu, Feb 16, 2012 at 3:00 AM, Adrian Schröter <adrian(a)suse.de> wrote:
Am Mittwoch, 15. Februar 2012, 16:33:46 schrieb Greg
I've just been ignoring the release variable
in my specfiles but I
don't really understand the way it works
I suspect its described on the wiki, but I
couldn't find it.
As an example, I maintain sleuthkit. Looking in 3
repos I see:
sleuthkit | 3.2.3-10.1 | x86_64 | security
sleuthkit | 3.2.3-3.5 | x86_64 | factory-oss
sleuthkit | 3.2.3-2.1.3 | x86_64 | openSUSE
As of a few days ago, they all had "release:
0" in their respective
My understanding is that the number following the
dash above is the
release number, I really have 3 releases of 3.2.3
-2, -3, and -10. Is that right?
If I push the code in security to factory, will
it suddenly become -10 (or
Do I ever need to set the release value in my
specfiles to anything but 0?
No, OBS is setting the release number during build to a proper value.
However, it is important that you have a branch (or link) in your package
sources, so OBS can ensure that your development version is always higher
the version in your submit target.
So the below behavior is by design:
I branched nikto out of the security repo to my home via the webui.
I then made a small patch and SR'ed it back to security (and it was
accepted several hours ago).
v | nikto | package | 2.1.1-2.1 | noarch | security
i | nikto | package | 2.1.1-5.1 | noarch | (System Packages)
Intuitively (after the SR is accepted in security) I expect
security:nikto to now have a equal or higher version than my home
version. I think that is why I find this confusing.
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org