{{{
[root@sharpie ~]# yum --enablerepo='debug' install /usr/lib/debug/.build-id/19/294b37440dfa2b227d18083b75cd8e9381c559
Loaded plugins: langpacks, refresh-packagekit
fedora/20/ppc64/metalink | 2.5 kB 00:00:00
fedora-debuginfo/20/ppc64/metalink | 2.5 kB 00:00:00
updates/20/ppc64/metalink | 2.4 kB 00:00:00
updates-debuginfo/20/ppc64/metalink | 2.5 kB 00:00:00
updates-testing/20/ppc64/metalink | 2.5 kB 00:00:00
updates-testing-debuginfo/20/ppc64/metalink | 26 kB 00:00:00
Could not parse metalink https://mirrors.fedoraproject.org/metalink?repo=updates-testing-debug-f20&arch=ppc64 error was
No repomd file

One of the configured repositories failed (Unknown),
and yum doesn't have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work "fix" this:

 1. Contact the upstream for the repository and get them to fix the problem.
 2. Reconfigure the baseurl/etc. for the repository, to point to a working
    upstream. This is most often useful if you are using a newer
    distribution release than is supported by the repository (and the
    packages for the previous distribution release still work).
 3. Disable the repository, so yum won't use it by default. Yum will then
    just ignore the repository until you permanently enable it again or use
    --enablerepo for temporary usage:
        yum-config-manager --disable <repoid>
 4. Configure the failing repository to be skipped, if it is unavailable.
    Note that yum will try to contact the repo. when it runs most commands,
    so will have to try and fail each time (and thus. yum will be be much
    slower). If it is a very temporary problem though, this is often a nice
    compromise:
        yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

File /var/cache/yum/ppc64/20/updates-testing-debuginfo/metalink.xml does not exist
}}}

ive updated things in the database, after the next run through things should be okay, please let us know if its not in 3 hours