From: motorto <motorto@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] btrfs-progs: update to 5.19.1.
Date: Wed, 14 Sep 2022 23:50:31 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39290@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 675 bytes --]
There is a new pull request by motorto against master on the void-packages repository
https://github.com/motorto/void-packages btrfs-progs-5.19.1
https://github.com/void-linux/void-packages/pull/39290
btrfs-progs: update to 5.19.1.
<!-- 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-glibc
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- armv6l
A patch file from https://github.com/void-linux/void-packages/pull/39290.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-btrfs-progs-5.19.1-39290.patch --]
[-- Type: text/x-diff, Size: 1244 bytes --]
From 5cca5a6a7e79c38a045ea00fc426c6ca1f97131a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Andr=C3=A9=20Cerqueira?= <acerqueira021@gmail.com>
Date: Wed, 14 Sep 2022 22:45:41 +0100
Subject: [PATCH] btrfs-progs: update to 5.19.1.
---
srcpkgs/btrfs-progs/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/btrfs-progs/template b/srcpkgs/btrfs-progs/template
index 292d5110106b..19dbfbf4b34e 100644
--- a/srcpkgs/btrfs-progs/template
+++ b/srcpkgs/btrfs-progs/template
@@ -1,6 +1,6 @@
# Template file for 'btrfs-progs'
pkgname=btrfs-progs
-version=5.19
+version=5.19.1
revision=1
wrksrc="${pkgname}-v${version}"
build_style=gnu-configure
@@ -16,7 +16,7 @@ license="GPL-2.0-only, LGPL-2.1-or-later"
homepage="https://btrfs.wiki.kernel.org/index.php/Main_Page"
changelog="https://raw.githubusercontent.com/kdave/btrfs-progs/master/CHANGES"
distfiles="${KERNEL_SITE}/kernel/people/kdave/${pkgname}/${pkgname}-v${version}.tar.xz"
-checksum=1fbcf06e4b2f80e7a127fd687ed4625a5b74fa674fe212c836ff70e0edfcccf9
+checksum=26429e540343ccc7f5d4b3f8f42b916713280e898c5471da705026ef6d2c10a6
# Most of the tests depend on `mount` and `fallocate` commands, which are not
# presented in chroot-util-linux
make_check=no
next reply other threads:[~2022-09-14 21:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-14 21:50 motorto [this message]
2022-09-20 15:26 ` [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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39290@inbox.vuxu.org \
--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).