OK, I feel somewhat badly as this is seems a corner case more than anything, however . . . In testing the authentication window size for isodumper I changed from the gtk to the qt front end with drakrpm. To reproduce: 1. Mark isodumper-gtk to be uninstalled 2. Mark isodumper-qt to be installed Expected behaviour: the two actions are completed Actual behaviour: 1. isodumper and isodumper-gtk are both removed 2. Installation of isodumper-qt fails (logically) due to unfulfilled dependency of isodumper Workaround: reinstall isodumper and install isodumer-qt OK this behaviour might seem logical. However, due to a problem with pango I changed the front-end of doublecmd from gtk2 to qt4 and the installation of doublecmd-common was not affected, so it would seem to be possible to change graphical interfaces without removing and reinstalling the core program on which they depend.
I can see that uninstalling isodumper-gtk would take isodumper with it; otherwise it would be an orphan. But the subsequent installation of isodumper-qt should pull in isodumper. For the workaround, just installing isodumper-qt would work. Assigning to DavidG for isodumper.
Assignee: bugsquad => geiger.david68210
For this bug I now tried the other way around, and confirm weirdness: 1) I have isodumper and isodumper-qt installed. 2) In drakrpm I first select isodumper-gtk - Result: Dialogue autoselects lib64yui9-gtk and lib64yui9-mga-gtk, I accept. 3) I deselect isodumper-qt - Result; Dialogue say it must remove isodumper !! Packaging bug or bug in urpmi logic? Using 1.24-1.mga7 in updates testing
Whiteboard: (none) => MGA7TOOCC: (none) => fri, mageiatools, yves.brungard_mageia
I don't know if it is URPMI or a packaging issue. In the case of Double Commander there are three packages: doublecmd-common doublecmd-gtk doublecmd-qt I can, and have, changed back and forth between the graphical front ends without URPMI uninstalling doublecmd-common.
So ok I changed the required isodumper-gui from Requires to Recommends thus prevent to uninstall the main isodumper package.
Solved the problem, but should the Qt and Gtk front ends not conflict? With the Gtk interface installed, both urpmi and drakrpm allowed me to install the Qt front end and its dependencies. No harm done, but weird. Doublecmd I think allowed only one interface, perhaps because they simply could not co-exist. I was going to test, but it is no longer available. As the reported issues is solved, I will close this.
Resolution: (none) => FIXEDStatus: NEW => RESOLVED