Github messages for voidlinux
 help / color / mirror / Atom feed
From: steinex <steinex@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] xprop: update to 1.2.6.
Date: Thu, 12 Jan 2023 09:15:18 +0100	[thread overview]
Message-ID: <20230112081518._GD2iWNKGM1jgJLSKS8m2CgfgBvuOlTqI_GJ0h6fmEo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41584@inbox.vuxu.org>

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

There is an updated pull request by steinex against master on the void-packages repository

https://github.com/steinex/void-packages xprop
https://github.com/void-linux/void-packages/pull/41584

xprop: update to 1.2.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/41584.patch is attached

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

From f56d8139d9ec487ff7530c99b3c04ba83135a9fd Mon Sep 17 00:00:00 2001
From: Frank Steinborn <steinex@nognu.de>
Date: Wed, 11 Jan 2023 11:12:23 +0100
Subject: [PATCH] xprop: update to 1.2.6.

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

diff --git a/srcpkgs/xprop/template b/srcpkgs/xprop/template
index cd0a28ed05d7..0a27d4b71fff 100644
--- a/srcpkgs/xprop/template
+++ b/srcpkgs/xprop/template
@@ -1,6 +1,6 @@
 # Template file for 'xprop'
 pkgname=xprop
-version=1.2.5
+version=1.2.6
 revision=1
 build_style=gnu-configure
 hostmakedepends="pkg-config"
@@ -8,9 +8,9 @@ makedepends="libX11-devel libXmu-devel"
 short_desc="Property displayer for X"
 maintainer="Frank Steinborn <steinex@nognu.de>"
 license="MIT"
-homepage="https://xorg.freedesktop.org/wiki/"
-distfiles="${XORG_SITE}/app/${pkgname}-${version}.tar.bz2"
-checksum=9b92ed0316bf2486121d8bac88bd1878f16b43bd335f18009b1f941f1eca93a1
+homepage="https://gitlab.freedesktop.org/xorg/app/xprop"
+distfiles="${XORG_SITE}/app/xprop-${version}.tar.xz"
+checksum=580b8525b12ecc0144aa16c88b0aafa76d2e799b44c8c6c50f9ce92788b5586e
 
 post_install() {
 	vlicense COPYING

  parent reply	other threads:[~2023-01-12  8:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-11 10:23 [PR PATCH] " steinex
2023-01-12  4:56 ` [PR REVIEW] " classabbyamp
2023-01-12  8:15 ` steinex [this message]
2023-01-12 16:09 ` [PR PATCH] [Merged]: " leahneukirchen

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=20230112081518._GD2iWNKGM1jgJLSKS8m2CgfgBvuOlTqI_GJ0h6fmEo@z \
    --to=steinex@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).