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!
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!
FS#51291 - acpi_call package arbitrarily requires 'linux<4.8'
Attached to Project:
Community Packages
Opened by Tronje Krabbe (tronje) - Saturday, 08 October 2016, 20:46 GMT
Last edited by Dave Reisner (falconindy) - Saturday, 08 October 2016, 20:52 GMT
Opened by Tronje Krabbe (tronje) - Saturday, 08 October 2016, 20:46 GMT
Last edited by Dave Reisner (falconindy) - Saturday, 08 October 2016, 20:52 GMT
|
DetailsDescription:
Additional info: * Package versions: ** acpi_call 1.1.0-49 ** linux >= 4.8 * Since acpi_call hasn't been updated in about 3 years (see here: [0]), it seems arbitrary that it has this dependency. Exact error message: $ sudo pacman -Syu [...] error: failed to prepare transaction (could not satisfy dependencies) :: acpi_call: installing linux (4.8.1-1) breaks dependency 'linux<4.8' Steps to reproduce: Try to update to kernel version >= 4.8 with community package 'acpi_call' installed. Suggested solution: Maybe remove this specific dependency in the [testing] repository for now? [0] acpi_call repository on github: https://github.com/mkottman/acpi_call |
This task depends upon
Closed by Dave Reisner (falconindy)
Saturday, 08 October 2016, 20:52 GMT
Reason for closing: Not a bug
Additional comments about closing: testing is all or none.
Saturday, 08 October 2016, 20:52 GMT
Reason for closing: Not a bug
Additional comments about closing: testing is all or none.
Comment by Dave Reisner (falconindy) -
Saturday, 08 October 2016, 20:49 GMT
The dependency is correct. Seems like you have [testing] enabled without [community-testing]. That's what needs fixing here.
Comment by Tronje Krabbe (tronje) -
Saturday, 08 October 2016, 20:51 GMT
Oh, yes, you are correct. My bad, sorry; thanks for the quick response. I can update now :)