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#61437 - [dkms] do not increment *-dkms packages' pkgrel if there is no patch/configuration change applied
Attached to Project:
Arch Linux
Opened by BrLi (brli) - Thursday, 17 January 2019, 04:17 GMT
Last edited by Doug Newgard (Scimmia) - Thursday, 17 January 2019, 04:43 GMT
Opened by BrLi (brli) - Thursday, 17 January 2019, 04:17 GMT
Last edited by Doug Newgard (Scimmia) - Thursday, 17 January 2019, 04:43 GMT
|
DetailsDescription:
the *-dkms packages hold only the source for dkms to compile modules, they shouldn't have kernel dependencies thus no need to upgrade every time their binary counterparts get rebuild for new kernel release. you should give a fixed pkgrel at the package() part of the *-dkms package so that users won't re-downloaded a pkgerl++ package every time where the new package is identical to the old one, where dkms hook is triggered nonetheless. especially we know they haven't receive upgrade for long, such as acpi_call, vhba-module etc. Additional info: * package version(s) not specific * config and/or log files etc. Steps to reproduce: |
This task depends upon
Closed by Doug Newgard (Scimmia)
Thursday, 17 January 2019, 04:43 GMT
Reason for closing: Won't implement
Additional comments about closing: split packages can't currently work that way
Thursday, 17 January 2019, 04:43 GMT
Reason for closing: Won't implement
Additional comments about closing: split packages can't currently work that way