[SOLVED] Question on "No URLs in mirrorlist"

[svzrd]

Hi,
I upgraded from Mageia 9 to Cauldron. When I do any install/remove/update transaction, I get the following error.

Code: Select all

Mageia Cauldron - x86_64                                            593 kB/s |  10 MB     00:17
Mageia Cauldron - x86_64 - Updates                                   30  B/s | 134  B     00:04
Mageia 10 - x86_64                                                   33  B/s |  58  B     00:01
Error: Failed to download metadata for repo 'mageia-x86_64': Cannot prepare internal mirrorlist: No URLs in mirrorlist
Mageia 10 - x86_64 - Updates                                         33  B/s |  58  B     00:01
Error: Failed to download metadata for repo 'updates-x86_64': Cannot prepare internal mirrorlist: No URLs in mirrorlist
Ignoring repositories: mageia-x86_64, updates-x86_64

I guess, the errors are due to non-existent repos for 'Mageia 10'. Is it safe to disable two repos ('mageia-x86_64' and 'updates-x86_64')? I intend to stay on cauldron.

Also, why are the two 'Mageia 10' repos created when they don't exist yet on the servers?

[sturmvogel]

You may want to do a basic forum search:
https://forums.mageia.org/en/viewtopic.php?f=15&t=15730
My guess is, that you did not follow the correct procedure to switch to Cauldron:
https://wiki.mageia.org/en/Cauldron

Mageia 10 is not released, so no update repos are existing yet.

[svzrd]

You may want to do a basic forum search:
https://forums.mageia.org/en/viewtopic.php?f=15&t=15730

I did. I had also gone through the one you linked. I did not refer to the linked 'release notes' for my upgrade (although I have skimmed over it). To be honest, that wiki page really misleading even when it says 'This page is a draft'.

My guess is, that you did not follow the correct procedure to switch to Cauldron:
https://wiki.mageia.org/en/Cauldron

Mageia 10 is not released, so no update repos are existing yet.

This wiki is what I referred to when doing the upgrade. I followed it to a tee (used the urpmi part). That is the reason I am surprised why the two repos for 'Mageia 10' were there. Now, I've disabled both of them and retained only cauldron, cauldron-updates.

After two weeks or so, I will try to rerun the upgrade procedure on a new Mageia 9 install and see if it generates 'Mageia 10' repos automatically along with cauldron's. It is quite possible, as you mentioned, something was not right with my current upgrade even with my best efforts.

[sturmvogel]

I was able to reproduce the issue in a VB installation. The remaining MGA9 repo links gets converted to MGA10 links (which does not exist yet for update) after successfull upgrade to Cauldron.
This behaviour seems new. I adapted the wiki to make sure that old repos gets disabled/removed..

[svzrd]

Thanks @sturmvogel. If you think it is not a bug and the wiki instruction covers the case, I can close the thread as solved.

[svzrd]

Well, it indeed seems a bug - to enable 'Mageia 10' repos on cauldron system.

Initially I was not sure if it was my mistake during upgrade procedure. But I see same issue with cauldron docker image. If I try to use it with 'distrobox', the container setup fails with exact error.

To check I downloaded the rootfs.tar.xz and checked the repo files and the mageia (10) repos are enabled!

Code: Select all

[sv@vbox cauldron-docker-img]$ grep -E "enabled=1" etc/yum.repos.d/*.repo
etc/yum.repos.d/cauldron-x86_64.repo:enabled=1
etc/yum.repos.d/cauldron-x86_64.repo:enabled=1
etc/yum.repos.d/mageia-x86_64.repo:enabled=1
etc/yum.repos.d/mageia-x86_64.repo:enabled=1
[sv@vbox cauldron-docker-img]$


Checking /etc/yum.repos.d/mageia-x86_64.repo, we see

Code: Select all

[mageia-x86_64]
name=Mageia $releasever - x86_64
#baseurl=https://mirrors.kernel.org/mageia/distrib/$releasever/x86_64/media/core/release/
#metalink=https://mirrors.mageia.org/metalink?distrib=mageia-$releasever&arch=x86_64&section=core&repo=release
mirrorlist=https://www.mageia.org/mirrorlist/?release=$releasever&arch=x86_64&section=core&repo=release
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-Mageia
fastestmirror=1
enabled=1

[updates-x86_64]
name=Mageia $releasever - x86_64 - Updates
#baseurl=https://mirrors.kernel.org/mageia/distrib/$releasever/x86_64/media/core/updates/
#metalink=https://mirrors.mageia.org/metalink?distrib=mageia-$releasever&arch=x86_64&section=core&repo=updates
mirrorlist=https://www.mageia.org/mirrorlist/?release=$releasever&arch=x86_64&section=core&repo=updates
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-Mageia
fastestmirror=1
enabled=1


I disabled the two, rebuilt the docker image locally and with this image, distrobox container setup finished and was able to use the container.

[sturmvogel]

Well, it indeed seems a bug - to enable 'Mageia 10' repos on cauldron system.

Not really. As you can see in the yum repo file (only for DNF), the $releasever variable is used. After succesfull update to cauldron, the relasever is set to 10. That is why you have enabled Mageia 10 repos after upgrade to Cauldron.This is no issue, except that the update repos are not used with Cauldron and therefore are not populated with metadata. Thus the error when using any DNF command.

If you now compare the instructions from urpmi (for switching to cauldron), you will see that all stable repos needs to be removed prior upgrade to Cauldron. As for DNF, the repo definitions are provided via system packages (which can not be deleted). So you need to disable the unneeded yum repos prior upgrade to Cauldron or afterwards.

Should be a simple task for a Cauldron user.

[svzrd]

@sturmvogel, thank you so much for the clarification. Now I get it. Marking the topic as solved.