Opened 7 years ago
Closed 7 years ago
#17722 closed defect (fixed)
Infrastructure: No rpms available for F28 -> fixed
Reported by: | F | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 5.2.10 |
Keywords: | Cc: | ||
Guest type: | all | Host type: | Linux |
Description
http://download.virtualbox.org/virtualbox/rpm/fedora/ is missing a directory for F28. Fedora 28 has been released and users with the virtualbox repo [1] enabled, will be point there.
[1]: http://download.virtualbox.org/virtualbox/rpm/fedora/virtualbox.repo
Change History (12)
comment:3 by , 7 years ago
Didier, unless you posted just to Cc: yourself (a noble cause!), please read the comment right above yours (by yours truly).
comment:4 by , 7 years ago
@socratis: whatever the version is, just read the title of the bug report, there are no rpms for Fedora 28 (I meant 5.2.12)
.... simple subtraction ....
comment:5 by , 7 years ago
@heis2201: There's no "whatever the version". When you posted the ticket, the dates were not making sense. The ticket was not making sense. Now it might.
Simple math (may involve addition)...
comment:6 by , 7 years ago
@heis2201
Besides the jokes (in good spirit), there are no specific Fedora 27 packages, they point to the Fedora 26 ones. Maybe it's a matter of simply updating the wiki to state:
instead of simply
i.e. you can use the F26 packages? Maybe the F26 packages are "good enough" or simply "appropriate" for a F28 host?
comment:7 by , 7 years ago
@socratis
In my personal, as long as virtualbox provides a repository, it should provide something. I am aware that the F27 repo points to the F26 builds. The solution could be as simple as pointing F28 to F26 as well. That is still way better than a non-existing repository.
My experience of the recent past: The rpm packages built for F26 worked just fine for F27. Since my upgrade to F28 (having the .repo manually pointed to F27, meaning I am using the 5.2.12 packages built for F26), I experience some problems [*] for my Win7 guest. However, I have no idea what is causing the problem - there is many variables.
[*]:
- guest is causing requesting a lot of CPU
- guest is causing the host to run somewhat hot
- guest is freezing frequently (host is unaffected)
- guest sometimes behaves as if SHIFT key would be pressed (and hold down).
comment:8 by , 7 years ago
heis2201,
I'd suggest to head to the VirtualBox forums for this kind of questions. The reason? More eyes, more testimonies, we can see them in a bigger picture.
For example, your Shift key question? I got two more threads in the forums, plus a ticket <1>. It is better "synced" in the forums and if it turns out to be an issue worth of a ticket, then go for it.
Not sure if you should open a thread in the VirtualBox on Linux Hosts section of the forums, or the Windows Guests section of the forums. Do you have these issues with other guests as well?
As for your other questions, 1 could cause 2 and/or 3. The question is what's causing 1, the high CPU in the guest. Maybe Windows updates? Again, I'd suggest the forums, this ticket is starting to deviate from its title... ;)
<1>:
comment:9 by , 7 years ago
Thanks for hint! Sorry for getting off-topic here - I am aware end-user problems and workarounds are better discussed in a forum.
The initial bug report was more a reminder that it is time to create a F28 directory on the server and copy that .fc26 build in there.
Take care!
comment:10 by , 7 years ago
Summary: | Infrastructure: No rpms available for F28 → Infrastructure: No rpms available for F28 -> fixed |
---|
Should be fixed now.
comment:12 by , 7 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
2018-04-17: 5.2.10 VirtualBox (latest) was released.
2018-05-01: Fedora 28 was released.
As you can see by simple subtraction, the latest VirtualBox predates F28 by two weeks. I'm not even sure even if F28 is supported as a host in 5.2.10 at this point.
I know that the 5.2.10 didn't support F28 as a guest and you have to download the test builds to make it sing.
I wouldn't expect a 5.2.10 release for F28. I'd wait for the next official 5.2.12 release, if it makes the cut...