On Wed, Feb 27, 2013 at 1:17 PM, Bernhard Voelker
On 02/27/2013 09:56 AM, Andrey Borzenkov wrote:
On Wed, Feb 27, 2013 at 12:41 PM, Bernhard Voelker
wrote: Hi,
are there any guidelines on how to move programs from one package to another - while guaranteeing that the program is installed any time (either by the old or by the new package)?
The case: su and kill are moved from coreutils to util-linux upstreams. It'd be "quite not so optimal" if an installation would be left behind without them ...
As both are always installed on any system anyway, the simplest solution would be to set
Conflicts: other-package < version-before-move
in each RPM. This would force both of them to be updated in single transaction.
Sure, the problem is that I'm not the new package of util-linux including su does not yet exist (and I'm not the maintainer).
Hmm, for local testing, I could manually create such a package. Let's see ...
Unfortunately I'm not really sure that OBS actually provides monotonically increasing NVR given how R part is calculated.
I don't understand because I don't know the abbreviations NVR and R, but I'm sure I'll hit that issue soon. ;-)
NVR == Name-Version-Release. As far as I understand, OBS assigns Release as number of commits since project/package had initially been created. So when you branch package Release starts from the beginning. So it can happen - 12.2 is branched and starts with Release 1 - 12.2 is released with Release == 10 (as example) - you continue development on Factory and at some point branch 12.3 - if Version did not change, it may happen that Release in 12.3 will be lower than Release in 12.2, so above Conflicts will not fire. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org