On Tue, Feb 21, 2012 at 09:55:58AM -0500, Greg Freemyer wrote:
On Thu, Feb 16, 2012 at 3:00 AM, Adrian Schröter email@example.com wrote:
Am Mittwoch, 15. Februar 2012, 16:33:46 schrieb Greg Freemyer:
I've just been ignoring the release variable in my specfiles but I
don't really understand the way it works out.
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 Current OSS
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 represented above.
-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 then
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).
sudo zypper ref; zypper se -s nikto
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.
No, security:nikto is the base of the version counting, as your homedirectory linked to it. So your homeproject will always have the higher version.