| Summary: | auto-multiple-choice depend on perl-DBD-SQLite | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | marco tux4ever <onlylinux> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | bruno.pincon, marja11, pado |
| Version: | Cauldron | Keywords: | NEEDINFO, Triaged |
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | auto-multiple-choice | CVE: | |
| Status comment: | |||
|
Description
marco tux4ever
2013-12-19 16:10:34 CET
Manuel Hiebel
2013-12-22 20:22:55 CET
Keywords:
(none) =>
Triaged I confirm the 2 mentionned problems with AMC on mageia 4. First the amc package lacks a dependency on perl(DBD::SQLite). Secondly I meet also the problem with perl-Graphics-Magick (Magick.so: undefined symbol) but there is a workaround suggested by Alexis Bienvenüe which works for me. It consists in using perl-Image-Magick instead of perl-Graphics-Magick (so the dependency on perl-Graphics-Magick could be replaced by a dependecy on perl-Image-Magick for the AMC mageia package). hth PS : for those who want to use right now AMC on mageia-4 : urpmi perl-DBD-SQLite urpmi perl-Image-Magick rpm -e --nodeps perl-Graphics-Magick CC:
(none) =>
bruno.pincon
Alexis Bienvenüe
2014-07-11 12:09:09 CEST
CC:
(none) =>
pado Reassigning to BugSquad, because auto-multiple-choice is now maintained by nobody. Is this bug still valid, btw? If so, do you still see it in Mageia 5 or cauldron? Not yet CC'ing auto-multiple-choice committers, that can still be done when we read this bug didn't get fixed, yet Keywords:
(none) =>
NEEDINFO Since we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution. Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information. Closing as OLD. Status:
NEW =>
RESOLVED |