Problem with update after branching Rawhide to F21

Jon Ingason jon.ingason at
Sun Jul 27 16:24:16 UTC 2014

I follow the Rawhide wiki how to branch Rawhide to Fedora 21.
What I did was that I installed
Fedora-Live-Workstation-x86_64-rawhide-20140723.iso to VM with libvirt.
Then I clone it and used it to do the brancing.

I did following:

$ su -c 'yum-config-manager --disable rawhide'
$ su -c 'yum-config-manager --enable fedora,updates,updates-testing'
$ su -c 'yum --releasever=(version) distro-sync'

$ more /etc/fedora-release
Fedora release 21 (Twenty One)

Then I tested to do update with following results:

$ sudo yum update
[sudo] password for user:
Inlästa insticksmoduler: langpacks
fedora/22/x86_64/metalink                                   |  29 kB
Could not parse metalink
error was
No repomd file

 One of the configured repositories failed (Okänd),
 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

     2. Reconfigure the baseurl/etc. for the repository, to point to a
        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
        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
        Note that yum will try to contact the repo. when it runs most
        so will have to try and fail each time (and thus. yum will be be
        slower). If it is a very temporary problem though, this is often
a nice

            yum-config-manager --save

File /var/cache/yum/x86_64/22/fedora/metalink.xml does not exist

What does that mean? How can I fix this?

Jon Ingason

More information about the test mailing list