Github messages for voidlinux
 help / color / mirror / Atom feed
From: jovanlanik <jovanlanik@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] gtklock: update to 1.3.6
Date: Fri, 09 Sep 2022 01:58:13 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39177@inbox.vuxu.org> (raw)

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

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

https://github.com/jovanlanik/void-packages master
https://github.com/void-linux/void-packages/pull/39177

gtklock: update to 1.3.6
<!-- 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/39177.patch is attached

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

From ff2ec769ab870ffb474ac4e48cdcf919d51a957d Mon Sep 17 00:00:00 2001
From: Jovan Lanik <jox969@gmail.com>
Date: Fri, 9 Sep 2022 01:56:30 +0200
Subject: [PATCH] gtklock: update to 1.3.6

---
 srcpkgs/gtklock/template | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/gtklock/template b/srcpkgs/gtklock/template
index c88fc4ac1c9e..eadc1162bc09 100644
--- a/srcpkgs/gtklock/template
+++ b/srcpkgs/gtklock/template
@@ -1,6 +1,6 @@
 # Template file for 'gtklock'
 pkgname=gtklock
-version=1.3.5
+version=1.3.6
 revision=1
 build_style=gnu-makefile
 make_use_env=yes
@@ -11,7 +11,7 @@ maintainer="Jovan Lanik <jox969@gmail.com>"
 license="GPL-3.0-or-later"
 homepage="https://github.com/jovanlanik/gtklock"
 distfiles="https://github.com/jovanlanik/gtklock/archive/refs/tags/v${version}.tar.gz"
-checksum=753259cdf4b16dbe2b564a80a919976c2661a028d9d06b22f1da466e615a6766
+checksum=ddc39721e0fc4e2bfb18c17bb5f158af79934f376258137dc78b144ff84c1650
 
 post_install() {
 	# copying CSS example provided

             reply	other threads:[~2022-09-08 23:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-08 23:58 jovanlanik [this message]
2022-09-10 13:20 ` [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-39177@inbox.vuxu.org \
    --to=jovanlanik@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).