From: Michael J Gruber <git@drmicha.warpmail.net>
To: Christian Hesse <mail@eworm.de>, Junio C Hamano <gitster@pobox.com>
Cc: "Torsten Bögershausen" <tboegi@web.de>, git@vger.kernel.org
Subject: Re: [PATCH 1/1] skip RFC1991 tests with gnupg 2.1.x
Date: Fri, 12 Dec 2014 17:00:41 +0100 [thread overview]
Message-ID: <548B1129.80202@drmicha.warpmail.net> (raw)
In-Reply-To: <20141212105444.50adca35@leda.localdomain>
Christian Hesse schrieb am 12.12.2014 um 10:54:
> Christian Hesse <mail@eworm.de> on Fri, 2014/12/12 09:35:
>> Junio C Hamano <gitster@pobox.com> on Thu, 2014/12/11 15:10:
>>> Christian Hesse <mail@eworm.de> writes:
>>>
>>>> However... Even if GnuPG 2.2.x (or whatever future release) will become
>>>> next stable: It will not reintroduce support for rfc1991.
>>>
>>> How certain are we about the deprecation?
>>
>> The sixth beta of GnuPG [0] had this change:
>>
>> * gpg: Removed the option --pgp2 and --rfc1991 and the ability to
>> create PGP-2 compatible messages.
>
> This is the corresponding commit:
>
> http://git.gnupg.org/cgi-bin/gitweb.cgi?p=gnupg.git;a=commit;h=2b8d8369d59249b89526c18c5ac276e6445dc35e
>
So, in fact, gpg2.1 removes support for creating pgp2 (rfc1991)
signatures only. That is: We could put an armor exported signature
into our test suite, test verification against that signature,
and restrict the test for creation of that signature by gpg version (or
skip it completely).
Michael
prev parent reply other threads:[~2014-12-12 16:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-11 9:30 [PATCH 1/1] skip RFC1991 tests with gnupg 2.1.x Christian Hesse
2014-12-11 15:32 ` Torsten Bögershausen
2014-12-11 16:54 ` Michael J Gruber
2014-12-11 22:44 ` Christian Hesse
2014-12-11 23:10 ` Junio C Hamano
2014-12-12 8:35 ` Christian Hesse
2014-12-12 9:54 ` Christian Hesse
2014-12-12 16:00 ` Michael J Gruber [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=548B1129.80202@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=mail@eworm.de \
--cc=tboegi@web.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).