From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: wangmy <wangmy@fujitsu.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] btrfs-tools: upgrade 6.1.3 -> 6.2
Date: Thu, 2 Mar 2023 12:55:41 +0100 [thread overview]
Message-ID: <ZACOvSVKmQ+n1P0K@mail.local> (raw)
In-Reply-To: <1677717540-2052-1-git-send-email-wangmy@fujitsu.com>
This fails on the AB:
stdio: ERROR: btrfs-tools-6.2-r0 do_fetch: Fetcher failure: Unable to find revision 6439e92cba81c068afca76f8e010fb7175620176 in branch master even from upstream
stdio: ERROR: btrfs-tools-6.2-r0 do_fetch: Bitbake Fetcher Error: FetchError('Unable to fetch URL from any source.', 'git://git.kernel.org/pub/scm/linux/kernel/git/kdave/btrfs-progs.git;branch=master')
On 02/03/2023 08:39:00+0800, wangmy wrote:
> From: Wang Mingyu <wangmy@fujitsu.com>
>
> Changelog:
> ==========
> * receive: fix a corruption when decompressing zstd extents
> * subvol sync: print total number and deletion progress
> * accelerated hash algorithm implementations in fallback mode on x86_64
> * fi mkswapfile: new option --uuid
> * new global option --log=level to set the verbosity level directly
> * other:
> * experimental: update checksum conversion (not usable yet)
> * build actually requires -std=gnu11
> * refactor help option formatting, auto wrap long lines
>
> Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
> ---
> .../btrfs-tools/{btrfs-tools_6.1.3.bb => btrfs-tools_6.2.bb} | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
> rename meta/recipes-devtools/btrfs-tools/{btrfs-tools_6.1.3.bb => btrfs-tools_6.2.bb} (98%)
>
> diff --git a/meta/recipes-devtools/btrfs-tools/btrfs-tools_6.1.3.bb b/meta/recipes-devtools/btrfs-tools/btrfs-tools_6.2.bb
> similarity index 98%
> rename from meta/recipes-devtools/btrfs-tools/btrfs-tools_6.1.3.bb
> rename to meta/recipes-devtools/btrfs-tools/btrfs-tools_6.2.bb
> index b4dfc5b3f3..4e3d544fad 100644
> --- a/meta/recipes-devtools/btrfs-tools/btrfs-tools_6.1.3.bb
> +++ b/meta/recipes-devtools/btrfs-tools/btrfs-tools_6.2.bb
> @@ -19,7 +19,7 @@ SRC_URI = "git://git.kernel.org/pub/scm/linux/kernel/git/kdave/btrfs-progs.git;b
> file://0001-Add-a-possibility-to-specify-where-python-modules-ar.patch \
> file://0001-Use-pread-pwrite-ftruncate-stat-instead-of-64bit-equ.patch \
> "
> -SRCREV = "908b4b4450320e30fdef693f09b42f4eb93702c3"
> +SRCREV = "6439e92cba81c068afca76f8e010fb7175620176"
> S = "${WORKDIR}/git"
>
> PACKAGECONFIG ??= " \
> --
> 2.34.1
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#177952): https://lists.openembedded.org/g/openembedded-core/message/177952
> Mute This Topic: https://lists.openembedded.org/mt/97329642/3617179
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [alexandre.belloni@bootlin.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2023-03-02 11:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-02 0:39 [OE-core] [PATCH] btrfs-tools: upgrade 6.1.3 -> 6.2 wangmy
2023-03-02 11:55 ` Alexandre Belloni [this message]
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=ZACOvSVKmQ+n1P0K@mail.local \
--to=alexandre.belloni@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=wangmy@fujitsu.com \
/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