After installing dropbox, using the installer downloaded from the Dropbox site, Discover seems to have added a Dropbox repository entry. And every few seconds it throws me this error:
cannot update repo 'Dropbox': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried; Last error: Status code: 404 for http://linux.dropbox.com/fedora/42/repodata/repomd.xml (IP: 18.64.236.97)
I was able to unclick the ‘Dropbox’ repository in Discover to stop this behavior. Now I’d really like to remove that repository entry entirely from Discover. But for the life of me I can’t find a way to do that. Where the heck are repo entries for Discover kept so that I can remove this?
Dropbox installed perfectly and is running just fine. It’s only Discover that is having an issue.
And, of course, it’d be nice to understand why this happened in the first place. Using Dropbox’s .rmp file that I downloaded I installed it using DNF from the command line. But sudo dnf repolist all does not show any repos configured for DNF. So apparently DNF hasn’t tried to add a repo for Dropbox.
I just did a fresh install of fedora-42, KDE edition (obviously). While I have been on fedora-KDE for some 7-8 years now this is the first time I’ve actually used Discover as I noticed that dnfdragora was not longer part of the install. So not a newbie to KDE, but am a newbie with Discover.
Ok - I figured it out. When I listed the repos DNF knew about I left off the two hyphens in front of the all flag. So then executing the command correctly:
sudo dnf repolist --all
I do see that DNF probably did add the dropbox repo.
So I deleted /etc/yum.repos.d/dropbox.repo and all is now well.
1 Like
If you want to know the reason why it didn’t work, it’s because the toplevel dropbox repo doesn’t have a “42” subfolder yet as you can see here:
Dropbox Fedora top level
The “repo” file for the dropbox probably referenced the “$releasever” dnf built-in variable which on your system resolves to “42”. When they get around to adding the
https://linux.dropbox.com/fedora/42
it would finally work.
1 Like
Thanks for the explanation. I remember back in the Fedora 30s era that that happened all the time. Then it seemed like Dropbox wasn’t even in the repos anywhere for a while and I would install it ‘manually.’ But clearly my memory wasn’t good enough to remember that that could have been the issue.
Of course, one could argue the nature of the error message doesn’t help either, lol
When you see 404 error on network related things, the idea is equivalent to “file not found”
BTW, one option you might have would be to hardcode the dropbox repo file to replace the $releasever to 41 that would let you install the dropbox package from 41. But even that one has packages from fc39… maybe those are too old and would have library problems