| Summary: | F33: Uninstallation of Virtual Box does not have proper auto-remove functionality; leaves behind a tainted kernel in its wake. | ||
|---|---|---|---|
| Product: | Fedora | Reporter: | Andrew Thurman <ajtbecool> |
| Component: | VirtualBox | Assignee: | Sérgio Basto <sergio> |
| Status: | REOPENED --- | ||
| Severity: | enhancement | CC: | leigh123linux, xsaipc0d |
| Priority: | P1 | ||
| Version: | unspecified | ||
| Hardware: | x86_64 | ||
| OS: | GNU/Linux | ||
| namespace: | |||
|
Description
Andrew Thurman
2020-10-14 22:42:38 CEST
dnf remove VirtualBox-server removes all kmods Removing: VirtualBox-server x86_64 Removing dependent packages: VirtualBox x86_64 VirtualBox-webservice x86_64 akmod-VirtualBox x86_64 kmod-VirtualBox-5.8.12-100.fc31.x86_64 x86_64 kmod-VirtualBox-5.8.13-100.fc31.x86_64 x86_64 kmod-VirtualBox-5.9.0-36.fc34.x86_64 x86_64 Then I feel like `VirtualBox` shouldn't be the AppStream package, but rather `VirtualBox-server`. If you don't have proper dependency management in GUIs, you shouldn't include the AppStream metadata. I'm not a package mainatiner so maybe I'm talking BS, but it just feels like what's best for the end user experience. VirtualBox is the Qt part (graphics), which of course needs the server package , but server package doesn't need the graphics package . I think VirtualBox-kmodsrc will stay behind, maybe there is a need to enforce a dependency so it get removed if uneeded also...
I would suggest to use something like: with fedora or rhel>7
%package kmodsrc
...
Requires: VirtualBox-server = %{evr} or VitualBox-guest = %{evr}
(to be tested)
it is not fixed |