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#34712 - problem with how makepkg handles svn PKGBUILDs
Attached to Project:
Pacman
Opened by U (Gusar) - Wednesday, 10 April 2013, 11:54 GMT
Last edited by Allan McRae (Allan) - Thursday, 11 April 2013, 04:21 GMT
Opened by U (Gusar) - Wednesday, 10 April 2013, 11:54 GMT
Last edited by Allan McRae (Allan) - Thursday, 11 April 2013, 04:21 GMT
|
DetailsI wanted to convert the tigervnc-svn PKGBUILD in AUR to the new VCS handling in pacman-4.1. The problem is, the upstream tigervnc source has a README.txt file in it. But when makepkg runs
svn checkout --config-dir "$dir" "$url" "$dir" the README.txt in the checkout is from subversion, not tigervnc (subversion creates a few files in config-dir, among them README.txt). Later when the source is exported, there's no README.txt in the export. This causes package creation to fail with CMake Error at cmake_install.cmake:56 (FILE): file INSTALL cannot find "/var/abs/local/tigervnc-svn/src/tigervnc/README.txt". I suggest using something other than "$dir" for --config-dir |
This task depends upon
Closed by Allan McRae (Allan)
Thursday, 11 April 2013, 04:21 GMT
Reason for closing: Duplicate
Additional comments about closing: FS#34636
Thursday, 11 April 2013, 04:21 GMT
Reason for closing: Duplicate
Additional comments about closing: