Latest version of epel-release ships with epel-testing.repo which points to a none existing testing-epel8 repo and therefore gives an error 'Failed to synchronize cache for repo 'epel-testing', ignoring this repo.' to user using yum --enablerepo=epel-testing
[cloud-user@lxvmc8-amd64 ~]$ curl "https://mirrors.fedoraproject.org/metalink?repo=testing-epel8&arch=x86_64" | grep ^testing % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 54197 100 54197 0 0 394k 0 --:--:-- --:--:-- --:--:-- 394k [cloud-user@lxvmc8-amd64 ~]$ curl "https://mirrors.fedoraproject.org/metalink?repo=testing-epel8&arch=x86_64" | grep testing-epel invalid repo or arch # repo=testing-epel4&arch=i386 # repo=testing-epel4&arch=ppc # repo=testing-epel4&arch=x86_64 # repo=testing-epel5&arch=i386 # repo=testing-epel5&arch=ppc # repo=testing-epel5&arch=x86_64 # repo=testing-epel6&arch=i386 # repo=testing-epel6&arch=ppc64 # repo=testing-epel6&arch=x86_64 # repo=testing-epel7&arch=aarch64 # repo=testing-epel7&arch=ppc64 # repo=testing-epel7&arch=ppc64
Metadata Update from @alphacc: - Issue close_status updated to: Duplicate - Issue status updated to: Closed (was: Open)
Not sure which ticket is the duplicate one, but I reset the ctime of all files testing/8 in the database and now MM was able to detect the repositories. The testing-epel8 repository should soon show up (two hours at most).
Login to comment on this ticket.