[opensuse-packaging] Changed versioning scheme
Hi, I deal with a package which has a changed versioning scheme. Upstream now has 2.6, while the currently packaged version is 3026 (probably at a time where now version was available from upstream?). As epoch is not used in openSUSE and is ignored. How could I deal with this situation? Looking in the wiki, there is: https://en.opensuse.org/openSUSE:Package_naming_guidelines But I'm not sure which separator I should use. '_', '+', and '.' are explicitly not forbidden. But nothing is explicitly allowed. Is there any recommendation or guideline? My case: I want to update vimplugin-gnupg to the current upstream version: https://build.opensuse.org/package/show/editors/vim-plugins https://github.com/jamessan/vim-gnupg Sebastian -- python programming - mail server - photo - video - https://sebix.at cryptographic key at https://sebix.at/DC9B463B.asc and on public keyservers
22.06.2016 22:36, Sebastian пишет:
Hi,
I deal with a package which has a changed versioning scheme. Upstream now has 2.6, while the currently packaged version is 3026 (probably at a time where now version was available from upstream?). As epoch is not used in openSUSE and is ignored. How could I deal with this situation?
As far as I understand openSUSE relies on "zypper dup" to enforce currently available version. So you probably do not need to do anything special. Although lack of epoch support sounds like a bug or at least misfeature.
Looking in the wiki, there is: https://en.opensuse.org/openSUSE:Package_naming_guidelines But I'm not sure which separator I should use. '_', '+', and '.' are explicitly not forbidden. But nothing is explicitly allowed.
Is there any recommendation or guideline?
My case: I want to update vimplugin-gnupg to the current upstream version: https://build.opensuse.org/package/show/editors/vim-plugins https://github.com/jamessan/vim-gnupg
Sebastian
On 22/06/2016 21:36, Sebastian wrote:
Hi,
I deal with a package which has a changed versioning scheme. Upstream now has 2.6, while the currently packaged version is 3026 (probably at a time where now version was available from upstream?). As epoch is not used in openSUSE and is ignored. How could I deal with this situation?
Looking in the wiki, there is: https://en.opensuse.org/openSUSE:Package_naming_guidelines But I'm not sure which separator I should use. '_', '+', and '.' are explicitly not forbidden. But nothing is explicitly allowed.
Is there any recommendation or guideline?
My case: I want to update vimplugin-gnupg to the current upstream version: https://build.opensuse.org/package/show/editors/vim-plugins https://github.com/jamessan/vim-gnupg
Sebastian
I think, without actually trying, you have to provide and obsolete the old version in the sub package, ie provide > 3026 and obsolete 3026 and hope that they never bring out a 3027. Not sure if this will work without actually renaming the sub package with a 2 suffix. Hope this helps, Dave P -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
participants (3)
-
Andrei Borzenkov
-
Dave Plater
-
Sebastian