I have 36 installed as my OS on a new build. I did the easy 35 to 36 system upgrade and now MySQL repo isn’t responding. I’m at the point where I just want to reflash my system with 36 iso and start over. If I go into my bio and boot from a bootable flash drive, will it automaticly earse my curent OS “Fedora 36” and make it so I am starting with a fresh Fedora 36?
MySQL 8.0 Community Server 6.5 B/s | 10 B 00:01
Errors during downloading metadata for repository ‘mysql80-community’:
Status code: 404 forhttp://repo.mysql.com/yum/mysql-8.0-community/fc/36/x86_64/repodata/repomd.xml (IP: 2.18.160.230)
Error: Failed to download metadata for repo ‘mysql80-community’: Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried
MySQL Connectors Community 5.6 B/s | 10 B 00:01
Errors during downloading metadata for repository ‘mysql-connectors-community’:
Status code: 404 forhttp://repo.mysql.com/yum/mysql-connectors-community/fc/36/x86_64/repodata/repomd.xml (IP: 2.18.160.230)
Error: Failed to download metadata for repo ‘mysql-connectors-community’: Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried
MySQL Tools Community 5.7 B/s | 10 B 00:01
Errors during downloading metadata for repository ‘mysql-tools-community’:
Status code: 404 for http://repo.mysql.com/yum/mysql-tools-community/fc/36/x86_64/repodata/repomd.xml (IP: 2.18.160.230)
Error: Failed to download metadata for repo ‘mysql-tools-community’: Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried
Ignoring repositories: mysql80-community, mysql-connectors-community, mysql-tools-community
Last metadata expiration check: 0:03:27 ago on Thu 30 Jun 2022 05:32:03 PM EDT.
No match for argument: all
Error: No packages marked for upgrade.
I’ve tried several different fixes to include removing mysql and reinstalling. This issue is driving me crazy and any assistance would be great.
But why would re-installing F36 fix repo errors? Is the rest of Fedora Linux behaving as expected? If so, I would suggest you just have an error in the url somewhere.
Thank you for responding. I have not been able to correct this issue. I have been opening all the files and haven’t found were to put the correct address. I have checked out Index of /232905/yum, just incase I find where to correct the url. Do you have any suggestions on where I should start?
/etc/yum.repos.d/ is where the files that point to your configured repos are. Normally, you add a repo with dnf. So to see what repos you have already configured enter dnf repolist. To look at how you can use dnf to query or add repo’s you can start with dnf --help then dnf <command> --help once you have the command interested in.
Thank you, --help has been a great starting point. Hopefully I will figure it out soon. I’ve been Fedora for 2 years, so still pretty new when issues come up. They are rarely the same issue and takes me days to find out why something didn’t update right, a key expired, or a url changed.
If you use your web browser you will find that the path you are trying to reach does not exist. https://repo.mysql.com/yum/mysql-cluster-8.0-community/ does not have an fc subdirectory.
The issue is not with fedora but rather with the url within the mysql? .repo file located in /etc/yum.repos.d/ that you are using. In fact I think fedora has mostly switched from mysql to mariadb or postgresql for the db it distributes.
I see a Index of /232905/yum/mysql-8.0-community/fc directory but it’s subdirectory list ends at 35. So there is no version yet for Fedora 36. Probably the paths in the mysql file in /etc/yum.repos.d contain the variable $releasever, which means that this is incremented going from 35 to 36. You can try to hardcode the 35 in the dnf file, but of course you might run into dependency problems. Or if you know how to build packages, download the Fedora35 SRPM and see whether it builds the F36 rpm. Alternative is use podman and pull a Fedora 35 container, install the F35 Mysql version within it and run with podman F35 Mysql in a F35 environment under F36.