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#13727 - [makepkg] VCS packages, makedepends and output
Attached to Project:
Pacman
Opened by Allan McRae (Allan) - Monday, 09 March 2009, 23:48 GMT
Last edited by Allan McRae (Allan) - Friday, 10 August 2012, 04:56 GMT
Opened by Allan McRae (Allan) - Monday, 09 March 2009, 23:48 GMT
Last edited by Allan McRae (Allan) - Friday, 10 August 2012, 04:56 GMT
|
DetailsSummary and Info:
devel_update() can get run before the VCS tool is installed as a makedep. Currently, the lack of VCS tool results in an immediate exit from devel_update(). This results in some interesting output: ==> Making package: notify-sharp-svn 3009-2 i686 (Mon Mar 9 08:23:02 UTC 2009) ... ==> Installing missing dependencies... (subversion) ==> Entering fakeroot environment... ==> Determining latest svn revision... -> Version found: 3032 (note the different version there and how --forcever does not seem to have been used/work) ... ==> Finished making: notify-sharp-svn 3009-2 i686 (Mon Mar 9 08:25:36 UTC 2009) Maybe this can be improved somehow... |
This task depends upon
Closed by Allan McRae (Allan)
Friday, 10 August 2012, 04:56 GMT
Reason for closing: Implemented
Additional comments about closing: https://projects.archlinux.org/pacman.gi t/commit/?id=024bc44a
Friday, 10 August 2012, 04:56 GMT
Reason for closing: Implemented
Additional comments about closing: https://projects.archlinux.org/pacman.gi t/commit/?id=024bc44a
Well now that I've looked, that function doesn't do at all what I expected. Maybe we need to be smart enough in devel_check() that we actually have a return code, and then check that in the main flow of makepkg?