| Summary: | Wrong Orphans with mumble | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Adrien D <email> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED WORKSFORME | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | stormi-mageia |
| Version: | 2 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
|
Description
Adrien D
2012-12-19 22:42:22 CET
Adrien D
2012-12-19 22:42:36 CET
Whiteboard:
(none) =>
MCC how have you installed mumble ? Whiteboard:
MCC =>
(none) By MCC, I clicked on mumble ans mumble11x (I installed both) I tested both rpmdrake and urpmi and found no bug. If you install mumble-11x via "urpmi mumble-11x" or rpmdrake (clicking only mumble-11x, which automatically selects mumble as a dependency), and then remove mumble-11x, then mumble is considered orphan. This is expected behaviour. If you install specifying mumble explicitly, such as "urpmi mumble mumble-11x" or click on mumble and then mumble-11x in rpmdrake, then urpmi --auto-orphans doesn't try to remove mumble. Status:
NEW =>
RESOLVED |