Bonjour,
J'ai également fais la mise à jour de F20 à F21. Tout se passe bien mais j'ai un souci depuis lorsque j'essaie de faire un update. QQn a-t-il deja connu ce probleme et comment s'en sortir.
fedora@localhost ~$ sudo yum update
Modules complémentaires chargés : fastestmirror, langpacks
adobe-linux-x86_64 | 951 B 00:00
fedora/21/x86_64/metalink | 28 kB 00:00
fedy | 1.6 kB 00:00
http://www.infinality.net/fedora/linux/21/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Essai d'un autre miroir.
http://www.infinality.net/fedora/linux/21/noarch/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Essai d'un autre miroir.
One of the configured repositories failed (Infinality - noarch),
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 infinality-noarch
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=infinality-noarch.skip_if_unavailable=true
failure: repodata/repomd.xml from infinality-noarch: [Errno 256] No more mirrors to try.
http://www.infinality.net/fedora/linux/21/noarch/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Je me suis dis que c'était le repo de fedy qui devait bloquer je l'ai édité pour mettre "enable=0" mais toujours le même prob avec un autre repo.
Merci pour votre aide.