[opensuse-packaging] RPM version ordering
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hi all, i have a problem with one of my packages, python-openssl: the previous version was called 0.7a and the current one is 0.7. However, in rpm's (and zypp's) view 0.7a > 0.7 and the package will break distribution upgrade because it won't let itself be "downgraded". How can i work around this? Is it possible to e.g. specify that the newer one Obsoletes: %{name} = 0.7a and be done with it? thanks for help m. - -- (if you have any comments, please CC me in the reply, otherwise my replies will break threads. that is a bug in my way of using the mailinglist, which is not yet fixed) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAkjuL9kACgkQjBrWA+AvBr8WXwCgie6RWXcffcUid45l3vaiDnrk G7EAoKWKsK5eF3xjkAaGGcryImOrz/Fo =0Pqb -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Jan Matejek wrote:
i have a problem with one of my packages, python-openssl: the previous version was called 0.7a and the current one is 0.7.
Bad versioning policy from upstream.
However, in rpm's (and zypp's) view 0.7a > 0.7 and the package will break distribution upgrade because it won't let itself be "downgraded".
You just can't package such pre releases with their official 'version'. Call them 0.6_0.7a or similar instead. cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.de/ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On Oct 13, 08 16:00:33 +0200, Ludwig Nussel wrote:
Jan Matejek wrote:
i have a problem with one of my packages, python-openssl: the previous version was called 0.7a and the current one is 0.7.
Bad versioning policy from upstream.
However, in rpm's (and zypp's) view 0.7a > 0.7 and the package will break distribution upgrade because it won't let itself be "downgraded".
You just can't package such pre releases with their official 'version'. Call them 0.6_0.7a or similar instead.
... which would have helped at an earlier stage, ... As a workaround, you could name the current version '0.7final' or perhaps '0.7.0' already works. cheers, Jw. -- o \ Juergen Weigert paint it green! __/ _=======.=======_ <V> | jw@suse.de (not a debating __/ _---|____________\/ \ | 0911 74053-508 excercise.) __/ (____/ /\ (/) | _____________________________/ _/ \_ vim:set sw=2 wm=8 SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Jan Matejek wrote:
i have a problem with one of my packages, python-openssl: the previous version was called 0.7a and the current one is 0.7.
However, in rpm's (and zypp's) view 0.7a > 0.7 and the package will break distribution upgrade because it won't let itself be "downgraded".
Why do you think so? The dist upgrade algorithm happily downgrades packages. 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-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jan Matejek wrote:
i have a problem with one of my packages, python-openssl: the previous version was called 0.7a and the current one is 0.7. However, in rpm's (and zypp's) view 0.7a > 0.7 and the package will break distribution upgrade because it won't let itself be "downgraded".
How can i work around this? Is it possible to e.g. specify that the newer one Obsoletes: %{name} = 0.7a and be done with it?
$ rpmvercmp 0.7a 0.7+final
:0.7+final-0 is newer
cheers
- --
-o) Pascal Bleser http://linux01.gwdg.de/~pbleser/
/\\
On Tue, Oct 14, 2008 at 08:19:15AM +0200, Pascal Bleser wrote:
i have a problem with one of my packages, python-openssl: the previous version was called 0.7a and the current one is 0.7. However, in rpm's (and zypp's) view 0.7a > 0.7 and the package will break distribution upgrade because it won't let itself be "downgraded".
How can i work around this? Is it possible to e.g. specify that the newer one Obsoletes: %{name} = 0.7a and be done with it?
$ rpmvercmp 0.7a 0.7+final :0.7+final-0 is newer
Just to clarify: rpm splits on all non-alphanumeric characters and compares the substrings. Thus "final" is compared against "a", (But as said before: dist-upgrade has no problems with downgrading. Just be sure that there's no repository still enabled with the old 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-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Michael Schroeder napsal(a):
Jan Matejek wrote:
i have a problem with one of my packages, python-openssl: the previous version was called 0.7a and the current one is 0.7.
However, in rpm's (and zypp's) view 0.7a > 0.7 and the package will break distribution upgrade because it won't let itself be "downgraded".
Why do you think so? The dist upgrade algorithm happily downgrades packages.
well, i didn't try it myself, but this bugreport claims otherwise: https://bugzilla.novell.com/show_bug.cgi?id=432544
Cheers, Michael.
-- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On Tue, Oct 14, 2008 at 12:44:32PM +0200, jan mat??jek wrote:
Michael Schroeder napsal(a):
Jan Matejek wrote:
i have a problem with one of my packages, python-openssl: the previous version was called 0.7a and the current one is 0.7.
However, in rpm's (and zypp's) view 0.7a > 0.7 and the package will break distribution upgrade because it won't let itself be "downgraded".
Why do you think so? The dist upgrade algorithm happily downgrades packages.
well, i didn't try it myself, but this bugreport claims otherwise: https://bugzilla.novell.com/show_bug.cgi?id=432544
That just says that the bug reporter also doesn't know about the dist upgrade algortihm. M. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On Tuesday 14 October 2008, Michael Schroeder wrote:
(But as said before: dist-upgrade has no problems with downgrading. Just be sure that there's no repository still enabled with the old version.)
As long as we make clear that this is the policy, I'm fine with that. so far I didn't know that this is an invalid (unspported) setup. with the shared library policy in place more users will have older distributions as addon repository in their sources list, therefore I think my bugreport is valid. it is the most sensible solution imho. in that situation, the current distribution upgrade algorithmn will pick the 11.0 package even though it is from an older code stream, which is why I filed the bugreport. I read somewhere that Provides: python-openssl > 0.7a would help with the version downgrade. Feel free to close it if we declare this setup as "broken". Greetings, Dirk -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
participants (7)
-
Dirk Müller -
Jan Matejek -
jan matějek -
Juergen Weigert -
Ludwig Nussel -
Michael Schroeder -
Pascal Bleser