| Summary: | missing dependency in drakxtools can lead to not working tools | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Pablo Saratxaga <pablo> |
| Component: | RPM Packages | Assignee: | Thierry Vignaud <thierry.vignaud> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | minor | ||
| Priority: | Low | CC: | pablo, tac |
| Version: | 3 | Keywords: | Triaged |
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | drakxtools | CVE: | |
| Status comment: | |||
|
Description
Pablo Saratxaga
2013-06-04 12:08:14 CEST
related bug: https://bugs.mageia.org/show_bug.cgi?id=6362 (it was wrongly diagnostiqued; what is there described is not the hostname problem, but the same as I describe here)
Pablo Saratxaga
2013-06-04 12:16:17 CEST
CC:
(none) =>
pablo
Manuel Hiebel
2013-06-08 16:46:24 CEST
Keywords:
(none) =>
Triaged There's not much we can do here. If not all packages are updated to work with new perl, then... Priority:
Normal =>
Low so the problem is perl dependency? the problem here is that rpmdrake itself is functional, but doesn't load because wrong detection of X11. rpmdrake is, among all tools, a bit special, as it is what allow users to save their system by updating packages. If rpmdrake fails, an advanced user will be able to run urpmi on cli; but a non-advanced user will be completly lost, and have a bad experience on the distro. Could rpmdrake, alone, be modified to just check existence of $DISPLAY variable instead of using xf86main::main::Xtest ? Maybe also xf86main::main::Xtest, when it fails but $DISPLAY exists, could show a small text telling that maybe perl and/or drakx tools are out of date and should be updated. That will save some people. Mageia 3 changed to end-of-life (EOL) status 4 months ago. http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- The Mageia Bugsquad Status:
NEW =>
RESOLVED |