Wow! I was just looking the same thing and... saw this post from an hour ago.
So they basically don't care about any of the users, right?
Would it be possible for any of you to try to use the build that we have available for Fedora in https://www.dropbox.com/install-linux and let me know if you're able to install Dropbox successfully with it regardless of the version of Fedora you have?
Also, could any of you let me know your use case for the repo in https://linux.dropbox.com/fedora/ and why the build mentioned above is not sufficient for you (may not fulfill that use case)?
That will give us a better idea about next steps.
Thank you very much and also thanks for your patience on this matter.
Yes, installing the RPM works and DropBox functions.
The Linux repo is the standardized way of distributing packages. If you understand the concept of the Apple or Google App store for your iOS or Android device that is what Linux repos give you but they go one step further they allow you to have multiple repos so that you can get software that is not part of the core OS distro. The update and install tools in Linux like apt, yum, dnf, or pacman used the repos that are on a system and when you install an package it pulls from all of the repos to satisfy any dependencies are needed, it also will tell you if there are any conflicts with libraries or packages.
There is another aspect to this if you are dealing with multiple Linux systems. With repos you can have the repo for the software you need/want included in the image when you provision the systems and it is a simple command to install and/or update multiple systems. If you rely on individule rpm/deb files that you down load you have to distribute and install them which is a more cumbersome process. There are also repo managment tools like Spacewalk that allow you to configure the standard repos you want to use in your organization and have your linus systems pull from centralized system so you can keep the systems configured the same across the environment and only have to pull packages from the internet once.
The use case is very straight forward. RPM repositories are designed to make it possible to automatically update software WITHOUT user involvement. The solution that you all provide on your install page is a manual process that is only good for a onetime installs and does not deal with ongoing updates.
It is probably worth noting that Fedora 28 is coming out in days, so you should honestly be adding packages for both Fedora 27 and Fedora 28.
It is possible that this may be as simple as linking the Fedora 27 and 28 directories in that repo to the Fedora 26 directory, until real packages can be built for each of those platforms.
If you don't want to upgrade repositories every new version of Fedora, just change one line in the dropbox.repo file
[Dropbox] name=Dropbox Repository baseurl=http://linux.dropbox.com/fedora/$releasever/ gpgkey=https://linux.dropbox.com/fedora/rpm-public-key.asc
[Dropbox] name=Dropbox Repository baseurl=http://linux.dropbox.com/fedora/1.0/ gpgkey=https://linux.dropbox.com/fedora/rpm-public-key.asc
add new folder 1.0 in the repo directory and that will fix most of the users' problems. In case of some breaking change, just bump the version and we're done.
Using a single repo for all versions is not a good idea since Dropbox is not statically linked and is dependent on existing libraries that will likely change from version to version.
By hard coding the Fedora release version you are breaking the automatic method that the whole repo system is built on. In a single repo you can have multiple versions of the RPM which the packaging tool like dnf can select the once that fits the system it is being installed on. For example in the repo for Fedora 10 x86_64 there are:
So if you have something installed that requres librires that conflict with version 2015.10.28-1 of Dropbox but not ver 2015.02.12-1 dnf wil update you to 2015.02.12-1 and not 2015.10.28-1.
Thanks a lot for the information provided. Your input will definitely inform our considerations for the repo in https://linux.dropbox.com/fedora/ in the future.
Please continue to use the build available in https://www.dropbox.com/install-linux in the meantime. The Dropbox desktop application should be able to auto-update to newer versions by itself.
It's not just Fedora. Debian and Ubuntu also do not have folders for their most recent releases.
Even if the Dropbox client is able to self-update, that might not be an option for everybody. Not to mention that, at the very least, repositories should be created for newer releases of distributions.
Optimally, an updated version of the client should be kept on the repositories, even if it's the same one for every release of every distro.
If you need more help you can log a ticket with our Support Team here (expected response time 24 hours), or contact us on Twitter or Facebook.
For more info on available support options, see this article.
If you found the answer to your question, please 'like' the post to say thanks to the user!
Solved! : See solution