From: teldra <teldra@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] gparted: update to 1.3.1.
Date: Sat, 07 Aug 2021 09:45:01 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32382@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 720 bytes --]
There is a new pull request by teldra against master on the void-packages repository
https://github.com/teldra/void-packages update-gparted
https://github.com/void-linux/void-packages/pull/32382
gparted: update to 1.3.1.
#### Have the results of the proposed changes been tested?
- [x] I generally don't use the affected packages but briefly tested this PR
#### Does it build and run successfully?
- [x] I built this PR locally for my native architecture, (x86_64-glibc)
- [x] I built this PR locally for these architectures (if supported. mark crossbuilds):
- [x] aarch64-musl
- [x] armv7l
- [x] armv6l-musl
A patch file from https://github.com/void-linux/void-packages/pull/32382.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-update-gparted-32382.patch --]
[-- Type: text/x-diff, Size: 1057 bytes --]
From c6bf7bfe10fbb55d0faa73298a73281fbd959648 Mon Sep 17 00:00:00 2001
From: teldra <teldra@rotce.de>
Date: Sat, 7 Aug 2021 09:43:00 +0200
Subject: [PATCH] gparted: update to 1.3.1.
---
srcpkgs/gparted/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/gparted/template b/srcpkgs/gparted/template
index 2a84ad3954ae..db6d59810086 100644
--- a/srcpkgs/gparted/template
+++ b/srcpkgs/gparted/template
@@ -1,6 +1,6 @@
# Template file for 'gparted'
pkgname=gparted
-version=1.3.0
+version=1.3.1
revision=1
build_style=gnu-configure
configure_args="--enable-libparted-dmraid"
@@ -13,7 +13,7 @@ maintainer="teldra <teldra@rotce.de>"
license="GPL-2.0-or-later"
homepage="https://gparted.sourceforge.io"
distfiles="${SOURCEFORGE_SITE}/gparted/gparted/gparted-${version}/gparted-${version}.tar.gz"
-checksum=8dc180245dd9ea45e6e2f4bc69512f187e08be7f799c98a825a0b04c161cbd2a
+checksum=5eee2e6d74b15ef96b13b3a2310c868ed2298e03341021e7d12a5a98a1d1e109
# Some tests are known to fail since 1.1.0
# This disables these:
next reply other threads:[~2021-08-07 7:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-07 7:45 teldra [this message]
2021-08-08 21:03 ` [PR PATCH] [Merged]: " ericonr
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-32382@inbox.vuxu.org \
--to=teldra@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).