[opensuse-packaging] package versioning
Dear all, I have a simple question; Let's imagine we have a package 'foobar'; which the latest stable release is 1.0. Someone decides to to update to git snapshot and uses a version based on the date, for example: 20121017, where the NEVRA goes into something like: Name: foobar Epoch: 0 Version: 20121017 Release: 0 Arch: noarch Now after two years of git snapshotting we get an official release, lets say, 1.1; Would it normal to suppose that version wise: 20121017 > 1.1 Eventually my guess was that we should enforce Epoch to get back into track and make sure 1.1 would replace the former packages; If I understood correctly it is not wise to use Epoch within openSUSE and it should be banned... So... How do we get this update going ? This is just an hipotetical case, though I can remember of few examples currently in production, which don't for this case; I'm mainly interesting in knowing how to deal with this in openSUSE. Thanks. NM -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Mon, 17 Sep 2012 23:36:19 +0100 Nelson Marques <nmo.marques@gmail.com> wrote:
Dear all,
I have a simple question; Let's imagine we have a package 'foobar'; which the latest stable release is 1.0. Someone decides to to update to git snapshot and uses a version based on the date, for example: 20121017, where the NEVRA goes into something like:
Name: foobar Epoch: 0 Version: 20121017 Release: 0 Arch: noarch
Now after two years of git snapshotting we get an official release, lets say, 1.1; Would it normal to suppose that version wise:
20121017 > 1.1
Eventually my guess was that we should enforce Epoch to get back into track and make sure 1.1 would replace the former packages; If I understood correctly it is not wise to use Epoch within openSUSE and it should be banned...
So... How do we get this update going ?
This is just an hipotetical case, though I can remember of few examples currently in production, which don't for this case; I'm mainly interesting in knowing how to deal with this in openSUSE.
Thanks.
NM Hi AFAIK It should be related to the git/svn etc release, for example for gimp-dds I used;
date_rXXX So using export; svn export -r175 http://gimp-dds.googlecode.com/svn/trunk/ gimp-dds So it became latest stable release+svnyyyymmdd_r175 in the version. The version should always prefix in your case something like 1.0+gityyyymmdd_rabcdefg Then 1.1 would be greater, even if it's 0.0 then you would still see it updated.... -- Cheers Malcolm °¿° (Linux Counter #276890) openSUSE 12.2 (x86_64) Kernel 3.4.6-2.10-desktop up 7:31, 6 users, load average: 0.08, 0.11, 0.13 CPU Intel i5 CPU M520@2.40GHz | Intel Arrandale GPU -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
Malcolm, Ideally, I trully agree with you; and with 4.10 you support for tilde also... but... lets assume the harm has been done... Can we fall back to all might Epoch ? :) NM 2012/9/18 Malcolm <malcolm_lewis@bellsouth.net>:
On Mon, 17 Sep 2012 23:36:19 +0100 Nelson Marques <nmo.marques@gmail.com> wrote:
Dear all,
I have a simple question; Let's imagine we have a package 'foobar'; which the latest stable release is 1.0. Someone decides to to update to git snapshot and uses a version based on the date, for example: 20121017, where the NEVRA goes into something like:
Name: foobar Epoch: 0 Version: 20121017 Release: 0 Arch: noarch
Now after two years of git snapshotting we get an official release, lets say, 1.1; Would it normal to suppose that version wise:
20121017 > 1.1
Eventually my guess was that we should enforce Epoch to get back into track and make sure 1.1 would replace the former packages; If I understood correctly it is not wise to use Epoch within openSUSE and it should be banned...
So... How do we get this update going ?
This is just an hipotetical case, though I can remember of few examples currently in production, which don't for this case; I'm mainly interesting in knowing how to deal with this in openSUSE.
Thanks.
NM Hi AFAIK It should be related to the git/svn etc release, for example for gimp-dds I used;
date_rXXX
So using export;
svn export -r175 http://gimp-dds.googlecode.com/svn/trunk/ gimp-dds
So it became latest stable release+svnyyyymmdd_r175 in the version.
The version should always prefix in your case something like 1.0+gityyyymmdd_rabcdefg
Then 1.1 would be greater, even if it's 0.0 then you would still see it updated....
-- Cheers Malcolm °¿° (Linux Counter #276890) openSUSE 12.2 (x86_64) Kernel 3.4.6-2.10-desktop up 7:31, 6 users, load average: 0.08, 0.11, 0.13 CPU Intel i5 CPU M520@2.40GHz | Intel Arrandale GPU
-- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
-- --- Artigo 21 - Direito à Resistência Todos têm o direito de resistir a qualquer ordem que ofensa os seus direitos, liberdades e garantias e de repelir pela força qualquer agressão, quando não seja possível recorrer à autoridade pública. Constituição da Républica Portuguesa -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Tue, 18 Sep 2012 01:08:11 +0100 Nelson Marques <nmo.marques@gmail.com> wrote:
Malcolm,
Ideally, I trully agree with you; and with 4.10 you support for tilde also... but... lets assume the harm has been done... Can we fall back to all might Epoch ? :)
NM
Hi AFAIK It should be related to the git/svn etc release, for example for gimp-dds I used;
date_rXXX
So using export;
svn export -r175 http://gimp-dds.googlecode.com/svn/trunk/ gimp-dds
So it became latest stable release+svnyyyymmdd_r175 in the version.
The version should always prefix in your case something like 1.0+gityyyymmdd_rabcdefg
Then 1.1 would be greater, even if it's 0.0 then you would still see it updated....
-- Cheers Malcolm °¿° (Linux Counter #276890) openSUSE 12.2 (x86_64) Kernel 3.4.6-2.10-desktop up 7:31, 6 users, load average: 0.08, 0.11, 0.13 CPU Intel i5 CPU M520@2.40GHz | Intel Arrandale GPU
-- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
Hi In that case wouldn't you add an obsoletes to the spec file? It's all actually a subject I've been thinking about for an agreed format, svn seems easy, git commits are more confusing ;) Darix was the one who sorted me out on the svn export... -- Cheers Malcolm °¿° (Linux Counter #276890) openSUSE 12.2 (x86_64) Kernel 3.4.6-2.10-desktop up 8:20, 6 users, load average: 0.05, 0.15, 0.15 CPU Intel i5 CPU M520@2.40GHz | Intel Arrandale GPU -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
In that case wouldn't you add an obsoletes to the spec file?
Obsoletes is weird enough and I'm not pretty sure if it's the right thing; Epoch is fun, but once it comes in, it never leaves... That's a nightmare with jpackage stuff...
It's all actually a subject I've been thinking about for an agreed format, svn seems easy, git commits are more confusing ;)
It's a nice thing to set on stone; reviewers should pay special attention for crazy versions. Either way, when the time comes we'll see :)
Darix was the one who sorted me out on the svn export...
svn is fun for dry runs :P -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
Le lundi 17 septembre 2012, à 23:36 +0100, Nelson Marques a écrit :
Eventually my guess was that we should enforce Epoch to get back into track and make sure 1.1 would replace the former packages; If I understood correctly it is not wise to use Epoch within openSUSE and it should be banned...
So... How do we get this update going ?
We don't use epoch in openSUSE, see http://lists.opensuse.org/opensuse-packaging/2009-01/msg00091.html You should just use the real version when updating to the new tarball (and I agree people should not use "bad" versions in the first place). Short summary: libzypp will do the magic. Vincent -- Les gens heureux ne sont pas pressés. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
participants (3)
-
Malcolm
-
Nelson Marques
-
Vincent Untz