Bug 18633

Summary:	Conflict with between sddm and lightdm in Mga5 to Mga6 upgrade
Product:	Mageia	Reporter:	Charles Edwards <cae>
Component:	RPM Packages	Assignee:	Nicolas Lécureuil <mageia>
Status:	RESOLVED FIXED	QA Contact:
Severity:	critical
Priority:	Normal	CC:	jani.valimaa, marja11, thierry.vignaud
Version:	Cauldron
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	sddm-0.13.0-2.mga6.src.rpm	CVE:
Status comment:

Description Charles Edwards 2016-06-06 15:53:42 CEST

Conflict between sddm and lightdm

Installation failed:
	file /etc/dbus-1/system.d/org.freedesktop.DisplayManager.conf from install of sddm-0.13.0-2.mga6.x86_64 conflicts with file from package lightdm-1.14.4-1.mga5.x86_64


This can prevent successful upgrade of Mga5 to Mga6.

Comment 1 Marja Van Waes 2016-06-07 14:39:14 CEST

Assigning to sddm and neoclust, because wally is less available atm.

CC: (none) => jani.valimaa, marja11
Assignee: bugsquad => mageia
Summary: Conflict with lightdm in Mga5 to Mga6 upgrade => Conflict with between sddm and lightdm in Mga5 to Mga6 upgrade

Comment 2 Jani Välimaa 2016-06-07 21:53:29 CEST

There shouldn't be conflicts as the files are identical. IIRC this is caused by a some change in rpm's checksum handling (or something like that) between mga5 and cauldron. Unfortunately I can't find the commit which is causing this.

Updating both pkgs in same transaction should work, but I think there's no way to ensure that. Maybe this is something for ERRATA.

Comment 3 Charles Edwards 2016-06-07 22:51:05 CEST

They do update properly if it is done in the same transaction but that is not a
guarantee.

It would also work if a conflict is added ssdm
Conflicts:  lightdm > 1.18.1

Adding an ERRATA will not help the people whose 5 to 6 upgrade fails because of a conflict.

In upgrades I have tested using Mga6.iso when the upgrade fails in this manner,
even Mg5 is borked and is no longer bootable.
User is now has no option but a clean install.

Comment 4 Charles Edwards 2016-06-07 22:58:30 CEST

(In reply to Charles Edwards from comment #3)
 
> It would also work if a conflict is added ssdm
> Conflicts:  lightdm > 1.18.1
 
Sorry wrong key
Conflicts:  lightdm < 1.18.1

Comment 5 David Walser 2016-06-13 15:02:03 CEST

Indeed, you can never count on this "rpm doesn't consider a conflict if the file is the same" behavior, because it will never work correctly when upgrading from an older version in which the file is different, unless they are upgraded in the same transaction.  This does need to be fixed, and a conflicts tag is probably the right solution.

Comment 6 Rémi Verschelde 2016-06-22 07:39:03 CEST

I added a conflict, should be fixed in sddm-0.13.0-4.mga6. (Provided sddm from mga5 does not conflict with lighdm from mga6, else a conflict might also be needed in the lightdm package).

Comment 7 Rémi Verschelde 2016-06-22 07:39:29 CEST

Marking as fixed, please reopen if the fix was not enough.

Status: NEW => RESOLVED
Resolution: (none) => FIXED

Comment 8 Thierry Vignaud 2016-06-28 17:38:25 CEST

That's not enough.
As the file is identical in both package in mga5, same in mga6, we must add a conflict in both packages.

Else we get:

Installation failed:
        file /etc/dbus-1/system.d/org.freedesktop.DisplayManager.conf from install of lightdm-1.18.1-1.mga6.x86_64 conflicts with file from package sddm-0.11.0-1.1.mga5.x86_64

CC: (none) => thierry.vignaud

Comment 9 Rémi Verschelde 2016-06-28 17:59:23 CEST

Thanks for implementing the better fix :)