Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

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 Andreas Radke (AndyRTR) - Thursday, 13 May 2021, 08:44 GMT
Task Type Bug Report
Category Packages
Status Assigned
Assigned To Christian Hesse (eworm)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

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

Comment by Christian Hesse (eworm) - Wednesday, 12 May 2021, 09:24 GMT
Oh, damn...
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.
Comment by Philip Müller (philm) - Wednesday, 12 May 2021, 09:54 GMT
I don't know if a dummy package like virtualbox-guest-dkms-obsolete might fix it, with a notice to remove the package after all. Does virtualbox-guest-utils replace dkms or was it only added to remove that obsolete package?
Comment by Christian Hesse (eworm) - Wednesday, 12 May 2021, 10:35 GMT
It is just to remove the obsolete package. The modules are provided by upstream linux now.
Comment by Philip Müller (philm) - Wednesday, 12 May 2021, 16:04 GMT
Yep, not all older kernels support it, but with 5.10 and higher it is included. Would it make sense to include the replace not in the linux and linux-lts package? Installing any virtualbox-guest-utils is odd if it is not needed on your system.
Comment by Christian Hesse (eworm) - Thursday, 13 May 2021, 20:14 GMT
Well, what's really odd is that you have virtualbox-guest-dkms installed on a system that does not need it. ;)
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.

Loading...