From: ailiop-git <ailiop-git@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] btrfs-progs: update to 5.10.
Date: Sun, 24 Jan 2021 17:11:47 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28153@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1600 bytes --]
There is a new pull request by ailiop-git against master on the void-packages repository
https://github.com/ailiop-git/void-packages btrfs-progs
https://github.com/void-linux/void-packages/pull/28153
btrfs-progs: update to 5.10.
<!-- Mark items with [x] where applicable -->
#### General
- [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)
#### Have the results of the proposed changes been tested?
- [ ] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] I generally don't use the affected packages but briefly tested this PR
<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->
<!--
#### Does it build and run successfully?
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [ ] 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/28153.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-btrfs-progs-28153.patch --]
[-- Type: text/x-diff, Size: 1551 bytes --]
From 3d20abb17e8dfa1f312f2ed670606cf8eac4c6fd Mon Sep 17 00:00:00 2001
From: Anthony Iliopoulos <ailiop@altatus.com>
Date: Sun, 24 Jan 2021 17:03:21 +0100
Subject: [PATCH] btrfs-progs: update to 5.10.
---
srcpkgs/btrfs-progs/template | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/btrfs-progs/template b/srcpkgs/btrfs-progs/template
index 6855dbbc0b4..483fc3ac0c7 100644
--- a/srcpkgs/btrfs-progs/template
+++ b/srcpkgs/btrfs-progs/template
@@ -1,13 +1,13 @@
# Template file for 'btrfs-progs'
pkgname=btrfs-progs
-version=5.9
+version=5.10
revision=1
wrksrc="${pkgname}-v${version}"
build_style=gnu-configure
make_check_target=test
configure_args="--disable-backtrace --disable-python"
hostmakedepends="asciidoc pkg-config xmlto"
-makedepends="acl-devel e2fsprogs-devel libzstd-devel lzo-devel"
+makedepends="acl-devel e2fsprogs-devel libmount-devel libzstd-devel lzo-devel"
checkdepends="acl-progs e2fsprogs tar xz which eudev"
short_desc="Btrfs filesystem utilities"
maintainer="Enno Boland <gottox@voidlinux.org>"
@@ -15,7 +15,7 @@ license="GPL-2.0-only, LGPL-3.0-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=b89358a665ad753ecbdff11d2be77d230d2b197bb3c7e0eb739fb979c087a791
+checksum=e71a0d6dd504f3a5d957fce9a30281eb61ecf991c8af315fe0061a1b97a1d021
pre_build() {
if [ $CROSS_BUILD ]; then
next reply other threads:[~2021-01-24 16:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-24 16:11 ailiop-git [this message]
2021-03-16 23:35 ` FollieHiyuki
2021-03-16 23:36 ` FollieHiyuki
2021-03-30 14:58 ` ahesford
2021-03-30 14:58 ` [PR PATCH] [Closed]: " ahesford
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-28153@inbox.vuxu.org \
--to=ailiop-git@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).