Am 15.02.2012 22:33, schrieb Greg Freemyer:

All,

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 specfiles.

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 -11)?

Do I ever need to set the release value in my specfiles to anything but 0?

Thanks Greg IIRC OBS handles the release number itself. When packaging by hand, you can use the release number to indicate patch levels or subsequent changes of packaging without changing version of the packaged software itself.

-- Ralf Lang Linux Consultant / Developer Tel.: +49-170-6381563 Mail: lang@b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537 -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

On Thu, Feb 16, 2012 at 3:00 AM, Adrian Schröter wrote:

Am Mittwoch, 15. Februar 2012, 16:33:46 schrieb Greg Freemyer:

...

All,

...

...

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

...

specfiles.

...

...

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

...

-11)?

...

...

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.

Adrian, 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). Now

sudo zypper ref; zypper se -s nikto

shows 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. Greg -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

On Tue, Feb 21, 2012 at 10:09 AM, Marcus Meissner wrote:

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 wrote:

...

Am Mittwoch, 15. Februar 2012, 16:33:46 schrieb Greg Freemyer:

...

All,

...

...

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

...

specfiles.

...

...

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

...

-11)?

...

...

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.

Adrian,

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).

Now

...

sudo zypper ref; zypper se -s nikto

shows

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.

Ciao, Marcus

So now to "update" to the version in security, I have to do? sudo zypper in --force nikto-2.1.1-2.1 fyi: in this case I'm going to delete the package from my home project. I only branched it to fix the simple bug you accepted, so i definitely want to switch to the security version. Thanks Greg -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

On 02/15/2012 02:17 PM, Ralf Lang wrote:

Am 15.02.2012 22:33, schrieb Greg Freemyer:

...

All,

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 specfiles.

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 -11)?

Do I ever need to set the release value in my specfiles to anything but 0?

Thanks Greg IIRC OBS handles the release number itself. When packaging by hand, you can use the release number to indicate patch levels or subsequent changes of packaging without changing version of the packaged software itself.

Yes, and I generally set Release:0 and forget it in my packages. I've not needed to change this unless working on some branched packages. HTH, Peter -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org