FS#70809 - [virtualbox-guest-utils] conflicting guest-utils when dkms package is installed
Attached to Project:
Community Packages
Opened by Philip Müller (philm) - Wednesday, 12 May 2021, 08:31 GMT
Last edited by Toolybird (Toolybird) - Sunday, 16 April 2023, 03:01 GMT
Opened by Philip Müller (philm) - Wednesday, 12 May 2021, 08:31 GMT
Last edited by Toolybird (Toolybird) - Sunday, 16 April 2023, 03:01 GMT
|
Details
Description:
Having virtualbox-guest-dkms installed will result in this error: :: Starting full system upgrade... :: Replace virtualbox-guest-dkms with community/virtualbox-guest-utils? [Y/n] :: Replace virtualbox-guest-dkms with community/virtualbox-guest-utils-nox? [Y/n] resolving dependencies... looking for conflicting packages... error: unresolvable package conflicts detected error: failed to prepare transaction (conflicting dependencies) :: virtualbox-guest-utils and virtualbox-guest-utils-nox are in conflict Wouldn't it not been better to have a package like virtualbox having that replace, and not possible conflicting packages? Additional info: * package version(s): virtualbox-guest-dkms 6.1.22-1 * not yet installed versions (s): virtualbox-guest-utils 6.1.22-2 virtualbox-guest-utils-nox 6.1.22-2 Steps to reproduce: Try to update when virtualbox-guest-dkms without virtualbox-guest-utils or virtualbox-guest-utils-nox is installed. |
This task depends upon
Closed by Toolybird (Toolybird)
Sunday, 16 April 2023, 03:01 GMT
Reason for closing: None
Additional comments about closing: Enough time has passed, no longer relevant.
Sunday, 16 April 2023, 03:01 GMT
Reason for closing: None
Additional comments about closing: Enough time has passed, no longer relevant.
Not sure we can resolve this. This should work fine if you press 'n' for either of both, no? Or just remove package virtualbox-guest-dkms if you want neither of both.
Well, virtualbox is installed on the host, virualbox-guest-dkms is/was installed on the guest. Adding the replace there does not make sense.
Thinking about this again I think it's not a big issue - unless the above applied which is uncommon.
I am inclined to keep this as-is.