From: motorto <motorto@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] xcb-util-cursor: update to 0.1.4.
Date: Sun, 27 Nov 2022 13:25:55 +0100 [thread overview]
Message-ID: <20221127122555._8dc5dNffwzDRIQzC6X70csdnMC3rG3BGdj5zho7TzM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40626@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 586 bytes --]
There is an updated pull request by motorto against master on the void-packages repository
https://github.com/motorto/void-packages xcb-util-cursor_0.1.3
https://github.com/void-linux/void-packages/pull/40626
xcb-util-cursor: update to 0.1.4.
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
#### Local build testing
- I built this PR locally for my native architecture, x86_64-musl
A patch file from https://github.com/void-linux/void-packages/pull/40626.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-xcb-util-cursor_0.1.3-40626.patch --]
[-- Type: text/x-diff, Size: 1409 bytes --]
From cc9c7f29ab99ed26dded01d2aea2c51e88ebd5e2 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Andr=C3=A9=20Cerqueira?= <acerqueira021@gmail.com>
Date: Sat, 19 Nov 2022 22:35:34 +0000
Subject: [PATCH] xcb-util-cursor: update to 0.1.4.
---
srcpkgs/xcb-util-cursor/template | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/srcpkgs/xcb-util-cursor/template b/srcpkgs/xcb-util-cursor/template
index 16beb6bb0051..b69bd9217772 100644
--- a/srcpkgs/xcb-util-cursor/template
+++ b/srcpkgs/xcb-util-cursor/template
@@ -1,6 +1,6 @@
-# Template build for 'xcb-util-cursor'.
+# Template file for 'xcb-util-cursor'
pkgname=xcb-util-cursor
-version=0.1.3
+version=0.1.4
revision=1
build_style=gnu-configure
configure_args="--disable-static"
@@ -8,10 +8,10 @@ hostmakedepends="pkg-config gperf m4"
makedepends="xcb-util-renderutil-devel xcb-util-image-devel"
short_desc="XCB cursor library (libxcursor port)"
maintainer="Orphaned <orphan@voidlinux.org>"
-homepage="http://xcb.freedesktop.org"
license="MIT"
-distfiles="http://xcb.freedesktop.org/dist/${pkgname}-${version}.tar.bz2"
-checksum=05a10a0706a1a789a078be297b5fb663f66a71fb7f7f1b99658264c35926394f
+homepage="https://xcb.freedesktop.org"
+distfiles="https://xcb.freedesktop.org/dist/xcb-util-cursor-${version}.tar.xz"
+checksum=28dcfe90bcab7b3561abe0dd58eb6832aa9cc77cfe42fcdfa4ebe20d605231fb
post_install() {
vlicense COPYING
next prev parent reply other threads:[~2022-11-27 12:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-19 22:36 [PR PATCH] " motorto
2022-11-19 22:38 ` [PR PATCH] [Updated] " motorto
2022-11-19 22:38 ` motorto
2022-11-20 5:47 ` [PR REVIEW] " classabbyamp
2022-11-20 10:46 ` [PR PATCH] [Updated] " motorto
2022-11-24 6:59 ` [PR REVIEW] " classabbyamp
2022-11-27 12:25 ` motorto [this message]
2022-11-27 12:26 ` motorto
2022-11-27 15:49 ` [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=20221127122555._8dc5dNffwzDRIQzC6X70csdnMC3rG3BGdj5zho7TzM@z \
--to=motorto@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).