[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH 1/1] gnu: gnupg: Update to 2.1.16.
From: |
Leo Famulari |
Subject: |
Re: [PATCH 1/1] gnu: gnupg: Update to 2.1.16. |
Date: |
Sun, 20 Nov 2016 00:56:06 -0500 |
User-agent: |
Mutt/1.7.1 (2016-10-04) |
On Sun, Nov 20, 2016 at 12:31:30AM +0100, Mathieu Lirzin wrote:
> Hi,
>
> Leo Famulari <address@hidden> writes:
>
> > On Sun, Nov 20, 2016 at 12:41:31AM +0200, Efraim Flashner wrote:
> >> Looks like they forgot to bootstrap it then.
> >
> > Because I altered two Makefile.am files in the 'patch-paths' phase, I
> > had to re-do the bootstrap in order for the Makefiles to be regenerated.
> >
> > I'm not an expert on Autotools. Does anyone know if there is a better
> > way?
>
> I have not tried but unless some weird issue, I think you can safely
> replace "/bin/pwd" directly in the generated Makefile(s) instead of the
> Makefile.am sources.
>
> This should fix the Autotools dependency and the warning.
I read a bit more and learned about $GNUPGHOME. `/bin/pwd/` is only
invoked if that variable is unset, so I set it in the test suite, and
it works for me.
And the problem with $HOME not existing, worked around by the set-home
phase, was apparently fixed in:
https://git.gnupg.org/cgi-bin/gitweb.cgi?p=gnupg.git;a=commitdiff;h=38d369de13acb95208a0ed8d1cf82ac19173688f;hp=fde9fa81d3d3b25a929b532cc1960d9d9f454a0c
Which I learned about here:
https://anonscm.debian.org/git/pkg-gnupg/gnupg2.git/commit/?id=bbcd4f60e834c79454d1eaf4adf052f8ff545f99
Pushed as 764c5662211793d381b6c4a85f6a1ef4ad353c3f