[opensuse-packaging] Versioning issues
I'm trying to clean up and update the tidy packge, for whatever reason it has the version number 1.0 in openSUSE although tidy uses 0.99.0 internally (it has a VERSION macro set to this and its SONAME is libtidy-0.99.so.0). So the correct version number should be 0.99.0.20100204cvs which is however smaller than 1.0. For the libtidy subpackage this would probably not be a problem since it could be renamed to libtidy0 in order to conform to the packaging policy and quieten rpmlint but that does not solve it for the tidy package. Since using epoch is not allowed, what would be an appropriate solution for this? -- Guido Berhoerster -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On Thu, 4 Feb 2010, Guido Berhoerster wrote:
I'm trying to clean up and update the tidy packge, for whatever reason it has the version number 1.0 in openSUSE although tidy uses 0.99.0 internally (it has a VERSION macro set to this and its SONAME is libtidy-0.99.so.0). So the correct version number should be 0.99.0.20100204cvs which is however smaller than 1.0. For the libtidy subpackage this would probably not be a problem since it could be renamed to libtidy0 in order to conform to the
libtidy-0_99-0 actually (the rpmlint report tells you that).
packaging policy and quieten rpmlint but that does not solve it for the tidy package. Since using epoch is not allowed, what would be an appropriate solution for this?
You can simply keep the version number at 1.0.
Richard.
--
Richard Guenther
* Richard Guenther
libtidy-0_99-0 actually (the rpmlint report tells you that).
packaging policy and quieten rpmlint but that does not solve it for the tidy package. Since using epoch is not allowed, what would be an appropriate solution for this?
You can simply keep the version number at 1.0.
So should I just leave it at libtidy and set version to 1.0.20100204cvs? -- Guido Berhoerster -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On Thu, 4 Feb 2010, Guido Berhoerster wrote:
* Richard Guenther
[2010-02-04 11:55]: libtidy-0_99-0 actually (the rpmlint report tells you that).
packaging policy and quieten rpmlint but that does not solve it for the tidy package. Since using epoch is not allowed, what would be an appropriate solution for this?
You can simply keep the version number at 1.0.
So should I just leave it at libtidy and set version to 1.0.20100204cvs?
no, make it libtidy-0_99-0 and set version to 1.0.
Or make it libtidy-0_99-0 and set version to 0.99.20100204cvs,
Provide and Obsolete libtidy <= 1.0.
Richard.
--
Richard Guenther
* Richard Guenther
Or make it libtidy-0_99-0 and set version to 0.99.20100204cvs, Provide and Obsolete libtidy <= 1.0.
That's what seems to be the correct thing to do that but that leads back to my initital question, since libtidy-0_99-0 is a subpackage of tidy using 0.99.20100204cvs would lead to upgrade problems for tidy since it is currently at 1.0. So if I can't use epoch the only option would be staying with 1.0 (which is of course completely arbitrary and misleading) or make it 1.0.20100204cvs to at least give a hint on what it contains. The Tidy project lacks any release management. -- Guido Berhoerster -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
participants (2)
-
Guido Berhoerster
-
Richard Guenther