From: tibequadorian <tibequadorian@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] timg: update to 1.4.4.
Date: Thu, 24 Mar 2022 16:49:13 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36317@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1216 bytes --]
There is a new pull request by tibequadorian against master on the void-packages repository
https://github.com/tibequadorian/void-packages timg
https://github.com/void-linux/void-packages/pull/36317
timg: update to 1.4.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 [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please [skip CI](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/36317.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-timg-36317.patch --]
[-- Type: text/x-diff, Size: 1067 bytes --]
From 48d29e99c27e914dca88abd24c215c7491d4bfc8 Mon Sep 17 00:00:00 2001
From: tibequadorian <tibequadorian@posteo.de>
Date: Thu, 24 Mar 2022 16:47:44 +0100
Subject: [PATCH] timg: update to 1.4.4.
---
srcpkgs/timg/template | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/timg/template b/srcpkgs/timg/template
index 7774d007cf01..91f1516b2597 100644
--- a/srcpkgs/timg/template
+++ b/srcpkgs/timg/template
@@ -1,6 +1,6 @@
# Template file for 'timg'
pkgname=timg
-version=1.4.2
+version=1.4.4
revision=1
build_style=cmake
configure_args="-DWITH_OPENSLIDE_SUPPORT=off -Wno-dev"
@@ -10,5 +10,5 @@ short_desc="24-bit color image & video viewer for terminal"
maintainer="33KK <g33kk@pm.me>"
license="GPL-2.0-only"
homepage="https://github.com/hzeller/timg"
-distfiles="${homepage}/archive/v${version}.tar.gz"
-checksum=7607efaffbed0b65b3c824956de421b155a4f14243e7a752b19454f88bf9d563
+distfiles="https://github.com/hzeller/timg/archive/v${version}.tar.gz"
+checksum=66d2e00b50068fd6638bb8be1859c50ca4f24caef751f9dc95b303f37fb07b1e
next reply other threads:[~2022-03-24 15:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-24 15:49 tibequadorian [this message]
2022-03-25 0:16 ` [PR PATCH] [Updated] " tibequadorian
2022-03-25 1:19 ` tibequadorian
2022-03-26 0:37 ` [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-36317@inbox.vuxu.org \
--to=tibequadorian@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).