From: chrysos349 <chrysos349@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] gnome-text-editor: update to 46.1
Date: Fri, 19 Apr 2024 16:34:45 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-49917@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 496 bytes --]
There is a new pull request by chrysos349 against master on the void-packages repository
https://github.com/chrysos349/void-packages gnome-text-editor
https://github.com/void-linux/void-packages/pull/49917
gnome-text-editor: update to 46.1
#### 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)
A patch file from https://github.com/void-linux/void-packages/pull/49917.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-gnome-text-editor-49917.patch --]
[-- Type: text/x-diff, Size: 1195 bytes --]
From eda1b8da65677492ae452279a9aefc57c8457bae Mon Sep 17 00:00:00 2001
From: chrysos349 <chrysostom349@gmail.com>
Date: Fri, 19 Apr 2024 17:34:21 +0300
Subject: [PATCH] gnome-text-editor: update to 46.1
---
srcpkgs/gnome-text-editor/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/gnome-text-editor/template b/srcpkgs/gnome-text-editor/template
index 97edcd00f1a52f..9c62afef873718 100644
--- a/srcpkgs/gnome-text-editor/template
+++ b/srcpkgs/gnome-text-editor/template
@@ -1,6 +1,6 @@
# Template file for 'gnome-text-editor'
pkgname=gnome-text-editor
-version=45.3
+version=46.1
revision=1
build_style=meson
hostmakedepends="pkg-config gettext itstool glib-devel
@@ -14,4 +14,4 @@ homepage="https://gitlab.gnome.org/GNOME/gnome-text-editor"
#changelog="https://gitlab.gnome.org/GNOME/gnome-text-editor/-/raw/gnome-45/NEWS"
changelog="https://gitlab.gnome.org/GNOME/gnome-text-editor/-/raw/main/NEWS"
distfiles="${GNOME_SITE}/gnome-text-editor/${version%.*}/gnome-text-editor-$version.tar.xz"
-checksum=f3ffcb11a92dfd04ba3c3b3d0e667847d4449a21e012ae36f07dda05ac7d3a52
+checksum=8ebfa0bea12e75f5efeacc721be3b8ae65027b024aa81db9ecab8c312257a2eb
next reply other threads:[~2024-04-19 14:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-19 14:34 chrysos349 [this message]
2024-04-20 1:52 ` [PR PATCH] [Merged]: " oreo639
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-49917@inbox.vuxu.org \
--to=chrysos349@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).