From: jestark <jestark@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] i3lock-color: Update to 2.12.c.5
Date: Fri, 31 Jul 2020 05:56:39 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23965@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 429 bytes --]
There is a new pull request by jestark against master on the void-packages repository
https://github.com/jestark/void-packages master
https://github.com/void-linux/void-packages/pull/23965
i3lock-color: Update to 2.12.c.5
i3lock-color has a new maintainer, Raymo111, switch upstream to his
repository and update to the latest release.
A patch file from https://github.com/void-linux/void-packages/pull/23965.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-master-23965.patch --]
[-- Type: text/x-diff, Size: 1653 bytes --]
From d4eae5b718a39deaa9780c6a563c4a86bfdfaebf Mon Sep 17 00:00:00 2001
From: James Stark <jstark@fortinet.com>
Date: Thu, 30 Jul 2020 18:51:08 -0700
Subject: [PATCH] i3lock-color: Update to 2.12.c.5
i3lock-color has a new maintainer, Raymo111, switch upstream to his
repository and update to the latest release.
---
srcpkgs/i3lock-color/template | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/srcpkgs/i3lock-color/template b/srcpkgs/i3lock-color/template
index 07bd585c69d..ce9cb5e1c82 100644
--- a/srcpkgs/i3lock-color/template
+++ b/srcpkgs/i3lock-color/template
@@ -1,8 +1,8 @@
# Template file for 'i3lock-color'
pkgname=i3lock-color
-version=2.12
-revision=2
-wrksrc="${pkgname}-${version}.c"
+version=2.12.c.5
+revision=1
+wrksrc="${pkgname}-${version}"
build_style=gnu-configure
hostmakedepends="pkg-config automake"
makedepends="libev-devel cairo-devel pam-devel libxkbcommon-devel xcb-util-devel
@@ -10,9 +10,9 @@ makedepends="libev-devel cairo-devel pam-devel libxkbcommon-devel xcb-util-devel
short_desc="Screenlocker forked from i3lock with more features"
maintainer="jtalowell <jtalowell@protonmail.com>"
license="MIT"
-homepage="https://github.com/PandorasFox/i3lock-color"
-distfiles="https://github.com/PandorasFox/i3lock-color/archive/${version}.c.tar.gz"
-checksum=c2ba4cfa51fee3fd2cab439805d213d8614407d93cf8eecbd4e6fa5cb4c9b7a3
+homepage="https://github.com/Raymo111/i3lock-color"
+distfiles="https://github.com/Raymo111/i3lock-color/archive/${version}.tar.gz"
+checksum=3a097a683145e5f4e3267acc6f1517385389cf2a993145017bf8ac437b51ff68
conf_files="/etc/pam.d/i3lock"
conflicts="i3lock"
next reply other threads:[~2020-07-31 3:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-31 3:56 jestark [this message]
2020-10-03 22:42 ` [PR PATCH] [Closed]: " jestark
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-23965@inbox.vuxu.org \
--to=jestark@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).