Revision history [back]
 | 1 | initial version |
If Dropbox repo is the the only repo you have problem with then you can temporally disable it from the command line with --disablerepo=Dropbox
yum update --disablerepo=Dropbox
or you can permanently disable the repo by adding the line enabled=0 to the repo file at /etc/yum.repos.d/dropbox.repo
one other option is to change the $releasever variable to fixed value e.g 18.
We have this problem each time when a new Fedora release came out, and Dropbox didn't open a repo for it.
| | 2 | No.2 Revision |
If Dropbox repo is the the only repo you have problem with then you can temporally disable it from the command line with --disablerepo=Dropbox
yum update --disablerepo=Dropbox
or you can permanently disable the repo by adding the line enabled=0 to the repo file at
/etc/yum.repos.d/dropbox.repo
one other option is to change the $releasever variable to fixed value e.g 18.
We have this problem each time when a new Fedora release came out, and Dropbox didn't open a repo for it.
