<div dir="ltr"><div>same problem , i update today 5 am ( chile hour ) and all work fine<br></div>later this i try to install a foo package and f21 fail for the same reason.<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Sep 17, 2014 at 1:52 PM, Joachim Backes <span dir="ltr"><<a href="mailto:joachim.backes@rhrk.uni-kl.de" target="_blank">joachim.backes@rhrk.uni-kl.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On 09/17/2014 06:50 PM, Joachim Backes wrote:<br>
> Trying to rum "yum update" fails actually:<br>
><br>
> ---------------------------------------------------------------------<br>
><br>
> Loaded plugins: langpacks<br>
> adobe-linux-x86_64 | 951 B<br>
> 00:00<br>
> fedora/21/x86_64/metalink | 24 kB<br>
> 00:00<br>
> fedora-cloud/21/x86_64/metalink | 29 kB<br>
> 00:00<br>
> Could not parse metalink<br>
> <a href="https://mirrors.fedoraproject.org/metalink?repo=fedora-cloud-21&arch=x86_64" target="_blank">https://mirrors.fedoraproject.org/metalink?repo=fedora-cloud-21&arch=x86_64</a><br>
> error was<br>
> No repomd file<br>
><br>
><br>
> One of the configured repositories failed (Unknown),<br>
> and yum doesn't have enough cached data to continue. At this point the only<br>
> safe thing yum can do is fail. There are a few ways to work "fix" this:<br>
><br>
> 1. Contact the upstream for the repository and get them to fix the<br>
> problem.<br>
><br>
> 2. Reconfigure the baseurl/etc. for the repository, to point to a<br>
> working<br>
> upstream. This is most often useful if you are using a newer<br>
> distribution release than is supported by the repository (and the<br>
> packages for the previous distribution release still work).<br>
><br>
> 3. Disable the repository, so yum won't use it by default. Yum will<br>
> then<br>
> just ignore the repository until you permanently enable it again<br>
> or use<br>
> --enablerepo for temporary usage:<br>
><br>
> yum-config-manager --disable <repoid><br>
><br>
> 4. Configure the failing repository to be skipped, if it is<br>
> unavailable.<br>
> Note that yum will try to contact the repo. when it runs most<br>
> commands,<br>
> so will have to try and fail each time (and thus. yum will be be<br>
> much<br>
> slower). If it is a very temporary problem though, this is often<br>
> a nice<br>
> compromise:<br>
><br>
> yum-config-manager --save<br>
> --setopt=<repoid>.skip_if_unavailable=true<br>
><br>
> File /var/cache/yum/x86_64/21/fedora-cloud/metalink.xml does not exist<br>
><br>
> ------------------------------------------------------------------------------<br>
><br>
> Anybody has the same problems?<br>
<br>
</div></div>Trying to update without fedora-cloud repo fails too:<br>
----------------------------------------------------------------------------------<br>
<span class=""><br>
Loaded plugins: langpacks<br>
adobe-linux-x86_64 | 951 B<br>
00:00<br>
fedora/21/x86_64/metalink | 24 kB<br>
00:00<br>
</span>fedora-server/21/x86_64/metalink | 29 kB<br>
<span class="">00:00<br>
Could not parse metalink<br>
</span><a href="https://mirrors.fedoraproject.org/metalink?repo=fedora-server-21&arch=x86_64" target="_blank">https://mirrors.fedoraproject.org/metalink?repo=fedora-server-21&arch=x86_64</a><br>
<div class="HOEnZb"><div class="h5">error was<br>
No repomd file<br>
<br>
<br>
One of the configured repositories failed (Unknown),<br>
and yum doesn't have enough cached data to continue. At this point the only<br>
safe thing yum can do is fail. There are a few ways to work "fix" this:<br>
<br>
1. Contact the upstream for the repository and get them to fix the<br>
problem.<br>
<br>
2. Reconfigure the baseurl/etc. for the repository, to point to a<br>
working<br>
upstream. This is most often useful if you are using a newer<br>
distribution release than is supported by the repository (and the<br>
packages for the previous distribution release still work).<br>
<br>
3. Disable the repository, so yum won't use it by default. Yum will<br>
then<br>
just ignore the repository until you permanently enable it again<br>
or use<br>
--enablerepo for temporary usage:<br>
<br>
yum-config-manager --disable <repoid><br>
<br>
4. Configure the failing repository to be skipped, if it is<br>
unavailable.<br>
Note that yum will try to contact the repo. when it runs most<br>
commands,<br>
so will have to try and fail each time (and thus. yum will be be<br>
much<br>
slower). If it is a very temporary problem though, this is often<br>
a nice<br>
compromise:<br>
<br>
yum-config-manager --save<br>
--setopt=<repoid>.skip_if_unavailable=true<br>
<br>
</div></div><span class="HOEnZb"><font color="#888888">Joachim Backes<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
<br>
<br>
--<br>
<br>
Fedora release 21 (Twenty One)<br>
Kernel-3.16.2-301.fc21.x86_64<br>
<br>
<br>
Joachim Backes <<a href="mailto:joachim.backes@rhrk.uni-kl.de">joachim.backes@rhrk.uni-kl.de</a>><br>
<a href="https://www-user.rhrk.uni-kl.de/~backes" target="_blank">https://www-user.rhrk.uni-kl.de/~backes</a><br>
--<br>
test mailing list<br>
<a href="mailto:test@lists.fedoraproject.org">test@lists.fedoraproject.org</a><br>
To unsubscribe:<br>
<a href="https://admin.fedoraproject.org/mailman/listinfo/test" target="_blank">https://admin.fedoraproject.org/mailman/listinfo/test</a></div></div></blockquote></div><br></div>