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#69693 - [lm_sensors] Utter nonsense pkgver
Attached to Project:
Arch Linux
Opened by Magnus Boman (katt) - Thursday, 18 February 2021, 14:46 GMT
Last edited by Laurent Carlier (lordheavy) - Thursday, 18 February 2021, 15:27 GMT
Opened by Magnus Boman (katt) - Thursday, 18 February 2021, 14:46 GMT
Last edited by Laurent Carlier (lordheavy) - Thursday, 18 February 2021, 15:27 GMT
|
DetailsDescription:
lm_sensors was just updated from 3.6.0 to 3.6.0.r5313, there is *no* way there were 5313 commits since the last release. Not only that but the maintainer has directly just written `3.6.0` in the pkgver() and counting from the first commit. Do official packages not have to conform to any sort of standards? I checked and using the examples in the VCS package guidelines works absolutely brilliantly. I am aware this may not be a critical bug, but it is absolutely an eyesore. katt@main ~/lm-sensors (master) ยป git describe --long --tags | sed 's/V//;s/\([^-]*-g\)/r\1/;s/-/./g' 3.6.0.r41.g31d1f125 |
This task depends upon
Closed by Laurent Carlier (lordheavy)
Thursday, 18 February 2021, 15:27 GMT
Reason for closing: Fixed
Additional comments about closing: lm_sensors-1:3.6.0.r41.g31d1f125
Thursday, 18 February 2021, 15:27 GMT
Reason for closing: Fixed
Additional comments about closing: lm_sensors-1:3.6.0.r41.g31d1f125
Comment by Laurent Carlier (lordheavy) -
Thursday, 18 February 2021, 15:23 GMT
doh, should be fixed soon