From: steinex <steinex@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] xfce4-terminal: update to 1.0.3.
Date: Fri, 13 May 2022 18:43:39 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37103@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1245 bytes --]
There is a new pull request by steinex against master on the void-packages repository
https://github.com/steinex/void-packages xfce4-terminal
https://github.com/void-linux/void-packages/pull/37103
xfce4-terminal: update to 1.0.3.
<!-- 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 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/37103.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-xfce4-terminal-37103.patch --]
[-- Type: text/x-diff, Size: 1126 bytes --]
From 0a311678c39ff00a15fdf36b8f60c592d66fa02f Mon Sep 17 00:00:00 2001
From: Frank Steinborn <steinex@nognu.de>
Date: Fri, 13 May 2022 18:27:45 +0200
Subject: [PATCH] xfce4-terminal: update to 1.0.3.
---
srcpkgs/xfce4-terminal/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/xfce4-terminal/template b/srcpkgs/xfce4-terminal/template
index 418817a0ac32..d3aaada37900 100644
--- a/srcpkgs/xfce4-terminal/template
+++ b/srcpkgs/xfce4-terminal/template
@@ -1,6 +1,6 @@
# Template file for 'xfce4-terminal'
pkgname=xfce4-terminal
-version=1.0.2
+version=1.0.3
revision=1
build_style=gnu-configure
configure_args="--with-locales-dir=/usr/share/locale"
@@ -13,4 +13,4 @@ license="GPL-2.0-or-later"
homepage="https://docs.xfce.org/apps/xfce4-terminal/start"
changelog="https://gitlab.xfce.org/apps/xfce4-terminal/-/raw/master/NEWS"
distfiles="https://archive.xfce.org/src/apps/${pkgname}/${version%.*}/${pkgname}-${version}.tar.bz2"
-checksum=ac1543167b43322ad2483ffb033a7e74669ecb59f4b63016a3c183d96141d326
+checksum=1c69a6d2edffbaf30d7123da82fd05c12259fc279caf7c491520158cc67ff5ed
next reply other threads:[~2022-05-13 16:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-13 16:43 steinex [this message]
2022-05-13 19:13 ` [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-37103@inbox.vuxu.org \
--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).