Github messages for voidlinux
 help / color / mirror / Atom feed
From: 4ricci <4ricci@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] gnupg2: update to 2.2.28.
Date: Sat, 12 Jun 2021 13:31:48 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31437@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1558 bytes --]

There is a new pull request by 4ricci against master on the void-packages repository

https://github.com/4ricci/void-packages gnupg2
https://github.com/void-linux/void-packages/pull/31437

gnupg2: update to 2.2.28.
<!-- Mark items with [x] where applicable -->

#### General
- [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)

#### Have the results of the proposed changes been tested?
- [x] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] I generally don't use the affected packages but briefly tested this PR

<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->
<!-- 
#### Does it build and run successfully? 
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [ ] I built this PR locally for my native architecture, (ARCH-LIBC)
- [ ] I built this PR locally for these architectures (if supported. mark crossbuilds):
  - [ ] aarch64-musl
  - [ ] armv7l
  - [ ] armv6l-musl
-->


A patch file from https://github.com/void-linux/void-packages/pull/31437.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-gnupg2-31437.patch --]
[-- Type: text/x-diff, Size: 1437 bytes --]

From d1155fbfe61e7de9697d256be95e1c5ef844665a Mon Sep 17 00:00:00 2001
From: Roberto Ricci <ricci@disroot.org>
Date: Sat, 12 Jun 2021 13:19:18 +0200
Subject: [PATCH] gnupg2: update to 2.2.28.

---
 srcpkgs/gnupg2/template | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/srcpkgs/gnupg2/template b/srcpkgs/gnupg2/template
index 8cd59ff07a52..772a6baab6f7 100644
--- a/srcpkgs/gnupg2/template
+++ b/srcpkgs/gnupg2/template
@@ -1,6 +1,6 @@
 # Template file for 'gnupg2'
 pkgname=gnupg2
-version=2.2.27
+version=2.2.28
 revision=1
 wrksrc="gnupg-${version}"
 build_style=gnu-configure
@@ -11,14 +11,14 @@ configure_args="--enable-gpg-is-gpg2 $(vopt_enable ldap)
  --with-npth-prefix=${XBPS_CROSS_BASE}/usr"
 hostmakedepends="pkg-config"
 makedepends="bzip2-devel gnutls-devel libassuan-devel libcurl-devel
- libksba-devel libldap-devel libusb-compat-devel npth-devel sqlite-devel"
+ libksba-devel libldap-devel libusb-compat-devel npth-devel sqlite-devel libgcrypt-devel"
 depends="pinentry"
 short_desc="GNU Privacy Guard (2.x)"
 maintainer="Orphaned <orphan@voidlinux.org>"
 license="GPL-3.0-or-later"
 homepage="https://www.gnupg.org/"
 distfiles="https://gnupg.org/ftp/gcrypt/gnupg/gnupg-${version}.tar.bz2"
-checksum=34e60009014ea16402069136e0a5f63d9b65f90096244975db5cea74b3d02399
+checksum=6ff891fc7583a9c3fb9f097ee0d1de0a12469d4b53997e7ba5064950637dfaec
 build_options="ldap"
 build_options_default="ldap"
 

             reply	other threads:[~2021-06-12 11:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-12 11:31 4ricci [this message]
2021-06-12 18:07 ` [PR REVIEW] " ericonr
2021-06-12 18:14 ` [PR PATCH] [Updated] " 4ricci
2021-06-14  2:55 ` [PR PATCH] [Merged]: " ericonr

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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31437@inbox.vuxu.org \
    --to=4ricci@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).