From: ssnailed <ssnailed@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] xsecurelock: update to 1.9.0
Date: Fri, 16 Feb 2024 12:09:36 +0100 [thread overview]
Message-ID: <20240216110936.EB0B12504A@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48759@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 487 bytes --]
There is an updated pull request by ssnailed against master on the void-packages repository
https://github.com/ssnailed/void-packages master
https://github.com/void-linux/void-packages/pull/48759
xsecurelock: update to 1.9.0
#### Testing the changes
- I tested the changes in this PR: **YES**
#### Local build testing
- I built this PR locally for my native architecture, (x86_64-glibc)
A patch file from https://github.com/void-linux/void-packages/pull/48759.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-master-48759.patch --]
[-- Type: text/x-diff, Size: 1994 bytes --]
From f5118ac0148b8420e7741fef7802da1ad490ae25 Mon Sep 17 00:00:00 2001
From: Luca Bilke <bilke@tralios.de>
Date: Fri, 16 Feb 2024 11:52:00 +0100
Subject: [PATCH 1/2] xsecurelock: update to 1.9.0
---
srcpkgs/xsecurelock/template | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/xsecurelock/template b/srcpkgs/xsecurelock/template
index e32f1d71cdd339..99c232ee65b193 100644
--- a/srcpkgs/xsecurelock/template
+++ b/srcpkgs/xsecurelock/template
@@ -1,7 +1,7 @@
# Template file for 'xsecurelock'
pkgname=xsecurelock
-version=1.8.0
-revision=2
+version=1.9.0
+revision=1
build_style=gnu-configure
configure_args="--with-pam-service-name=system-local-login
--with-xscreensaver=/usr/libexec/xscreensaver
@@ -16,7 +16,7 @@ maintainer="Sean R. Lang <srlang@ncsu.edu>"
license="Apache-2.0"
homepage="https://github.com/google/xsecurelock"
distfiles="https://github.com/google/xsecurelock/archive/v${version}.tar.gz"
-checksum=c11a5cc1a9c835749a6fe472a40d12cac10ae4c89a67f153a5492debe7b80633
+checksum=e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
pre_configure() {
sh autogen.sh
From 6e11e2cea5de0409391b25ede2d4c750ef1cbb71 Mon Sep 17 00:00:00 2001
From: Luca Bilke <bilke@tralios.de>
Date: Fri, 16 Feb 2024 12:09:33 +0100
Subject: [PATCH 2/2] fix checksum
---
srcpkgs/xsecurelock/template | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/srcpkgs/xsecurelock/template b/srcpkgs/xsecurelock/template
index 99c232ee65b193..4a964576a93a0a 100644
--- a/srcpkgs/xsecurelock/template
+++ b/srcpkgs/xsecurelock/template
@@ -16,7 +16,7 @@ maintainer="Sean R. Lang <srlang@ncsu.edu>"
license="Apache-2.0"
homepage="https://github.com/google/xsecurelock"
distfiles="https://github.com/google/xsecurelock/archive/v${version}.tar.gz"
-checksum=e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
+checksum=22aca05799326681bf296a288182d7b28066ff2d4db26d09bd7b2dfe8405269e
pre_configure() {
sh autogen.sh
next prev parent reply other threads:[~2024-02-16 11:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-16 11:06 [PR PATCH] " ssnailed
2024-02-16 11:09 ` ssnailed [this message]
2024-02-16 12:56 ` [PR PATCH] [Updated] " ssnailed
2024-02-19 16:53 ` [PR PATCH] [Merged]: " leahneukirchen
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=20240216110936.EB0B12504A@inbox.vuxu.org \
--to=ssnailed@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).