updates-testing: multilib broken for days now
paul at city-fan.org
Thu Jul 9 13:37:58 UTC 2015
On 09/07/15 12:39, Miloslav Trmač wrote:
>> On Wed, 8 Jul 2015 21:30:40 +0200
>> Reindl Harald <h.reindl at thelounge.net> wrote:
>>> Protected multilib versions: polkit-0.113-1.fc21.x86_64 !=
>> This is due to polkit splitting out a polkit-libs package between those
>> two versions. This makes it only include the polkit-libs package
>> instead of a polkit.i686.
>> You should be able to just remove the old polkit.i686, but I agree it
>> needs to be handed by the package cleanly for upgrades.
> Oops. Is there a way to handle this cleanly at all? I can’t just do polkit-libs.i686 Obsoletes: polkit.i686, that would break 32-bit-only systems.
Obsoletes: polkit < 0.112-7
(assuming this is the EVR at which the split was introduced)
On a 32-bit system, both polkit and polkit-libs should be updated to
polkit-0.112-7, whilst on x86_64, polkit-libs-0.112-7.i386 will obsolete
polkit-0.112-1.i386 and the x86_64 versions will upgrade to 0.112-7 as
Nothing arch-specific is necessary for the Obsoletes.
More information about the devel