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
Task Type Bug Report
Category General
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version git
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Summary 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.
   makepkg-gpghome.patch (1.8 KiB)
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.
Comment by KaiSforza (KaiSforza) - Wednesday, 13 February 2013, 06:30 GMT
See, or you could just fix the PKGBUILD to not be horrible. You shouldn't be exporting HOME (or anything) in a PKGBUILD if you don't want to use it for the entire run of makepkg.

(Example: http://ix.io/4of )
Comment by Christian Hesse (eworm) - Wednesday, 13 February 2013, 06:52 GMT
Agreed about the horrible PKGBUILD, but it is not my one. Took me some time to find the culprit...

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.

Loading...