Github messages for voidlinux
 help / color / mirror / Atom feed
From: FollieHiyuki <FollieHiyuki@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] btrfs-progs: update to 5.11
Date: Fri, 19 Mar 2021 18:37:20 +0100	[thread overview]
Message-ID: <20210319173720.zEJqLHrXaKrFbh5kREXMgq33qDIETR-Dzw77Oy7ybTU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29547@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1850 bytes --]

There is an updated pull request by FollieHiyuki against master on the void-packages repository

https://github.com/FollieHiyuki/void-packages btrfs-update
https://github.com/void-linux/void-packages/pull/29547

btrfs-progs: update to 5.11
<!-- 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?
- [x] 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

Taken over and closes #28153
Why do we disable Python bindings for `libbtrfsutil`?
I gave up half way through cherry-picking tests to disable :) Most of them fail without `mount` command from util-linux.
Welcome other for battle test.

<!--
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/29547.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-btrfs-update-29547.patch --]
[-- Type: text/x-diff, Size: 1641 bytes --]

From 1736481211856366fd6d06588f6de08e6c2e805b Mon Sep 17 00:00:00 2001
From: FollieHiyuki <folliekazetani@protonmail.com>
Date: Wed, 17 Mar 2021 18:16:46 +0300
Subject: [PATCH] btrfs-progs: update to 5.11

---
 srcpkgs/btrfs-progs/template | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/srcpkgs/btrfs-progs/template b/srcpkgs/btrfs-progs/template
index 6855dbbc0b40..095113147f4d 100644
--- a/srcpkgs/btrfs-progs/template
+++ b/srcpkgs/btrfs-progs/template
@@ -1,21 +1,22 @@
 # Template file for 'btrfs-progs'
 pkgname=btrfs-progs
-version=5.9
+version=5.11
 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"
-checkdepends="acl-progs e2fsprogs tar xz which eudev"
+makedepends="acl-devel e2fsprogs-devel libzstd-devel lzo-devel libblkid-devel
+ libuuid-devel zlib-devel"
+checkdepends="acl-progs attr-progs e2fsprogs tar xz which eudev grep"
 short_desc="Btrfs filesystem utilities"
 maintainer="Enno Boland <gottox@voidlinux.org>"
 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=d41961b0a92160c80f894ad9a1882822889c2e1d084cbf3e08b8c214a5cf0137
 
 pre_build() {
 	if [ $CROSS_BUILD ]; then

  parent reply	other threads:[~2021-03-19 17:37 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-17 18:12 [PR PATCH] [WIP] " FollieHiyuki
2021-03-17 18:32 ` [PR PATCH] [Updated] " FollieHiyuki
2021-03-19 17:18 ` FollieHiyuki
2021-03-19 17:25 ` FollieHiyuki
2021-03-19 17:37 ` FollieHiyuki [this message]
2021-03-19 17:43 ` ericonr
2021-03-19 17:52 ` FollieHiyuki
2021-03-19 17:57 ` FollieHiyuki
2021-03-19 18:15 ` ericonr
2021-03-19 18:30 ` FollieHiyuki
2021-03-19 21:59 ` [PR PATCH] [Updated] " FollieHiyuki
2021-03-19 23:14 ` FollieHiyuki
2021-03-19 23:30 ` FollieHiyuki
2021-03-19 23:36 ` FollieHiyuki
2021-03-19 23:48 ` ericonr
2021-03-20  0:08 ` [PR PATCH] [Updated] " FollieHiyuki
2021-03-20  0:10 ` FollieHiyuki
2021-03-20  0:11 ` FollieHiyuki
2021-03-20  0:18 ` FollieHiyuki
2021-03-26 23:38 ` [PR PATCH] [Updated] " FollieHiyuki
2021-05-18  7:21 ` FollieHiyuki
2021-06-01 20:55 ` ologantr
2021-06-01 21:04 ` FollieHiyuki
2021-06-01 21:27 ` ologantr
2021-06-01 21:39 ` [PR PATCH] [Updated] " FollieHiyuki
2021-06-01 21:40 ` FollieHiyuki
2021-06-01 21:43 ` [PR PATCH] [Updated] " FollieHiyuki
2021-06-02  4:14 ` [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=20210319173720.zEJqLHrXaKrFbh5kREXMgq33qDIETR-Dzw77Oy7ybTU@z \
    --to=folliehiyuki@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).