On Tue, Feb 27, 2018 at 03:44:07PM +0100, Eli Schwartz via arch-projects wrote:
> On 02/27/2018 05:41 AM, Emiel Wiedijk via arch-projects wrote:
> > Correct, but makepkg --verifysource is run with sudo -u $myuser, and sudo
> > resets the environment. And the code that copies ~/.gnupg to the chroot
On 02/27/2018 05:41 AM, Emiel Wiedijk via arch-projects wrote:
> Correct, but makepkg --verifysource is run with sudo -u $myuser, and sudo
> resets the environment. And the code that copies ~/.gnupg to the chroot
> apparantly hasn't been removed yet (as of
>
> On 02/26/2018 02:03 PM, Emiel Wiedijk via arch-projects wrote:
>
> > Previously, makechrootpkg hardcoded ~/.gnupg. Therefore, if a user
> >
> > uses a custom GPG home directory, the siganture checking would fail.
> >
> > Now makechrootpkg uses $GNUPGHOME, with a fallback to ~/.gnupg.
>
>
On 02/26/2018 02:03 PM, Emiel Wiedijk via arch-projects wrote:
> Previously, makechrootpkg hardcoded ~/.gnupg. Therefore, if a user
> uses a custom GPG home directory, the siganture checking would fail.
> Now makechrootpkg uses $GNUPGHOME, with a fallback to ~/.gnupg.
There is no signature
Previously, makechrootpkg hardcoded ~/.gnupg. Therefore, if a user
uses a custom GPG home directory, the siganture checking would fail.
Now makechrootpkg uses $GNUPGHOME, with a fallback to ~/.gnupg.
Signed-off-by: Emiel Wiedijk
---
makechrootpkg.in | 12 +++-
1 file