On 2 June 2016 at 09:24, Michael Mol <mike(a)virtualinterconnect.com> wrote: > Ran a yum check-update on a staleish host this morning, saw these. They ask > that I contact the epel-testing and epel-testing-source repository owners, > which appear to be this list. > > > Update notice FEDORA-EPEL-2016-7a12df64c2 (from epel-testing) is broken, or a > bad duplicate, skipping. > You should report this problem to the owner of the epel-testing repository. > Update notice FEDORA-EPEL-2016-4a34feb770 (from epel-testing) is broken, or a > bad duplicate, skipping. > Update notice FEDORA-EPEL-2016-68173ad9aa (from epel-testing) is broken, or a > bad duplicate, skipping. > Update notice FEDORA-EPEL-2016-3ad7519632 (from epel-testing) is broken, or a > bad duplicate, skipping. > Update notice FEDORA-EPEL-2016-d116318f11 (from epel-testing) is broken, or a > bad duplicate, skipping. > Update notice FEDORA-EPEL-2016-a3e8d9b435 (from epel-testing) is broken, or a > bad duplicate, skipping. > Update notice FEDORA-EPEL-2016-7a12df64c2 (from epel-testing-source) is > broken, or a bad duplicate, skipping. OK I have replicated it in EPEL-7 Update notice FEDORA-EPEL-2016-68173ad9aa (from epel-testing) is broken, or a bad duplicate, skipping. Update notice FEDORA-EPEL-2016-3ad7519632 (from epel-testing) is broken, or a bad duplicate, skipping. Update notice FEDORA-EPEL-2016-d116318f11 (from epel-testing) is broken, or a bad duplicate, skipping. Update notice FEDORA-EPEL-2016-a3e8d9b435 (from epel-testing) is broken, or a bad duplicate, skipping. It does not seem to break yum update.. will try to figure out what is causing this. Thnaks. -- Stephen J Smoogen.
