| Summary: | Changing graphical front-end for isodumper forces uninstall of the program | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | aguador <waterbearer54> |
| Component: | RPM Packages | Assignee: | David GEIGER <geiger.david68210> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | minor | ||
| Priority: | Normal | CC: | fri, mageiatools, yvesbrungard |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | MGA7TOO | ||
| Source RPM: | isodumper-1.17-2.mga8.src.rpm | CVE: | |
| Status comment: | |||
|
Description
aguador
2020-06-12 09:11:21 CEST
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) =>
MGA7TOO 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) =>
FIXED |