Stanislav Brabec changed bug 1074250
What Removed Added
Flags   needinfo?(dimstar@opensuse.org)

Comment # 17 on bug 1074250 from
Dominique Leuenberger, reply to comment 16:

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

The file conflict exists between the old build of bash-completion that provided
rfkill completion file in the past, and util-linux, which provides it now.

> 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.

So you say that if it is a distro upgrade (or TW), it is OK to move file from
one package to another, and it does not need a special packaging help like:

Conflicts: foo <= last_version_of_foo_that_contains_the_conflicting_file

I was being afraid of a risk that zypper dup or zypper up will complain on a
file conflict instead of seamless update or that it will do something wrong.

If it is smart enough nowadays, I can remove many conflicts in the util-linux
package:

 File conflict of su and kill (up to 12.3 and SLE11).
# It should be coreutils < 8.21-4, but coreutils provide Release-less symbol.
Conflicts:      coreutils < 8.21
# File conflict of sulogin and utmpdump (up to 12.3 and SLE11).
Conflicts:      sysvinit-tools < 2.88+-87
# rfkill conflicts of completion files with <= Leap 42.3 and < SLE15.
Conflicts:      bash-completion <= 2.7-1.3
# The preset is provided by the presets branding package since 0.4
(bsc#1012850) and since 12.2 in SLE (boo#1029775)
Conflicts:      systemd-presets-branding < 12.2

> And I sure hope we won't do such file moves as maintenance
> updates.

We already did it in Leap:

# File conflicts of completion files with <= Leap 42.1 and <= SLE12 SP1 (fixed
by SLE12 Update, boo#977259#c3).
Conflicts:      bash-completion <= 2.1-10

So only in case of file move by the Online Update, we really need such conflict
to ensure that both packages are updated together.


You are receiving this mail because: