Historical bug tracker for the Pacman package manager.
The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues
This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues
This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
FS#46800 - [makepkg] Always update pkgver with pkgver()
Attached to Project:
Pacman
Opened by Link Mauve (linkmauve) - Monday, 19 October 2015, 14:27 GMT
Last edited by Allan McRae (Allan) - Thursday, 31 December 2015, 10:09 GMT
Opened by Link Mauve (linkmauve) - Monday, 19 October 2015, 14:27 GMT
Last edited by Allan McRae (Allan) - Thursday, 31 December 2015, 10:09 GMT
|
DetailsDescription:
Sometimes the user updated the revision in src manually, in this case calling `makepkg -e` won’t run pkgver() to set the pkgver variable to the current version. Additional info: * package version(s) pacman 4.1.2-4 Steps to reproduce: - Get a development PKGBUILD - Run `makepkg -o` to clone the repository in src/ - Commit something there, to change the VCS revision - Run `makepkg -e` Expected result: The package created would have a pkgver corresponding to the actual source, instead of the one that got cloned at first. |
This task depends upon
Closed by Allan McRae (Allan)
Thursday, 31 December 2015, 10:09 GMT
Reason for closing: Fixed
Additional comments about closing: git commit 8454daa7
Thursday, 31 December 2015, 10:09 GMT
Reason for closing: Fixed
Additional comments about closing: git commit 8454daa7