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#30843 - [virtualbox-source] - does not allow for custom kernel headers anymore

Attached to Project: Community Packages
Opened by John (graysky) - Wednesday, 25 July 2012, 05:15 GMT
Last edited by Sébastien Luttringer (seblu) - Wednesday, 25 July 2012, 13:33 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Sébastien Luttringer (seblu)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: Recent update of this package tries to pull down 'linux-headers' on systems that run custom kernels. This is a change in behavior as previous version allowed for linux-xxx-headers that are installed to work so long as the user installs both this package and the main community/virtualbox package at the same time.

Additional info:
* package version(s) 4.1.18-3
This task depends upon

Closed by  Sébastien Luttringer (seblu)
Wednesday, 25 July 2012, 13:33 GMT
Reason for closing:  Not a bug
Comment by Sébastien Luttringer (seblu) - Wednesday, 25 July 2012, 13:28 GMT
linux-xxx-headers are still optional. There is no change in this way.

Your issue probably come from dkms, which needs linux-headers. You custom kernel must provide linux-headers.

Loading...