I am changing the thread title to what the issue this turned out to be, “OM repos 404 not found”.
For information for all users encountering something similar to this:
Edit: For @SilentRanger copying the .repo file I posted should work just fine, then after doing that use Sofware Repository Selector aka om-repo-picker to enable or disable which repos you wish to use. For other users you can get someone to post a working .repo file and copy that or you could do the following:
Download for your OMLx branch and arch, using ROME (rolling repository) x86_64 as the example here:
Download from here: https://abf-downloads.openmandriva.org/
Look for rolling if you use ROME or Rock if you use that and then your arch. Then navigate to the main release repo in this example here: Index of /rolling/repository/x86_64/main/release/
Find and download the .rpm for distro-release-repos in this example: https://abf-downloads.openmandriva.org/rolling/repository/x86_64/main/release/distro-release-repos-25.04-4-omv2504.x86_64.rpm
Then you want to back up your existing .repo file in this example:
cd /etc/yum.repos.d
ls
find your .repo file in this example we:
sudo mv openmandriva-rolling-x86_64.repo openmandriva-rolling-x86_64.repo.bak
So openmandriva-rolling-x86_64.repo.bak is the backed up file in case it is needed in the future. Then:
Navigate to the directory where you downloaded the distro-release-repos .rpm and install that in this case like this:
sudo dnf in distro-release-repos-25.04-4-omv2504.x86_64.rpm
and that should rewrite your .repo file to the latest version available. Then you can open Software Repository Selector aka: om-repo-picker and set which repos you wish enabled.
Note: If you use znver1 just change x86_64 to znver1 in the commands.
Note-2: Obviously this applies IF the problem is something incorrect in the actual .repo file. There are other possible reasons why one might see 404 not found. For instance if you happen to try a dnf transaction while packages are being published or when developers are copying packages from cooker to rolling this results in the repodata being rewritten which dnf sees as “404 Not found”. But this is just a matter of waiting a bit and trying again. Or some server might be down, this is not common but also not never.