From: lonxwolx <lonxwolx@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] betterlockscreen: update to 4.0.4.
Date: Sat, 10 Sep 2022 11:26:48 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39199@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1292 bytes --]
There is a new pull request by lonxwolx against master on the void-packages repository
https://github.com/lonxwolx/void-packages betterlockscreen
https://github.com/void-linux/void-packages/pull/39199
betterlockscreen: update to 4.0.4.
betterlockscreen: update to 4.0.4
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- 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/39199.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-betterlockscreen-39199.patch --]
[-- Type: text/x-diff, Size: 1994 bytes --]
From a785eac666caa433392ef6208ca0d3ca31f4f574 Mon Sep 17 00:00:00 2001
From: lonxwolx <lonxwolx@gmail.com>
Date: Tue, 6 Sep 2022 12:43:28 +0800
Subject: [PATCH] betterlockscreen: update to 4.0.4.
betterlockscreen: update to 4.0.4
---
srcpkgs/betterlockscreen/patches/use-loginctl.patch | 8 +++-----
srcpkgs/betterlockscreen/template | 6 +++---
2 files changed, 6 insertions(+), 8 deletions(-)
diff --git a/srcpkgs/betterlockscreen/patches/use-loginctl.patch b/srcpkgs/betterlockscreen/patches/use-loginctl.patch
index b2f67eb8bdb7..fbee7bb3b249 100644
--- a/srcpkgs/betterlockscreen/patches/use-loginctl.patch
+++ b/srcpkgs/betterlockscreen/patches/use-loginctl.patch
@@ -1,12 +1,10 @@
--- a/betterlockscreen
+++ b/betterlockscreen
-@@ -965,6 +965,6 @@ done
+@@ -968,6 +968,6 @@ echof header "Betterlockscreen"
# Activate lockscreen
[[ $runsuspend ]] || lockargs+=(-n)
[[ $runlock ]] && lockselect "$lockstyle" && \
- { [[ $runsuspend ]] && systemctl suspend; }
+ { [[ $runsuspend ]] && loginctl suspend; }
-
--exit 0
-\ No newline at end of file
-+exit 0
+
+ exit 0
diff --git a/srcpkgs/betterlockscreen/template b/srcpkgs/betterlockscreen/template
index 5de5ae4c67b6..2052595c5b40 100644
--- a/srcpkgs/betterlockscreen/template
+++ b/srcpkgs/betterlockscreen/template
@@ -1,14 +1,14 @@
# Template file for 'betterlockscreen'
pkgname=betterlockscreen
-version=4.0.3
-revision=2
+version=4.0.4
+revision=1
depends="ImageMagick bash bc feh i3lock-color xdpyinfo xrandr xrdb xset"
short_desc="Sweet looking lockscreen for linux system"
maintainer="Aleksander Zien <Aleks@nderZien.com>"
license="MIT"
homepage="https://github.com/pavanjadhaw/betterlockscreen"
distfiles="https://github.com/pavanjadhaw/betterlockscreen/archive/refs/tags/v${version}.tar.gz"
-checksum=d96fd64f1c94c91fec5d26b9665ba68f7f130c8a8612978ad9edbfa859710671
+checksum=608b56989eea0b45c0f88bdc9e3c7742430f809a1bcd60d558eb6af99aeecc91
do_install() {
vbin betterlockscreen
next reply other threads:[~2022-09-10 9:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-10 9:26 lonxwolx [this message]
2022-09-10 21:41 ` [PR PATCH] [Merged]: " classabbyamp
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-39199@inbox.vuxu.org \
--to=lonxwolx@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).