Bonjour , après avoir fais une petite mise à jour je me suis confronté a un problème avec Yum , il actuellement impossible d'installer un logiciel , en effet à chaque yum install , j'ai le droit à ça : 
 One of the configured repositories failed (Inconnu),
 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/19-2/fedora/metalink.xml does not exist
[gamerlix@localhost ~]$
Si quelqu'un à une idée , ou un lien qui pourrai m'aider , ça serai cool , merci :hammer:
> One of the configured repositories failed (Inconnu)
yum repolist donne quoi ? ou le contenu du /etc/yum.repos.d ?
Merci j'ai exécute ta commande et j'ai obtenu ceci : 
[root@localhost gamerlix]# yum repolist
Modules complémentaires chargés : langpacks, refresh-packagekit
adobe-linux-x86_64                                       |  951 B     00:00     
fedora/19-2/x86_64/metalink                              |  27 kB     00:00     
Could not parse metalink https://mirrors.fedoraproject.org/metalink?repo=fedora-19-2&arch=x86_64 error was 
No repomd file
adobe-linux-x86_64                                                          2/2
playonlinux                                              |  951 B     00:00     
playonlinux                                                               38/38
updates/19-2/x86_64/metalink                             |  27 kB     00:00     
Could not parse metalink https://mirrors.fedoraproject.org/metalink?repo=updates-released-f19-2&arch=x86_64 error was 
No repomd file
viperr-stable                                            | 2.9 kB     00:00     


 One of the configured repositories failed (Inconnu),
 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/19-2/fedora/metalink.xml does not exist
J'ai télécharger à l'adresse https://mirrors.fedoraproject.org/metalink?repo=fedora-19-2&arch=x86_64 le fichier metalink, et je l'ai placé à /var/cache/yum/x86_64/19-2/fedora/.
Maintenant j'obtiens ceci: 
[root@localhost gamerlix]# yum repolist
Modules complémentaires chargés : langpacks, refresh-packagekit
adobe-linux-x86_64                                       |  951 B     00:00     
fedora/19-2/x86_64/metalink                              |  27 kB     00:00     
Could not parse metalink https://mirrors.fedoraproject.org/metalink?repo=fedora-19-2&arch=x86_64 error was 
No repomd file
playonlinux                                              |  951 B     00:00     
updates/19-2/x86_64/metalink                             |  27 kB     00:00     
Could not parse metalink https://mirrors.fedoraproject.org/metalink?repo=updates-released-f19-2&arch=x86_64 error was 
No repomd file
viperr-stable                                            | 2.9 kB     00:00     


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

No repomd file
Je précise que je suis sous Viperr , remix de Fedora avec openbox c'est pour cela qu j'ai un dépot nommé viperr
=> fedora/19-2/
19-2 ça n'existe pas, donc voir avec Viper
Ce n'est clairement pas un problème Fedora.
Bon y a du nouveau , j'ai consulté le bugzilla et autre site et maintenant voici ce que j'obtiens si je tente une update : 
[root@localhost yum.repos.d]# yum update
Modules complémentaires chargés : langpacks, refresh-packagekit


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

Cannot find a valid baseurl for repo: rpmfusion-free/$releasever/x86_64
[root@localhost yum.repos.d]#
remi wrote:=> fedora/19-2/
19-2 ça n'existe pas, donc voir avec Viper
Ce n'est clairement pas un problème Fedora.
il est tellement facile de jette la pierre sur viperr sans reèl analyse ce qu'est viperr et de ce qu'elle fait.

viperr n'est rien d'autre qu'une fedora generic ! qui utilise le paquet generic-release de fedora pour enlever les branding fedora. les rpm de viperr ne touche en rien au système fedora generic.

Il y a actuellement de gros problème avec les paquet generic ( et ils viennent de fedora pas de viperr).

Merci de ta compréhension remi.