There isn't a Linux repository for Fedora 32

[tdias]

Hello everyone.

An RPM repo for Fedora 32 hasn't been created yet, which leads to errors every time I use my package manager.

Is Dropbox aware of this problem?

[Lusil]

Hello everyone, thanks for your ongoing reports on this. 

In order for us to have a better look into this with each one of you more in-depth, could you please contact our Support team from this link? 

If you can't submit a ticket or you have trouble doing so, I'm more than happy to send you one, instead. 

Just give me another nudge and I'll make sure to get back to you as soon as possible.

Thanks again, everyone!

[Richard E.7]

Lusil, I can find no link or option to report this issue on the page for which you provided the link. It contains only "Helpful articles", "Helpful tools" and links to "Chatbox" and "Community". Perhaps this is due to my account level (free).

I'm including a summary below.

 The problem is very straight forward. Fedora users are seeing the following error message (or something similar) when they attempt to update their systems from your online repositories:

"Dropbox Repository 109 kB/s | 25 kB 00:00
Errors during downloading metadata for repository 'Dropbox':
- Status code: 404 for http://linux.dropbox.com/fedora/32/repodata/repomd.xml (IP: 99.84.47.55)
Error: Failed to download metadata for repo 'Dropbox': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried
Ignoring repositories: Dropbox

Last metadata expiration check: 2:42:44 ago on Sun 05 Jul 2020 07:36:46 PM EDT."

This indicates that the repository at http://linux.dropbox.com/fedora/32 does not exist. There is nothing available for version 32 of Fedora. We find that if you "hardwire" 31 into the correct place in your system it works. This indicates that there is compatibility between these 2 versions.

When this is the case it would be very helpful to simply link the two locations in your repository, or perhaps copy version 31 into the location for version 32.

The following was provided as an example to work around this issue:

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/31/
gpgkey=http://linux.dropbox.com/fedora/rpm-public-key.asc

The problem with doing this is that when/if a version becomes available for Fedora version 32, the update process will not detect it.

It would be better if this were fixed on the Dropbox site rather than having all the Dropbox Fedora users "hack" their systems. The simplest way to assist your users would be to either create a link from version 31 for version 32 in your repository, or copy the code from version 31 and place it in the version 32 location. Of course, this assumes that version 31 is qualified for version 32.

[Lusil]

Thanks for your extensive description, @Richard E.7 - greatly appreciated. 

I understand how important this is for all of you, however, it would be best to troubleshoot this with each user separately, due to account-specific information that might be needed, so that our team can investigate more efficiently. 

Having said that, I've sent you a ticket, so when you get the chance, please check your inbox for my latest message and we'll take it from there. 

Thanks again!

[MichaelE]

Dropbox not having a Repo for Fedora 32 is not a specific user error. Its a complete failure on Dropbox's part.

[MichaelE]

These are workaround to dropbox not creating a symbolic link. Maybe Dropbox can't handle the additional storage space.

[petasis]

There is really no point in talking to dropbox. I have complained here, and I have conducted customer support. The reply is monotonously the same (no answer). Also technical support wants linux users to use an older repository (putting something stale in their operating system).

I refuse to do this. So I removed completely the dropbox repository from all my Fedora Linux computers. Their Linux support is very bad anyway. Without updates, when dropbox will stop working, I will stop paying.

As simple as that...

[Coca-Cola Advertisement]

Hold on everybody. We're living during a global pandemic--we don't know what is going on internal to the company that could be slowing down the normal process for support. They probably had turnover and the new staff don't know exactly what the old staff were doing for us.

[Coca-Cola Advertisement]

@Lusil

The issue that every user in this thread is facing will be the same if you open individual tickets for them.

Please refer to this issue where I explain what is going wrong in clear language to make this easier: https://www.dropboxforum.com/t5/Dropbox-ideas/Update-Fedora-Repositories-from-Fedora-Workstation-31-...

Here is a link to your Linux repository: https://linux.dropbox.com/fedora/

Please note that in your repository you are missing a folder for "32". This is the problem.

Is there a way to send this to the team at Dropbox who maintains this repository? Please get us in touch with this team.

[Coca-Cola Advertisement]

To those in the thread, maybe one of you could watch their jobs page and then work for them and fix this for us if the problem is turnover: https://www.dropbox.com/jobs

[XxBatfaIla7]

I was also facing this problem and few minutes ago I came into a solution. So here it is:

You need to edit your Dropbox.repo file.

Type this in your terminal:

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

and change 

baseurl=http://linux.dropbox.com/fedora/$releasever/

to

baseurl=http://linux.dropbox.com/fedora/31/

and that's it.