Github messages for voidlinux
 help / color / mirror / Atom feed
From: vilhelmbergsoe <vilhelmbergsoe@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] betterlockscreen: update to 4.0.3
Date: Sun, 10 Oct 2021 22:51:36 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33469@inbox.vuxu.org> (raw)

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

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

https://github.com/vilhelmbergsoe/void-packages master
https://github.com/void-linux/void-packages/pull/33469

betterlockscreen: update to 4.0.3
<!-- 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?
- [ ] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [x] 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/33469.patch is attached

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

From cec034d59da3558dd139ab23a88e0866c464f3ff Mon Sep 17 00:00:00 2001
From: Vilhelm Bergsoe <vilhelmbergsoe@gmail.com>
Date: Sun, 10 Oct 2021 22:33:35 +0200
Subject: [PATCH] betterlockscreen: update to 4.0.3

---
 srcpkgs/betterlockscreen/template | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/srcpkgs/betterlockscreen/template b/srcpkgs/betterlockscreen/template
index c0e5d710f151..904496193f18 100644
--- a/srcpkgs/betterlockscreen/template
+++ b/srcpkgs/betterlockscreen/template
@@ -1,14 +1,14 @@
 # Template file for 'betterlockscreen'
 pkgname=betterlockscreen
-version=3.0.1
-revision=3
+version=4.0.3
+revision=1
 depends="ImageMagick bash bc feh i3lock-color xdpyinfo xrandr xrdb"
 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/${version}.tar.gz"
-checksum=9b80af4b93e0b35bc916a584522ecf9eb39414c8010a2e4f2bb6941fdc5faf28
+distfiles="https://github.com/pavanjadhaw/betterlockscreen/archive/refs/tags/v${version}.tar.gz"
+checksum=d96fd64f1c94c91fec5d26b9665ba68f7f130c8a8612978ad9edbfa859710671
 
 do_install() {
 	vbin ${pkgname}

             reply	other threads:[~2021-10-10 20:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-10 20:51 vilhelmbergsoe [this message]
2021-10-11 10:44 ` [PR PATCH] [Updated] " vilhelmbergsoe
2021-10-11 21:57 ` [PR PATCH] [Merged]: " paper42

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-33469@inbox.vuxu.org \
    --to=vilhelmbergsoe@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).