| Summary: | Failure to add Core Release after upgrade from 4.1 | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Len Lawrence <tarazed25> |
| Component: | Release (media or process) | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED WORKSFORME | QA Contact: | |
| Severity: | major | ||
| Priority: | Normal | CC: | sysadmin-bugs |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
|
Description
Len Lawrence
2015-05-11 22:42:18 CEST
Maybe not a release blocker. "urpmi cheese" complained about not being able to access Core Release (distrib1), medium ignored, then went on to install cheese and dependencies from Core Release (distrib46). ??? On another machine, a full upgrade from 4.1 did not show this problem. Left the choice to $MIRRORLIST and all was well. So, bug invalid. It can happen indeed that Core Release is somewhat broken on Cauldron mirrors, especially when a new kernel is being synced or stuff like that. It should not affect the stable Mageia 5 once the mirrors are frozen. Status:
NEW =>
RESOLVED |