From: ram02z <ram02z@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] CopyQ: update to 6.0.1.
Date: Tue, 04 Jan 2022 02:58:04 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34840@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1208 bytes --]
There is a new pull request by ram02z against master on the void-packages repository
https://github.com/ram02z/void-packages CopyQ
https://github.com/void-linux/void-packages/pull/34840
CopyQ: update to 6.0.1.
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **briefly**
<!--
#### 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/34840.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-CopyQ-34840.patch --]
[-- Type: text/x-diff, Size: 1013 bytes --]
From ddaae74210f75ecb8d6fa9be3a66de99a9b2e729 Mon Sep 17 00:00:00 2001
From: Omar Zeghouani <omarzeghouanii@gmail.com>
Date: Tue, 4 Jan 2022 01:56:52 +0000
Subject: [PATCH] CopyQ: update to 6.0.1.
---
srcpkgs/CopyQ/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/CopyQ/template b/srcpkgs/CopyQ/template
index 3f9db762dbb0..c7fa15c9d05c 100644
--- a/srcpkgs/CopyQ/template
+++ b/srcpkgs/CopyQ/template
@@ -1,6 +1,6 @@
# Template file for 'CopyQ'
pkgname=CopyQ
-version=5.0.0
+version=6.0.1
revision=1
build_style=cmake
hostmakedepends="qt5-tools-devel extra-cmake-modules pkg-config
@@ -14,4 +14,4 @@ license="GPL-3.0-or-later"
homepage="https://hluk.github.io/CopyQ/"
changelog="https://raw.githubusercontent.com/hluk/CopyQ/master/CHANGES.md"
distfiles="https://github.com/hluk/CopyQ/archive/v${version}.tar.gz"
-checksum=cc77ef8104771bbaa8f99025c1e7a3d318892b0e8767021f3243457b0c68948e
+checksum=8d0b0fa840993fa100e888a5a1098e2769e3c234cd44236d75039e5c6e517645
next reply other threads:[~2022-01-04 1:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-04 1:58 ram02z [this message]
2022-01-05 7:25 ` ericonr
2022-01-05 15:03 ` mobinmob
2022-01-05 19:17 ` [PR PATCH] [Merged]: " ericonr
-- strict thread matches above, loose matches on Subject: below --
2022-01-02 19:44 [PR PATCH] CopyQ: Update " Jlll1
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-34840@inbox.vuxu.org \
--to=ram02z@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).