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?

[oscarcosta]

Still waiting a solution for this issue. Dropbox used to work flawless on Fedora until version 31.

[mweirauch]

Hasn't somebody tried just chaing the repository url in /etc/yum.repos.d/dropbox.repo?

What about switching from 'https://linux.dropbox.com/fedora/$releasever/' to 'https://linux.dropbox.com/fedora/31/' for the time being? (I am still on 31.)

[Richard E.7]

mweirauch   has a good idea. As long as the version for Fedora 31 is compatible with 32 this will stop the error messages for the future.

 But we have to keep an eye open for a new version since dnf/yum  will no longer pick them up by default.

[MichaelE]

I agree with Richard E.7... while it does work for now,  it also makes the whole Dropbox process fragile. The better solution would be for Dropbox to fix it.

It does raise the question is Dropbox only really interested in Windows and macOS... considering both of those OSes with MS & Apple have competing offerings to core Dropbox offering. Most of us don't really care for Google drive for good reason. Wonder how Dropbox plans to attract us to their other paid products when they really don't show the love of support for us. Drew, Tim or Bharat?

[oscarcosta]

I'm currently using version 31. It's not ideal, but it works for now. The only caveat is that when Dropbox decides to update repo 32, I’ll need to uninstall this version, edit the repo file, and install nautilus-dropbox again.

[griffineyes]

bump

"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."

[jojopogi]

As of moment 32 is not yet available from the URL repository  https://linux.dropbox.com/fedora/

Instead use 31 and try these two steps.

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

2. Change $releaserver to 31,  save it and run dnf update

Sample
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

[fedora32user]

edit the /etc/yum.repos.d/dropbox.repo like below and you can continue forward as a workaround.

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

[Coca-Cola Advertisement]

Hello everyone!

Rather than add to this thread, I have opened my own issue making a succinct argument to Dropbox so that they understand how this is hurting their bottom line while this should be a very easy fix for them and it inconsistent with their past maintenance for Fedora.

Please upvote and reply to the issue I have opened here: https://www.dropboxforum.com/t5/dropbox-ideas/update-fedora-repositories-from-fedora-workstation-31-...

[Richard E.7]

The temporary 'solution' to eliminate the error message by editing your /etc/yum.repos.d/dropbox.repo file has been recommended 3 times.  No need to add it again. 🙂

Upvote and reply to the issue opened here: https://www.dropboxforum.com/t5/dropbox-ideas/update-fedora-repositories-from-fedora-workstation-31-...