Mailing-List: contact commits-help@subversion.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@subversion.apache.org
Message-Id: <1498978397.1983144.1027858848.6F4FBB12@webmail.messagingengine.com>
From: Daniel Shahaf <danielsh@apache.org>
To: dev@subversion.apache.org
Cc: commits@subversion.apache.org
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"
Date: Sun, 02 Jul 2017 06:53:17 +0000
In-Reply-To: <20170702064538.33E8F3A167A@svn01-us-west.apache.org>
Subject: release.py += gpg2 support (was: svn commit: r1800548 -
 /subversion/trunk/tools/dist/release.py)
References: <20170702064538.33E8F3A167A@svn01-us-west.apache.org>
archived-at: Sun, 02 Jul 2017 06:53:27 -0000

danielsh@apache.org wrote on Sun, 02 Jul 2017 06:45 +0000:
> release.py: When parsing signatures (for check-sigs and write-announcemen=
t),
> use the machine-readable output format.  This adds support for ${PATH}/gpg
> being gpg2; up to now, it was assumed to be gpg1.
>=20
> The output of release.py is unchanged.

I tested this patch with both gpg1 and gpg2, and "It works on my
machine", but some testing would be good.  Could someone run

    release.py check-sigs --target=3D/working/copy/of/https://svn.apache.or=
g/repos/dist/dev/subversion 1.9.6

and ensure it works?  (I tested on Debian Stretch already)

Thanks.

Daniel
(if you get an error about key DB27E997429AF20C, just refresh my key
with =C2=ABgpg --keyserver pgp.mit.edu --refresh-keys E96646BE08C0AF0AA0F90=
788A5FEEE3AC7937444=C2=BB)