FS#71658 - [ctags] Inconsistent pkgver() generation
Attached to Project:
Arch Linux
Opened by Felix Yan (felixonmars) - Thursday, 29 July 2021, 18:53 GMT
Last edited by Buggy McBugFace (bugbot) - Saturday, 25 November 2023, 20:16 GMT
Opened by Felix Yan (felixonmars) - Thursday, 29 July 2021, 18:53 GMT
Last edited by Buggy McBugFace (bugbot) - Saturday, 25 November 2023, 20:16 GMT
|
Details
Description:
The PKGBUILD generates a different pkgver in default setup, not sure about the reason, though. Current repository version: ctags 1:r20210106+g08b1c490-1 $ extra-x86_64-build generates: ctags 1:r20210106+g08b1c490c-1 |
This task depends upon
Closed by Buggy McBugFace (bugbot)
Saturday, 25 November 2023, 20:16 GMT
Reason for closing: Moved
Additional comments about closing: https://gitlab.archlinux.org/archlinux/p ackaging/packages/ctags/issues/2
Saturday, 25 November 2023, 20:16 GMT
Reason for closing: Moved
Additional comments about closing: https://gitlab.archlinux.org/archlinux/p ackaging/packages/ctags/issues/2
Comment by
Evangelos Foutras (foutrelis) -
Friday, 30 July 2021, 08:20 GMT
Comment by
Felix Yan (felixonmars) - Friday,
30 July 2021, 08:32 GMT
Comment by
Buggy McBugFace (bugbot) - Tuesday,
08 August 2023, 19:11 GMT
More commits in the upstream repo probably.
Should we somehow set it to a constant and update the guidelines?
This is an automated comment as this bug is open for more then 2
years. Please reply if you still experience this bug otherwise
this issue will be closed after 1 month.