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
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!
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.
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.
Hello! Same issue here! It is anoying. Package manager is always displaying that error that can be easily fixed!
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:00Errors 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
Come on Dropbox... how hard is it? Granted I know Fedora is not your main demographic but its going on 2 months.
Myself and 689 others would like to know if Dropbox is going to fix the Fedora 32 repo link? Its been 2 months.
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.
Still waiting a solution for this issue. Dropbox used to work flawless on Fedora until version 31.
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.)
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?
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.
bump
"Dropbox Repository 109 kB/s | 25 kB 00:00Errors 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 triedIgnoring repositories: Dropbox
Last metadata expiration check: 2:42:44 ago on Sun 05 Jul 2020 07:36:46 PM EDT."
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
SampleOriginal:
[Dropbox]name=Dropbox Repositorybaseurl=http://linux.dropbox.com/fedora/$releasever/gpgkey=http://linux.dropbox.com/fedora/rpm-public-key.asc
New:
[Dropbox]name=Dropbox Repositorybaseurl=http://linux.dropbox.com/fedora/31/gpgkey=http://linux.dropbox.com/fedora/rpm-public-key.asc
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
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
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
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!
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:
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:
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.
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!
Dropbox not having a Repo for Fedora 32 is not a specific user error. Its a complete failure on Dropbox's part.
These are workaround to dropbox not creating a symbolic link. Maybe Dropbox can't handle the additional storage space.
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...
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.
@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-to-Fedora/idi-p/436151Here 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.
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
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.
This "solution" has been written already many times. This is not a solution.
