| Summary: | Post upgrade from mga3 running sudo urpmi --auto-update fails with conflicts | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Dylan Myers <ralgith> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | dmorganec, marja11, olivier |
| Version: | 4 | Keywords: | NEEDINFO |
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
|
Description
Dylan Myers
2014-02-04 04:45:16 CET
Curiously re-running the auto-update let it install all the maven and fontconfig stuff that failed the first time. (In reply to Dylan Myers from comment #1) The upgrade instructions do include the recommendation to run the upgrade command twice: https://wiki.mageia.org/en/Mageia_4_Release_Notes#Upgrading_online.2C_using_urpmi_.28CLI.29 If everything is now upgraded, you should probably close this bug report as invalid.
Manuel Hiebel
2014-02-04 18:42:18 CET
CC:
(none) =>
dmorganec Is this bug still valid? Keywords:
(none) =>
NEEDINFO Since there are insufficient details provided in this report for us to investigate the issue further, and 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 |