All of lore.kernel.org
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: richard.purdie@linuxfoundation.org,
	openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 05/48] btrfs-tools: upgrade 6.13 -> 6.14
Date: Wed, 2 Apr 2025 18:00:00 -0700	[thread overview]
Message-ID: <b8326eea-a748-42ad-922c-d0fcf961bc27@gmail.com> (raw)
In-Reply-To: <20250402071017.2157620-5-richard.purdie@linuxfoundation.org>

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


On 4/2/25 12:09 AM, Richard Purdie via lists.openembedded.org wrote:
> Add tag to SRC_URI to verify SRCREV.
>
> Drop patch merged upstream.
>
> Signed-off-by: Richard Purdie<richard.purdie@linuxfoundation.org>
> ---
>   ...y-to-specify-where-python-modules-ar.patch |  6 +--
>   ...dd-break-to-case-BTRFS_COMPRESS_NONE.patch | 40 -------------------
>   ...trfs-tools_6.13.bb => btrfs-tools_6.14.bb} |  5 +--
>   3 files changed, 5 insertions(+), 46 deletions(-)
>   delete mode 100644 meta/recipes-devtools/btrfs-tools/btrfs-tools/0001-mkfs-add-break-to-case-BTRFS_COMPRESS_NONE.patch
>   rename meta/recipes-devtools/btrfs-tools/{btrfs-tools_6.13.bb => btrfs-tools_6.14.bb} (95%)
>
> diff --git a/meta/recipes-devtools/btrfs-tools/btrfs-tools/0001-Add-a-possibility-to-specify-where-python-modules-ar.patch b/meta/recipes-devtools/btrfs-tools/btrfs-tools/0001-Add-a-possibility-to-specify-where-python-modules-ar.patch
> index 59ea5a66dac..2cd66d2722a 100644
> --- a/meta/recipes-devtools/btrfs-tools/btrfs-tools/0001-Add-a-possibility-to-specify-where-python-modules-ar.patch
> +++ b/meta/recipes-devtools/btrfs-tools/btrfs-tools/0001-Add-a-possibility-to-specify-where-python-modules-ar.patch
> @@ -1,4 +1,4 @@
> -From 76e635a56c5973671da3a8a2fd4fc32e823bf8c9 Mon Sep 17 00:00:00 2001
> +From 030ec81c0dac1e067faf49924d5631bb22ccc90d Mon Sep 17 00:00:00 2001
>   From: Alexander Kanavin<alex.kanavin@gmail.com>
>   Date: Wed, 23 May 2018 21:20:35 +0300
>   Subject: [PATCH] Add a possibility to specify where python modules are
> @@ -11,10 +11,10 @@ Signed-off-by: Alexander Kanavin<alex.kanavin@gmail.com>
>    1 file changed, 1 insertion(+), 1 deletion(-)
>   
>   diff --git a/Makefile b/Makefile
> -index 2f8d2fa0..c760e5ae 100644
> +index 7e36aa42..edff7d5b 100644
>   --- a/Makefile
>   +++ b/Makefile
> -@@ -985,7 +985,7 @@ endif
> +@@ -996,7 +996,7 @@ endif
>    ifeq ($(PYTHON_BINDINGS),1)
>    install_python: libbtrfsutil_python
>    	$(Q)cd libbtrfsutil/python; \
> diff --git a/meta/recipes-devtools/btrfs-tools/btrfs-tools/0001-mkfs-add-break-to-case-BTRFS_COMPRESS_NONE.patch b/meta/recipes-devtools/btrfs-tools/btrfs-tools/0001-mkfs-add-break-to-case-BTRFS_COMPRESS_NONE.patch
> deleted file mode 100644
> index 750ba830740..00000000000
> --- a/meta/recipes-devtools/btrfs-tools/btrfs-tools/0001-mkfs-add-break-to-case-BTRFS_COMPRESS_NONE.patch
> +++ /dev/null
> @@ -1,40 +0,0 @@
> -From ae0743dea3498429fce144e75c8b5b6eeed6f490 Mon Sep 17 00:00:00 2001
> -From: Wang Mingyu<wangmy@fujitsu.com>
> -Date: Tue, 11 Mar 2025 05:24:54 +0000
> -Subject: [PATCH] mkfs: add break to case BTRFS_COMPRESS_NONE
> -
> -when compression null, always through error "lzo support not compiled in"
> -
> -This bug was imported by following commit:
> -----------------------------------------------------
> -commit c6d24a363daed6501d13d9125c560387e2d755ca
> -Author: Mark Harmstone<maharmstone@fb.com>
> -Date:   Thu Dec 12 20:36:55 2024 +0000
> -
> -     btrfs-progs: mkfs: add lzo to --compress option
> -
> -     Allow --compress to work with lzo.
> -----------------------------------------------------
> -
> -Upstream-Status: Submitted [https://github.com/kdave/btrfs-progs/pull/967]
> -
> -Signed-off-by: Wang Mingyu<wangmy@fujitsu.com>
> ----
> - mkfs/rootdir.c | 1 +
> - 1 file changed, 1 insertion(+)
> -
> -diff --git a/mkfs/rootdir.c b/mkfs/rootdir.c
> -index 1927394..5f4cfb9 100644
> ---- a/mkfs/rootdir.c
> -+++ b/mkfs/rootdir.c
> -@@ -1654,6 +1654,7 @@ int btrfs_mkfs_fill_dir(struct btrfs_trans_handle *trans, const char *source_dir
> -
> - 	switch (compression) {
> - 	case BTRFS_COMPRESS_NONE:
> -+                break;
> - 	case BTRFS_COMPRESS_LZO:
> - #if !COMPRESSION_LZO
> - 		error("lzo support not compiled in");
> ---
> -2.43.0
> -
> diff --git a/meta/recipes-devtools/btrfs-tools/btrfs-tools_6.13.bb b/meta/recipes-devtools/btrfs-tools/btrfs-tools_6.14.bb
> similarity index 95%
> rename from meta/recipes-devtools/btrfs-tools/btrfs-tools_6.13.bb
> rename to meta/recipes-devtools/btrfs-tools/btrfs-tools_6.14.bb
> index d73d86ba8ae..cee1fdfd556 100644
> --- a/meta/recipes-devtools/btrfs-tools/btrfs-tools_6.13.bb
> +++ b/meta/recipes-devtools/btrfs-tools/btrfs-tools_6.14.bb
> @@ -15,11 +15,10 @@ LIC_FILES_CHKSUM = " \
>   SECTION = "base"
>   DEPENDS = "util-linux zlib"
>   
> -SRC_URI = "git://github.com/kdave/btrfs-progs.git;branch=master;protocol=https \
> +SRC_URI = "git://github.com/kdave/btrfs-progs.git;branch=master;protocol=https;tar=v${PV} \

what does tar= option do ? is it intentional here ?

>              file://0001-Add-a-possibility-to-specify-where-python-modules-ar.patch \
> -file://0001-mkfs-add-break-to-case-BTRFS_COMPRESS_NONE.patch \
>              "
> -SRCREV = "26e4d9174c70aac0e53c3b5de55cf159f8d9397f"
> +SRCREV = "5ad147c9ec00e657393c85b195c9bcc0f4c35a54"
>   S = "${WORKDIR}/git"
>   
>   PACKAGECONFIG ??= " \
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#214178):https://lists.openembedded.org/g/openembedded-core/message/214178
> Mute This Topic:https://lists.openembedded.org/mt/112042561/1997914
> Group Owner:openembedded-core+owner@lists.openembedded.org
> Unsubscribe:https://lists.openembedded.org/g/openembedded-core/unsub [raj.khem@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
-- 
-Khem

[-- Attachment #2: Type: text/html, Size: 7109 bytes --]

  parent reply	other threads:[~2025-04-03  1:00 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-02  7:09 [PATCH 01/48] at-spi2-core: upgrade 2.56.0 -> 2.56.1 Richard Purdie
2025-04-02  7:09 ` [PATCH 02/48] barebox-tools: upgrade 2025.02.0 -> 2025.03.0 Richard Purdie
2025-04-02  7:09 ` [PATCH 03/48] base-passwd: upgrade 3.6.6 -> 3.6.7 Richard Purdie
2025-04-02  7:09 ` [PATCH 04/48] bind: upgrade 9.20.6 -> 9.20.7 Richard Purdie
2025-04-02  7:09 ` [PATCH 05/48] btrfs-tools: upgrade 6.13 -> 6.14 Richard Purdie
2025-04-02  7:17   ` [OE-core] " Alexander Kanavin
2025-04-02  8:32     ` Richard Purdie
2025-04-03  1:00   ` Khem Raj [this message]
2025-04-02  7:09 ` [PATCH 06/48] ccache: upgrade 4.11 -> 4.11.2 Richard Purdie
2025-04-02  7:09 ` [PATCH 07/48] connman: upgrade 1.43 -> 1.44 Richard Purdie
2025-04-02  7:09 ` [PATCH 08/48] createrepo-c: upgrade 1.2.0 -> 1.2.1 Richard Purdie
2025-04-02  7:09 ` [PATCH 09/48] diffoscope: upgrade 289 -> 293 Richard Purdie
2025-04-02  7:09 ` [PATCH 10/48] ed: upgrade 1.21 -> 1.21.1 Richard Purdie
2025-04-02  7:09 ` [PATCH 11/48] ell: upgrade 0.74 -> 0.75 Richard Purdie
2025-04-02  7:09 ` [PATCH 12/48] gtk4: upgrade 4.18.1 -> 4.18.3 Richard Purdie
2025-04-02  7:09 ` [PATCH 13/48] harfbuzz: upgrade 10.4.0 -> 11.0.0 Richard Purdie
2025-04-02  7:09 ` [PATCH 14/48] iproute2: upgrade 6.13.0 -> 6.14.0 Richard Purdie
2025-04-02  7:09 ` [PATCH 15/48] kmod: upgrade 34.1 -> 34.2 Richard Purdie
2025-04-02  7:09 ` [PATCH 16/48] libevdev: upgrade 1.13.3 -> 1.13.4 Richard Purdie
2025-04-02  7:09 ` [PATCH 17/48] libinput: upgrade 1.27.1 -> 1.28.1 Richard Purdie
2025-04-02  7:09 ` [PATCH 18/48] libnotify: upgrade 0.8.4 -> 0.8.6 Richard Purdie
2025-04-02  7:09 ` [PATCH 19/48] libsdl2: upgrade 2.32.2 -> 2.32.4 Richard Purdie
2025-04-02  7:09 ` [PATCH 20/48] libsoup: upgrade 3.6.4 -> 3.6.5 Richard Purdie
2025-04-02  7:09 ` [PATCH 21/48] libusb1: upgrade 1.0.27 -> 1.0.28 Richard Purdie
2025-04-02  7:09 ` [PATCH 22/48] lighttpd: upgrade 1.4.77 -> 1.4.78 Richard Purdie
2025-04-02  7:09 ` [PATCH 23/48] llvm: upgrade 20.1.0 -> 20.1.1 Richard Purdie
2025-04-02  7:09 ` [PATCH 24/48] mpfr: upgrade 4.2.1 -> 4.2.2 Richard Purdie
2025-04-02  7:09 ` [PATCH 25/48] ofono: upgrade 2.15 -> 2.16 Richard Purdie
2025-04-02  7:09 ` [PATCH 26/48] pango: upgrade 1.56.2 -> 1.56.3 Richard Purdie
2025-04-02  7:09 ` [PATCH 27/48] piglit: upgrade to latest revision Richard Purdie
2025-04-02  7:09 ` [PATCH 28/48] python3-beartype: upgrade 0.20.0 -> 0.20.2 Richard Purdie
2025-04-02  7:09 ` [PATCH 29/48] python3-calver: upgrade 2022.6.26 -> 2025.04.01 Richard Purdie
2025-04-02  7:09 ` [PATCH 30/48] python3-numpy: upgrade 2.2.3 -> 2.2.4 Richard Purdie
2025-04-02  7:10 ` [PATCH 31/48] python3-poetry-core: upgrade 2.1.1 -> 2.1.2 Richard Purdie
2025-04-02  7:10 ` [PATCH 32/48] python3-pygobject: upgrade 3.52.2 -> 3.52.3 Richard Purdie
2025-04-02  7:10 ` [PATCH 33/48] python3-pyparsing: upgrade 3.2.1 -> 3.2.3 Richard Purdie
2025-04-02  7:10 ` [PATCH 34/48] python3-pytz: upgrade 2025.1 -> 2025.2 Richard Purdie
2025-04-02  7:10 ` [PATCH 35/48] python3-rdflib: upgrade 7.1.3 -> 7.1.4 Richard Purdie
2025-04-02  7:10 ` [PATCH 36/48] python3-rpds-py: upgrade 0.22.3 -> 0.24.0 Richard Purdie
2025-04-02  7:10 ` [PATCH 37/48] python3-scons: upgrade 4.9.0 -> 4.9.1 Richard Purdie
2025-04-02  7:10 ` [PATCH 38/48] python3-setuptools-scm: upgrade 8.2.0 -> 8.2.1 Richard Purdie
2025-04-02  7:10 ` [PATCH 39/48] python3-setuptools: upgrade 76.0.0 -> 78.1.0 Richard Purdie
2025-04-02  7:10 ` [PATCH 40/48] python3-trove-classifiers: upgrade 2025.3.13.13 -> 2025.3.19.19 Richard Purdie
2025-04-02  7:10 ` [PATCH 41/48] python3-typing-extensions: upgrade 4.12.2 -> 4.13.0 Richard Purdie
2025-04-02  7:10 ` [PATCH 42/48] python3-yamllint: upgrade 1.36.0 -> 1.37.0 Richard Purdie
2025-04-02  7:10 ` [PATCH 43/48] qemu: Upgrade 9.2.0 -> 9.2.3 Richard Purdie
2025-04-02  7:10 ` [PATCH 44/48] repo: upgrade 2.52 -> 2.53 Richard Purdie
2025-04-02  7:10 ` [PATCH 45/48] shaderc: upgrade 2024.3 -> 2025.1 Richard Purdie
2025-04-02 13:45   ` [OE-core] " Mathieu Dubois-Briand
2025-04-02 13:50     ` Richard Purdie
2025-04-02  7:10 ` [PATCH 46/48] stress-ng: upgrade 0.18.11 -> 0.18.12 Richard Purdie
2025-04-02  7:10 ` [PATCH 47/48] sysklogd: upgrade 2.7.1 -> 2.7.2 Richard Purdie
2025-04-02  7:10 ` [PATCH 48/48] wayland-protocols: upgrade 1.41 -> 1.42 Richard Purdie

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=b8326eea-a748-42ad-922c-d0fcf961bc27@gmail.com \
    --to=raj.khem@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.