#21423 new defect
No repo for Fedora 37
回報者: | Timothe Litt | 負責人: | |
---|---|---|---|
元件: | other | 版本: | VirtualBox-7.0.6 |
關鍵字: | Fedora-37 Repo | 副本: | |
Guest type: | all | Host type: | Linux |
描述
I just updated my Fedora (x86_64) host to release 37.
The DNF upgrade complained of a 404 for the VirtualBox repo.
Sure enough, http://download.virtualbox.org/virtualbox/rpm/fedora/ does not have a '37' child.
Can this be fixed?
Thanks.
更動歷史 (3)
comment:2 2 年 前 由 編輯
Thanks. What I actually did was remove virtualbox from dnf, and downloaded the F36 RPM from https://www.alldomusa.eu.org/wiki/Linux_Downloads
Not as convenient, but this isn't the first time that the repo hasn't been updated, and since I get e-mail when there's a new release, it isn't as bad as it seems... It also makes it somewhat easier to keep everything else up-to-date since I schedule Virtualbox updates around times when I can shutdown my VMs..
I don't understand why the virtualbox release process doesn't automatically create the softlink - as the download page says: "All distributions (built on EL6 and therefore not requiring recent system libraries)" So it would seem to be an exceptional case if a Fedora release ever requires a unique repo - and probably a Fedora compatibility bug.
But, wishes aren't fishes, so it's the non-DNF route for now.
comment:3 2 年 前 由 編輯
@tlhackque
you could install VirtualBox from rpmfusion. They are up-to-date with their repos and you get it packaged the way Fedora recommends packaging (akmods instead of dkms for the vbox kernel module).
also, that way you get updates the dnf way.
Fedora 37 is now 3 months old, and this really should have been fixed long time ago :-(
ESPECIALLY because the Fedora 36 build works perfectly well on Fedora 37.
tlhackque: You can fix this temporary by making this change to your repo file:
#baseurl=https://download.virtualbox.org/virtualbox/rpm/fedora/$releasever/$basearch baseurl=https://download.virtualbox.org/virtualbox/rpm/fedora/36/$basearch