Updating F21 currently fails

[Carlos Morel-Riquelme]

same problem , i update today 5 am ( chile hour ) and all work fine
later this i try to install a foo package and f21 fail for the same reason.

On Wed, Sep 17, 2014 at 1:52 PM, Joachim Backes <
joachim.backes at rhrk.uni-kl.de> wrote:

> On 09/17/2014 06:50 PM, Joachim Backes wrote:
> > Trying to rum "yum update" fails actually:
> >
> > ---------------------------------------------------------------------
> >
> > Loaded plugins: langpacks
> > adobe-linux-x86_64                                          |  951 B
> > 00:00
> > fedora/21/x86_64/metalink                                   |  24 kB
> > 00:00
> > fedora-cloud/21/x86_64/metalink                             |  29 kB
> > 00:00
> > Could not parse metalink
> >
> https://mirrors.fedoraproject.org/metalink?repo=fedora-cloud-21&arch=x86_64
> > 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/x86_64/21/fedora-cloud/metalink.xml does not exist
> >
> >
> ------------------------------------------------------------------------------
> >
> > Anybody has the same problems?
>
> Trying to update without fedora-cloud repo fails too:
>
> ----------------------------------------------------------------------------------
>
> Loaded plugins: langpacks
> adobe-linux-x86_64                                          |  951 B
> 00:00
> fedora/21/x86_64/metalink                                   |  24 kB
> 00:00
> fedora-server/21/x86_64/metalink                            |  29 kB
> 00:00
> Could not parse metalink
>
> https://mirrors.fedoraproject.org/metalink?repo=fedora-server-21&arch=x86_64
> 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
>
> Joachim Backes
>
>
>
> --
>
> Fedora release 21 (Twenty One)
> Kernel-3.16.2-301.fc21.x86_64
>
>
> Joachim Backes <joachim.backes at rhrk.uni-kl.de>
> https://www-user.rhrk.uni-kl.de/~backes
> --
> test mailing list
> test at lists.fedoraproject.org
> To unsubscribe:
> https://admin.fedoraproject.org/mailman/listinfo/test
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.fedoraproject.org/pipermail/test/attachments/20140917/a4c5aac6/attachment.html>