Bug 15911 - Failure to add Core Release after upgrade from 4.1
Summary: Failure to add Core Release after upgrade from 4.1
Status: RESOLVED WORKSFORME
Alias: None
Product: Mageia
Classification: Unclassified
Component: Release (media or process) (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal major
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-05-11 22:42 CEST by Len Lawrence
Modified: 2015-05-12 09:16 CEST (History)
1 user (show)

See Also:
Source RPM:
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Len Lawrence 2015-05-11 22:42:18 CEST 
Description of problem:
Starting with classic DVD install of KDE Mageia 4.1+updates tried upgrade to KDE using classic DVD iso for Cauldron.  No major problems until I tried to add update media.  The usual ones came up but not Core Release 32&64bit. It produced the aria2 failure message.  Ran through the loop four times, selecting a different mirror each time, 3 x http, 1 x ftp - same error every time.

Version-Release number of selected component (if applicable):
5 final

How reproducible:


Steps to Reproduce:
1.
2.
3.


Reproducible: 

Steps to Reproduce:
Comment 1 Len Lawrence 2015-05-11 23:16:14 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).  ???
Comment 2 Len Lawrence 2015-05-12 08:31:18 CEST 
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.
Comment 3 Rémi Verschelde 2015-05-12 09:16:15 CEST 
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
Resolution: (none) => WORKSFORME
Note You need to log in before you can comment on or make changes to this bug.