fter intentionally waiting two weeks I upgraded my Fedora Server to 44, and now the Dropbox entry is having some issues when updating with dnf:
Dropbox Repository 100% | 261.0 B/s | 1.6 KiB | 00m06s
>>> Status code: 404 for http://linux.dropbox.com/fedora/44/repodata/10d12831b54877b6e7bbd4635047873
0504c7088ee75ef593750ae1c357c140b-primary.xml.zst (IP: 3.165.206.96) - http://linux.dropbox.com/fedo
ra/44/repodata/10d12831b54877b6e7bbd46350478730504c7088ee75ef593750ae1c357c140b-primary.xml.zst
>>> Status code: 404 for http://linux.dropbox.com/fedora/44/repodata/10d12831b54877b6e7bbd4635047873
0504c7088ee75ef593750ae1c357c140b-primary.xml.zst (IP: 3.165.206.96) - http://linux.dropbox.com/fedo
ra/44/repodata/10d12831b54877b6e7bbd46350478730504c7088ee75ef593750ae1c357c140b-primary.xml.zst
>>> Status code: 404 for http://linux.dropbox.com/fedora/44/repodata/10d12831b54877b6e7bbd4635047873
0504c7088ee75ef593750ae1c357c140b-primary.xml.zst (IP: 3.165.206.96) - http://linux.dropbox.com/fedo
ra/44/repodata/10d12831b54877b6e7bbd46350478730504c7088ee75ef593750ae1c357c140b-primary.xml.zst
>>> Status code: 404 for http://linux.dropbox.com/fedora/44/repodata/10d12831b54877b6e7bbd4635047873
0504c7088ee75ef593750ae1c357c140b-primary.xml.zst (IP: 3.165.206.96) - http://linux.dropbox.com/fedo
ra/44/repodata/10d12831b54877b6e7bbd46350478730504c7088ee75ef593750ae1c357c140b-primary.xml.zst
>>> No more mirrors to try - All mirrors were already tried without success
I've checked, the structure exists but 10d12831b54877b6e7bbd46350478730504c7088ee75ef593750ae1c357c140b doesn't match the files that are actually there. I've tried reinstalling and cleaning cache and such. Right now I'm running the most recent Dropbox version via RPM, which makes dnf want to "upgrade" it to an older version:
Upgrading:
nautilus-dropbox x86_64 1:2026.01.15-1.fc44 rpmfusion-nonfree 47.9 KiB
replacing nautilus-dropbox x86_64 0:2026.05.06-1.fc44 @commandline 142.7 KiB
Installing dependencies:
dropbox x86_64 1:2026.01.15-1.fc44 rpmfusion-nonfree 135.6 KiB
Is there anything on my end to do to fix this or is this broken somewhere else?