All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Lehtonen <markus.lehtonen@linux.intel.com>
To: akuster808 <akuster808@gmail.com>,
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/3] Fix rpm signing with GPG v2.1
Date: Fri, 24 Feb 2017 09:31:54 +0200	[thread overview]
Message-ID: <7AB8ADC0-CEBA-4A5F-A2BF-4B62854EB9AA@linux.intel.com> (raw)
In-Reply-To: <9bbd49a0-b838-4342-43df-2bf3276c45ca@gmail.com>

On 23/02/2017, 17.58, "akuster808" <akuster808@gmail.com> wrote:

    Markus,
    
    
    On 02/23/2017 02:24 AM, Markus Lehtonen wrote:
    > This patchset makes signing work with all versions of GPG.  Previously, rpm
    > package signing in oe-core was not working with GPG v2.1 (which is becoming
    > more widespread). This was caused by a change in passphrase dialogue handling
    > of GPG.
    
    Off hand, do you know if Morty would benefit from this?

Yes it would. Same problem with GPG 2.1 there
  - Markus





  reply	other threads:[~2017-02-24  7:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-23 10:24 [PATCH 0/3] Fix rpm signing with GPG v2.1 Markus Lehtonen
2017-02-23 10:24 ` [PATCH 1/3] rpm: support customizing gpg command line Markus Lehtonen
2017-02-23 10:24 ` [PATCH 2/3] lib/oe/gpg_sign: make gpg version a property of the signer Markus Lehtonen
2017-02-23 10:24 ` [PATCH 3/3] lib/oe/gpg_sign: fix rpm signing with gpg > 2.1 Markus Lehtonen
2017-02-23 15:58 ` [PATCH 0/3] Fix rpm signing with GPG v2.1 akuster808
2017-02-24  7:31   ` Markus Lehtonen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-02-23 10:22 Markus Lehtonen
2017-02-23 15:48 ` Christopher Larson

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=7AB8ADC0-CEBA-4A5F-A2BF-4B62854EB9AA@linux.intel.com \
    --to=markus.lehtonen@linux.intel.com \
    --cc=akuster808@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.