14 – Alex Sleat

WARNING: by continuing following this guide you are putting your machine at risk by disabling the secuity features within SELinux, I strongly advise if you do not know what you are doing, stop and read up on the implications this action will have before continuing. Some information is avaible in the Fedora Wiki here .

Open up this file:

sudo gedit /etc/selinux/config

Change the line that looks like this:

SELINUX=enforcing

To this:

SELINUX=permissive

Save and reboot and it should be working, although again be warned this has disabled the security mechanism on your system. To re-enable this, simply do the same however change from permissive to enforcing and again reboot your machine.

After installing dropbox from the RPM package availble on the site on a new Fedora 15 install, I was unable to use yum without coming across this error:

$ update
Loaded plugins: langpacks, presto, refresh-packagekit
http://linux.dropbox.com/fedora/15/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found : http://linux.dropbox.com/fedora/15/repodata/repomd.xml
Trying other mirror.
http://linux.dropbox.com/fedora/15/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found : http://linux.dropbox.com/fedora/15/repodata/repomd.xml
Trying other mirror.
Error: Cannot retrieve repository metadata (repomd.xml) for repository: Dropbox. Please verify its path and try again

For some unknown reason dropbox repos dont seem to work past 13 so you’ll need to change the dropbox.repo file from detecting the current release to 13 like so:

Open the dropbox.repo file:

sudo gedit /etc/yum.repos.d/dropbox.repo

Change the baseurl from $relesever to 13 like so:

Original:

[Dropbox]
name=Dropbox Repository
baseurl=http://linux.dropbox.com/fedora/$releasever/
gpgkey=http://linux.dropbox.com/fedora/rpm-public-key.asc

New:

[Dropbox]
name=Dropbox Repository
baseurl=http://linux.dropbox.com/fedora/13/
gpgkey=http://linux.dropbox.com/fedora/rpm-public-key.asc

Save and close and everything should be working, try using sudo yum update to check and the error should have gone away. If not give a reboot a try.