From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH 0/5] gnupg: Update to 2.2.27
Date: Sun, 04 Apr 2021 13:10:10 +0200 [thread overview]
Message-ID: <20210404111015.66155-1-adolf.belka@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2181 bytes --]
This is the patch series for the update of gnupg from the legacy 1.4
branch to the LTS 2.2 branch.
Required for build and use are
libassuan New requirement for 2.2 branch - change from addon to Core program
libksba New requirement for 2.2 branch - new install
npth New requirement for 2.2 branch - new install
pinentry not required for build. Is required for some uses of gnupg such
as when providing passwords. This does not apply the the IPFire use cases.
Trying to update gpgme with the old 1.4 branch gnupg resulted in various
fails. Was looking for files that were not present.
Updating gpgme with 2.2 branch of gnupg was successful.
The iso created from the build of all the changes from this patch series
was installed in my vm testbed. Keys successfully imported. Package lists
successfully read and put into pakfire wui page. Several addons installed
successfully. Packages had signatures successfully verified.
My testing indicates that gnupg 2.2 branch is successfully working in
IPFire in place of the 1.4 branch
Adolf Belka (5):
gnupg: Update to 2.2.27
libassuan: Convert from addon to core program
libksba: required for gnupg 2.2 series
npth: required for gnupg 2.2 series
gpgme: Update to 1.15.1
config/rootfiles/common/gnupg | 107 ++++++++++--
.../rootfiles/{packages => common}/libassuan | 0
config/rootfiles/common/libksba | 9 +
config/rootfiles/common/npth | 7 +
config/rootfiles/packages/gpgme | 162 +++++++++++++++++-
lfs/gnupg | 4 +-
lfs/gpgme | 6 +-
lfs/libassuan | 6 -
lfs/libksba | 79 +++++++++
lfs/npth | 79 +++++++++
make.sh | 2 +
11 files changed, 434 insertions(+), 27 deletions(-)
rename config/rootfiles/{packages => common}/libassuan (100%)
create mode 100644 config/rootfiles/common/libksba
create mode 100644 config/rootfiles/common/npth
create mode 100644 lfs/libksba
create mode 100644 lfs/npth
--
2.31.1
next reply other threads:[~2021-04-04 11:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-04 11:10 Adolf Belka [this message]
2021-04-04 11:10 ` [PATCH 1/5] " Adolf Belka
2021-04-04 11:10 ` [PATCH 2/5] libassuan: Convert from addon to core program Adolf Belka
2021-04-04 11:10 ` [PATCH 3/5] libksba: required for gnupg 2.2 series Adolf Belka
2021-04-04 11:10 ` [PATCH 4/5] npth: " Adolf Belka
2021-04-04 11:10 ` [PATCH 5/5] gpgme: Update to 1.15.1 Adolf Belka
2021-04-06 10:38 ` [PATCH 0/5] gnupg: Update to 2.2.27 Michael Tremer
2021-04-06 12:09 ` Adolf Belka
2021-04-06 13:40 ` Michael Tremer
2021-04-07 10:33 ` Adolf Belka
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=20210404111015.66155-1-adolf.belka@ipfire.org \
--to=adolf.belka@ipfire.org \
--cc=development@lists.ipfire.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox