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#33837 - [makepkg] signing fails with exported HOME
Attached to Project:
Pacman
Opened by Christian Hesse (eworm) - Wednesday, 13 February 2013, 06:15 GMT
Last edited by Allan McRae (Allan) - Wednesday, 13 September 2017, 03:45 GMT
Opened by Christian Hesse (eworm) - Wednesday, 13 February 2013, 06:15 GMT
Last edited by Allan McRae (Allan) - Wednesday, 13 September 2017, 03:45 GMT
|
DetailsSummary and Info:
If environment variable HOME is exportet inside PKGBUILD gpg fails signing the package as it does not find it keyrings. My proposed fix is to call gpg with --homedir. Or is there anything more we can screw up and break which needs a proper fix? Steps to Reproduce: Inside PKGBUILD export HOME, then try to build the package with 'makepkg --sign'. See ruby-json_pure (https://aur.archlinux.org/packages/ruby-json_pure/) for an example. |
This task depends upon
Closed by Allan McRae (Allan)
Wednesday, 13 September 2017, 03:45 GMT
Reason for closing: Not a bug
Additional comments about closing: There is a limit of which bad things in PKGBUILDs can be covered by makepkg.
Wednesday, 13 September 2017, 03:45 GMT
Reason for closing: Not a bug
Additional comments about closing: There is a limit of which bad things in PKGBUILDs can be covered by makepkg.
makepkg-gpghome.patch
(Example: http://ix.io/4of )
I am fine if you say this is not supported, though I think in this case we need some more verbose output. The message "Failed to sign package file." really did not help a lot.