Comment # 10 on bug 1074250 from Stanislav Brabec

Regarding the conflict: I added a conflict that contains release part, but
probably did not pick high enough release. rfkill did a new rebuild in time
between, and release 8.6 was not covered by the symbol.

The change done by Antoine Belvire is not correct as well, as makes util-linux
obsoleted by self, which can badly confuse the solver:

That provides symbol rfkill version 0.5.
Provides:       rfkill = 0.5

That obsoletes anything that provides rfkill version <= 0.5, i. e. both rfkill
package and util-linux.
Obsoletes:      rfkill <= 0.5

There is no easy solution. Either return back release-based rfkill obsolescence
(which is unsafe, as different products can use different release numbers), or
set symbol version e. g. to 0.5.0.1 (which is unsafe as well because it will
block possible future re-introduction of a separate rfkill package version
0.5).

I propose to fill a drop request for rfkill in Factory, then revert to release
based conflict, but increment the version to the last rfkill release number
even seen + 1.

Regarding
/usr/lib/systemd/system/rfkill-block@.service
/usr/lib/systemd/system/rfkill-unblock@.service

It makes sense to add them to util-linux.

As integration of rfkill to util-linux was an upstream decision, we should
probably add these services to the upstream as well.