Comment # 16 on bug 1074250 from Dominique Leuenberger

(In reply to Stanislav Brabec from comment #15)

> # rfkill conflicts of completion files with <= Leap 42.3 and < SLE15.
> Conflicts:      bash-completion <= 2.7-1.3

scine rfkill no longer existst, the conflicts would have more chances to
survive in bash-completion (conflicts: rfkill <= 0.5); the same issue as above:
once rfkill 0.5 would be reintroduced, this conflicts would be in the way (but
again, release of bash-completion is unspecific:

42.1: verison 2.1, so ok
42.2:
42.3:
Leap 15:   2.7-lp150.1.5 (even 1000 checkins later, this will be < 2.7-1.3)
SLE-15:GA: 2.7-1.5 (at this time)

> bash-completion continues to exist and it did not get a version update. Just
> a new build of bash-completion contains one file less, and the old build
> conflicts with the new util-linux.

There is no real universal answer I'm afraid. Moving files between packages
will only work reliably (ever) if both packages are updated 'together' (sort of
what we expect in TW, since we formally only support zypper dup, so all
packages are updated together); from one release of Leap/SLE to the next, the
same is true. And I sure hope we won't do such file moves as maintenance
updates.

> Do we need some packaging-level help in Leap 15 to perform a seamless update
> with a file moved from one package to another? Is it already implemented in
> Leap 12?

In essence we can 'ignore' it for Leap N to Leap N+1, since, as mentioned
above, the only supported upgrade path is zypper dup (or upgrade from the DVD,
which das also a dist-upgrade); the result being that all packages are being
updated together.