Bug 26383

Summary:	Stock mirrors invalid
Product:	Mageia	Reporter:	A H <adampanda81>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED WORKSFORME	QA Contact:
Severity:	normal
Priority:	Normal	CC:	lewyssmith, manuel.mageia, ngompa13
Version:	Cauldron
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:

Description A H 2020-03-27 07:01:32 CET

Description of problem: 

The default mirror list (generator) that Mageia uses when first installed is invalid (all of them end with 404 errors) https://www.mageia.org/mirrorlist/?release=cauldron&arch=x86_64&section=core&repo=release

 They're looking for the file repomd.xml except it does not exist on ANY mirror.

This means out of the box a new user would be confused about why they could not update, to begin with.



Steps to Reproduce:
1. Install Mageia
2. Attempt to install after first signing in on your fresh install

sudo dnf upgrade --refresh

Comment 1 Manuel Hiebel 2020-03-27 12:01:04 CET

Hello,

You got only error with updates repo right ?

If so I guess this a noissue as these repo are not used in cauldron

see: https://ftp5.gwdg.de/pub/linux/mageia/distrib/cauldron/x86_64/media/core/updates/repodata/

versus: https://ftp5.gwdg.de/pub/linux/mageia/distrib/cauldron/x86_64/media/core/release/repodata/

but maybe we can still add something

CC: (none) => ngompa13
Component: Installer => RPM Packages

Comment 2 Lewis Smith 2020-06-18 21:06:19 CEST

> This means out of the box a new user would be confused about why they
> could not update, to begin with.
This is clearly not true, because every new installation (from an ISO = out-of-the-box) can be updated during the installation|after first boot, or subsequently. For example, I have just installed the first M8 pre-release, accepted its offer to set up the on-line repos, and later updated it without any fiddling at all.

OTOH Cauldron installations may be a different case.

@Manuel: Thanks for your comment. Can we properly assign this, or close it (what reason?)?

CC: (none) => lewyssmith, manuel.mageia

Comment 3 Manuel Hiebel 2020-06-19 18:45:13 CEST

yes

Status: NEW => RESOLVED
Resolution: (none) => WORKSFORME