Github messages for voidlinux
 help / color / mirror / Atom feed
From: ftrvxmtrx <ftrvxmtrx@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] pinentry-dmenu: move to a maintained fork and take ownership of the package
Date: Fri, 21 Jan 2022 17:28:34 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35154@inbox.vuxu.org> (raw)

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

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

https://github.com/ftrvxmtrx/void-packages pinentry-dmenu-fork
https://github.com/void-linux/void-packages/pull/35154

pinentry-dmenu: move to a maintained fork and take ownership of the package
#### Testing the changes
- I tested the changes in this PR: **YES**

#### Local build testing
- I built this PR locally for my native architecture, (aarch64-musl)


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

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-pinentry-dmenu-fork-35154.patch --]
[-- Type: text/x-diff, Size: 1545 bytes --]

From 1420ccdfd56acad3c4a97aeaf3fc2adc6a319859 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Sigrid=20Solveig=20Hafl=C3=ADnud=C3=B3ttir?=
 <ftrvxmtrx@gmail.com>
Date: Fri, 21 Jan 2022 17:26:52 +0100
Subject: [PATCH] pinentry-dmenu: move to a maintained fork and take ownership
 of the package

---
 srcpkgs/pinentry-dmenu/template | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/srcpkgs/pinentry-dmenu/template b/srcpkgs/pinentry-dmenu/template
index c1bed06079ff..7d760f7ecdcd 100644
--- a/srcpkgs/pinentry-dmenu/template
+++ b/srcpkgs/pinentry-dmenu/template
@@ -1,17 +1,17 @@
 # Template file for 'pinentry-dmenu'
 pkgname=pinentry-dmenu
-version=0.2.2
-revision=2
+version=0.2.3
+revision=1
 build_style=gnu-makefile
 makedepends="libXft-devel freetype-devel libconfig-devel
  libXinerama-devel libgpg-error-devel libassuan-devel
  gpgme-devel"
 short_desc="Pinentry program based on dmenu"
-maintainer="Orphaned <orphan@voidlinux.org>"
+maintainer="Sigrid Solveig Haflínudóttir <ftrvxmtrx@gmail.com>"
 license="GPL-2.0-or-later"
-homepage="https://github.com/ritze/pinentry-dmenu"
-distfiles="https://github.com/ritze/pinentry-dmenu/archive/${version}.tar.gz"
-checksum=7b29b79e7c3b5c00d1f3320aa522e88064b1e366542bb94735905cabcf3d4c62
+homepage="https://github.com/ftrvxmtrx/pinentry-dmenu"
+distfiles="https://github.com/ftrvxmtrx/pinentry-dmenu/archive/${version}.tar.gz"
+checksum=8ee15e114a880fd5f5c5f5aebd9b2eb469b26104449987454ee789fbe2bf9ee3
 
 alternatives="pinentry:pinentry:/usr/bin/pinentry-dmenu"
 

             reply	other threads:[~2022-01-21 16:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-21 16:28 ftrvxmtrx [this message]
2022-01-21 16:34 ` abenson
2022-01-21 19:58 ` ericonr
2022-01-21 19:58 ` ericonr
2022-01-21 20:01 ` [PR PATCH] [Updated] " ftrvxmtrx
2022-01-21 20:03 ` [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-35154@inbox.vuxu.org \
    --to=ftrvxmtrx@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    --subject='Re: [PR PATCH] pinentry-dmenu: move to a maintained fork and take ownership of the package' \
    /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

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).