that should have been:

gurpmi.addmedia

Curiously, both https://mirrors.mageia.org/api/mageia.9.x86_64.list and https://mirrors.mageia.org/api/mageia9.x86_64.list provide a list of mirrors. The first one (with the dot) appears correct and provides a list of 142 mirrors of mga9 for x86_64. The second one (WITHOUT the dot) also provides a list of mirrors, but there are 1104 of them and a mixture of mga9 and cauldron and for all four architectures.

IMHO the output without the dot is just plain wrong and the API should be returning 404 in that case. Consumers of the API SHOULD BE using the version WITH the dot. Looking at my old urpmi.cfg files since mga6 show them all using URLs with the dot.

The issue in comment #2 is that mga10 hasn't been released yet so there are no mirrors for it.

But, I think this dot/non-dot question is a red herring. I still don't see any indication that's the issue at hand in the original report.

Summary: drakrpm-editmedia and the mirrorlist api use different web addresses (with mageia.10 versus mageia10) => drakrpm-editmedia complains that it cannot find any suitable mirror when trying to add a mirror.
Assignee: sysadmin-bugs => bugsquad
CC: (none) => dan
Version: trunk => 9
Component: Other => RPM Packages
Product: Websites => Mageia
Target Milestone: --- => Mageia 9

(In reply to Dan Fandrich from comment #5)

> 
> The issue in comment #2 is that mga10 hasn't been released yet so there are
> no mirrors for it.
> 


Thanks, Dan.

I had assumed that Ben had hit this issue in Mageia 9, because he is a QA tester, but looking at the first bugs mail for this report, he had filed it against Cauldron.

So the problem is, that rpmdrake looks for Mageia 10 mirrors instead of for  Cauldron mirrors.

I have no idea since when this issue occurs, though, I always use my own mirror for my cauldrons.

Assigning to the Mageia Tools maintainers.

Assignee: bugsquad => mageiatools
Summary: drakrpm-editmedia complains that it cannot find any suitable mirror when trying to add a mirror. => drakrpm-editmedia looks for a Mageia 10 mirror instead of for a Cauldron mirror, so cannot find one.
Version: 9 => Cauldron
Target Milestone: Mageia 9 => ---

And here the error again, because I just obsoleted my comments that weren't helpful:


URPMI_ADDMEDIA_REASON reason=update
getting mirror list from https://mirrors.mageia.org/api/mageia.10.x86_64.list?reason=update
retrieved   mageia.10.x86_64.list?reason=update
found geolocalisation BE 50.83 4.33 from timezone Europe/Amsterdam
Fatal: Could not find a mirror from mirrorlist $MIRRORLIST

For the record, https://mirrors.mageia.org/api/mageia.cauldron.x86_64.list does seem to produce a valid list.

See also the thread starting with https://ml.mageia.org/l/arc/qa-discuss/2024-08/msg00008.html.

IIRC, the API usually gets updated to add the new release number when we get to the beta release stage (to allow QA to start testing upgrades). Before that, if you want to use cauldron, you need to ask for cauldron. And I suspect rpmdrake was never really designed to work for cauldron.

CC: (none) => mageia

Created attachment 14799 [details]
patch for cauldron mirrors.

The simplest workaround is to force using "cauldron" as the product version:
URPMI_ADDMEDIA_PRODUCT_VERSION=cauldron drakrpm-editmedia;

The second workaround is to modify the Perl file /usr/share/perl5/vendor_perl/urpm/mirrors.pm with:

sed "/\$product_version =/{s|^|#|;p;s|#||;s|\$product_id->{version};|((\$product_id->{branch} =~ \/devel\/i) ? 'cauldron' : \$product_id->{version});|}" -i /usr/share/perl5/vendor_perl/urpm/mirrors.pm

Attached is a patch for the urpmi source file that is slightly different than the above "sed" command, as I'm not sure if an exact match or a more generic match should be used in this case.

CC: (none) => arusanu