Description of problem: During an installation with errors as reported in bugs 31034 and 31046 the attempt to set up online sources for urpmi fails: <quote> There was a problem adding medium: Could not find a mirror from mirrorlist $MIRRORLIST Failure when adding medium Retry? </quote> Selected "Previous" to continue to the end. Version-Release number of selected component (if applicable): Mageia9-alpha1 How reproducible: Seems consistent on some hardware. Steps to Reproduce: 1. Start installing from the iso 2. Enable networking 3. Choose a mirror 4. Continue to the configuration stage and install the bootloader 5. Agree to setting up download sources 6. Observe the quoted message shown above 7. Select "Previous" to finish 8. Boot the system and try to set up the media sources with drakrpm-edit-media 9. Observe failure to obtain a mirrorlist
Thank you for the report. It looks as if the failure, if it occurs during installation, repeats in the installed system. Indefinitely? Are you alone in discovering this? (I am thinking of the PAD). Can you select a specific repo from the offered lists? CC'ing Dave who knows this area.
CC: (none) => davidwhodgins, lewyssmith
This appears to be a bug in the latest version of curl. The mirror list is downloaded using a command like this: curl -O 'http://mirrors.mageia.org/api/mageia.9.i586.list?reason=upgrade' The -O option tells curl to use the tail end of the URL as the file name in which to store the downloaded text. In Mageia 8, executing that command will create a file named 'mageia.9.i586.list?reason=upgrade'. In cauldron, it will create a file named 'mageia.9.i586.list'. But urpmi.addmedia is expecting the first file name, so thinks the download has failed.
CC: (none) => mageiaSource RPM: (none) => curl
I have submitted an upstream bug report to find out if this was an intentional change: https://github.com/curl/curl/issues/9826
In reply to comment 1: It looks as if the failure, if it occurs during installation, repeats in the installed system. Indefinitely? As far as I can tell. Have not noticed such reports from others. There are no offered lists - that is the point: no contact with $MIRRORLIST. The explanation in comment 2 raises the question - why only on my mini PCs?
Other reports are coming in, see bug 31049 and the qa-discuss mailing list. As the problem is in the curl program, yes it will affect the installed system too. Configure urpmi to use wget instead of curl to work round this (you will need to install wget if it isn't already installed). Unfortunately I saw this report after I had built and tested the latest round of ISOs, otherwise I would have forced the installer to use wget too. I am puzzled why you aren't seeing the same problem on other systems.
See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=31049
Priority: Normal => release_blocker
I shall check again on my production system. Meanwhile the new alpha works better at the bootloader stage (bug 31049). Media sources available now using wget.
Did you enable additional sources at the start of installation? The first round of ISOs had curl-7.85.0, which doesn't have this bug. But if you had enabled online media at the start of installation, the new version of curl would have been installed and then used when you tried to set up online media at the end of installation.
This problem continues to persist this morning as of the date & time of this posting. Severely limits testing of M9 isos
CC: (none) => wilcal.int
Attempting to manually install repo from my local source retreving failed, curl failed exited with 7 no metadata found for medium "core64" Same error is displayed for the M8 repo which works just fine on M8
@Bill, see comment 5. Configure urpmi to use wget, not curl.
If I try to add my local M9 core repo to a working M8 Vbox client the following error is displayed: urpmi.addmedia core64 http://192.168.0.9:8080/~mageia/distrib/9/x86_64/media/core/release with media_info/hdlist.cz adding medium "core64" http://192.168.0.9:8080/~mageia/distrib/9/x86_64/media/core/release/media_info/20221101-101846-synthesis.hdlist.cz ...retrieving failed: curl: (22) The requested URL returned error: 404 Not Found ...retrieving failed: curl failed: exited with 22 problem reading synthesis file of medium "core64" exact same process using: urpmi.addmedia core64 http://192.168.0.9:8080/~mageia/distrib/8/x86_64/media/core/release with media_info/hdlist.cz works just fine
Fixed by urpmi-8.128-1.mga9, which supports both the old and new curl behaviour.
Status: NEW => RESOLVEDResolution: (none) => FIXED
(In reply to Martin Whitaker from comment #12) > Fixed by urpmi-8.128-1.mga9, which supports both the old and new curl > behaviour. Kudos to Martin. You're the man.