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?

It seems that finally they updated the repository for Fedora 32. https://linux.dropbox.com/fedora/32/ its working now. Thanks

There isn't a Linux repository for Fedora 32

sherlock_pipe
Explorer | Level 4
5 years ago
Another Feodra user here facing the same issue. It is really annoying, in worst case they could at least copy the same Fedora 31 content in `32/` folder, this way the package manager `dn`f would not fail to fetch repo contents every time the system is upgraded. What are the Dropbox admins intentions for supporting Fedora 32? Ubuntu 20.04 users have no problems at this time.
- Richard E.7
  Helpful | Level 6
  5 years ago
  I concur with "sherlock_pipe". If the 31 release is compatible with 32, a link to or copy of the same package would help out your users.
  If it is a matter of testing/verification that compatibility exists, could you give us an estimate of the typical time before the latest version will be available from the repository?
  
  Thanks for you consideration.
  - silveraignacio
    New member | Level 2
    5 years ago
    Hello! Same issue here! It is anoying. Package manager is always displaying that error that can be easily fixed!
petasis
Helpful | Level 6
5 years ago
Why this has not been fixed already????????????????
My Fedora 32 system CANNOT update, because of the broken dropbox repository!!!

Dropbox Repository 77 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.86.243.9)
Error: Failed to download metadata for repo 'Dropbox': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried
- prajwel
  Helpful | Level 5
  5 years ago
  I'm eagerly waiting for the fedora 32 version so that I can update.
- fedora32user
  Explorer | Level 3
  5 years ago
  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
  - MichaelE
    Helpful | Level 6
    5 years ago
    These are workaround to dropbox not creating a symbolic link. Maybe Dropbox can't handle the additional storage space.
oscarcosta
Helpful | Level 5
5 years ago
Still waiting a solution for this issue. Dropbox used to work flawless on Fedora until version 31.
- mweirauch
  Helpful | Level 6
  5 years ago
  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
    Helpful | Level 6
    5 years ago
    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.
swhitmore
Explorer | Level 4
5 years ago
Loyal customer of 7 years here. Any update on this Dropbox? Like other users have said this should be a super simple fix and will make a portion of your customers happy.
griffineyes
Explorer | Level 4
5 years ago
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
  Explorer | Level 4
  5 years ago
  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
  - Richard E.7
    Helpful | Level 6
    5 years ago
    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-to-fedora/idi-p/436151
user981376
New member | Level 2
5 years ago
After installing Dropbox on Fedora 32 and running the following command:
dnf update
I get this error:
Dropbox Repository 20 kB/s | 25 kB 00:01 Errors during downloading metadata for repository 'Dropbox': - Status code: 404 for http://linux.dropbox.com/fedora/32/repodata/repomd.xml (IP: 13.35.111.119) Error: Failed to download metadata for repo 'Dropbox': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried Ignoring repositories: Dropbox
It seems that replacing "/32/" with "/31/" in the URL gives a valid XML response, so I imagine Dropbox doesn't have an updated repo for Fedora yet.
- oscarcosta
  Helpful | Level 5
  5 years ago
  It seems that finally they updated the repository for Fedora 32. https://linux.dropbox.com/fedora/32/ its working now.
  
  Thanks
  - Richard E.7
    Helpful | Level 6
    5 years ago
    Indeed, there is now a repository for Fedora 32. But I'm curious to know if they have fixed their release process so we won't run into this again when Fedora 33 is released.
    
    Dropbox, Jay Lusil can you let us know if there is really a long term solution in place for this, please?
    
    ~~R
MichaelE
Helpful | Level 6
5 years ago
Come on Dropbox... how hard is it? Granted I know Fedora is not your main demographic but its going on 2 months.
MichaelE
Helpful | Level 6
5 years ago
Myself and 689 others would like to know if Dropbox is going to fix the Fedora 32 repo link? Its been 2 months.
Jay
Dropbox Staff
5 years ago
Hi , thanks for posting on the Community!

I appreciate the info, I've forwarded the details to my colleagues to look into this matter further.

Let me know if you need any further assistance!
- Coca-Cola Advertisement
  Helpful | Level 5
  5 years ago
  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-to-fedora/idi-p/436151
XxBatfaIla7
New member | Level 2
5 years ago
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.
- petasis
  Helpful | Level 6
  5 years ago
  This "solution" has been written already many times. This is not a solution.
- Richard E.7
  Helpful | Level 6
  5 years ago
  XxBatfaIla7 wrote:
  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.
  XxBatfaIla7 Thanks for adding that but it has been suggested already.
  While this will eliminate the error messages it will conceal any future updates that Dropbox makes in the future because it will "hardwire" the updates to ONLY look at the version for Fedora v31.
  If you use this, make certain to occasionally check the Fedora Dropbox repo at http://linux.dropbox.com/fedora for newer versions.