From: auh@yoctoproject.org
To: Wang Mingyu <wangmy@fujitsu.com>
Cc: openembedded-core@lists.openembedded.org
Subject: [AUH] btrfs-tools: upgrading to 6.8.1 SUCCEEDED
Date: Wed, 15 May 2024 17:32:16 +0000 [thread overview]
Message-ID: <0101018f7d4fdc9b-d465dbdd-317a-449b-a303-450880fcbbe1-000000@us-west-2.amazonses.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3147 bytes --]
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *btrfs-tools* to *6.8.1* has Succeeded.
Next steps:
- apply the patch: git am 0001-btrfs-tools-upgrade-6.8-6.8.1.patch
- check the changes to upstream patches and summarize them in the commit message,
- compile an image that contains the package
- perform some basic sanity tests
- amend the patch and sign it off: git commit -s --reset-author --amend
- send it to the appropriate mailing list
Alternatively, if you believe the recipe should not be upgraded at this time,
you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that
automatic upgrades would no longer be attempted.
Please review the attached files for further information and build/update failures.
Any problem please file a bug at https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler
Regards,
The Upgrade Helper
-- >8 --
From 97d9d4386f556930262d9ea157ad4af1008ccb38 Mon Sep 17 00:00:00 2001
From: Upgrade Helper <auh@yoctoproject.org>
Date: Wed, 15 May 2024 08:18:29 +0000
Subject: [PATCH] btrfs-tools: upgrade 6.8 -> 6.8.1
---
...1-Add-a-possibility-to-specify-where-python-modules-ar.patch | 2 +-
.../btrfs-tools/{btrfs-tools_6.8.bb => btrfs-tools_6.8.1.bb} | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-devtools/btrfs-tools/{btrfs-tools_6.8.bb => btrfs-tools_6.8.1.bb} (98%)
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 4b1797b65f..756044628f 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 980f6edc269fa3ef8d4d4b9cd1aada2328131c19 Mon Sep 17 00:00:00 2001
+From 09f4a939d26331c3c2e2dec2a3edb6d4c07ef92f 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
diff --git a/meta/recipes-devtools/btrfs-tools/btrfs-tools_6.8.bb b/meta/recipes-devtools/btrfs-tools/btrfs-tools_6.8.1.bb
similarity index 98%
rename from meta/recipes-devtools/btrfs-tools/btrfs-tools_6.8.bb
rename to meta/recipes-devtools/btrfs-tools/btrfs-tools_6.8.1.bb
index 15cc7ac244..fac9f8f7ef 100644
--- a/meta/recipes-devtools/btrfs-tools/btrfs-tools_6.8.bb
+++ b/meta/recipes-devtools/btrfs-tools/btrfs-tools_6.8.1.bb
@@ -18,7 +18,7 @@ DEPENDS = "util-linux zlib"
SRC_URI = "git://git.kernel.org/pub/scm/linux/kernel/git/kdave/btrfs-progs.git;branch=master;protocol=https \
file://0001-Add-a-possibility-to-specify-where-python-modules-ar.patch \
"
-SRCREV = "3793e987d2b4e878410da16f33d963043d137d48"
+SRCREV = "5d97c32d6f94cf6f473a5f82964e3edaeb1b146e"
S = "${WORKDIR}/git"
PACKAGECONFIG ??= " \
--
2.44.0
[-- Attachment #2: 0001-btrfs-tools-upgrade-6.8-6.8.1.patch --]
[-- Type: application/octet-stream, Size: 2172 bytes --]
From 97d9d4386f556930262d9ea157ad4af1008ccb38 Mon Sep 17 00:00:00 2001
From: Upgrade Helper <auh@yoctoproject.org>
Date: Wed, 15 May 2024 08:18:29 +0000
Subject: [PATCH] btrfs-tools: upgrade 6.8 -> 6.8.1
---
...1-Add-a-possibility-to-specify-where-python-modules-ar.patch | 2 +-
.../btrfs-tools/{btrfs-tools_6.8.bb => btrfs-tools_6.8.1.bb} | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-devtools/btrfs-tools/{btrfs-tools_6.8.bb => btrfs-tools_6.8.1.bb} (98%)
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 4b1797b65f..756044628f 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 980f6edc269fa3ef8d4d4b9cd1aada2328131c19 Mon Sep 17 00:00:00 2001
+From 09f4a939d26331c3c2e2dec2a3edb6d4c07ef92f 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
diff --git a/meta/recipes-devtools/btrfs-tools/btrfs-tools_6.8.bb b/meta/recipes-devtools/btrfs-tools/btrfs-tools_6.8.1.bb
similarity index 98%
rename from meta/recipes-devtools/btrfs-tools/btrfs-tools_6.8.bb
rename to meta/recipes-devtools/btrfs-tools/btrfs-tools_6.8.1.bb
index 15cc7ac244..fac9f8f7ef 100644
--- a/meta/recipes-devtools/btrfs-tools/btrfs-tools_6.8.bb
+++ b/meta/recipes-devtools/btrfs-tools/btrfs-tools_6.8.1.bb
@@ -18,7 +18,7 @@ DEPENDS = "util-linux zlib"
SRC_URI = "git://git.kernel.org/pub/scm/linux/kernel/git/kdave/btrfs-progs.git;branch=master;protocol=https \
file://0001-Add-a-possibility-to-specify-where-python-modules-ar.patch \
"
-SRCREV = "3793e987d2b4e878410da16f33d963043d137d48"
+SRCREV = "5d97c32d6f94cf6f473a5f82964e3edaeb1b146e"
S = "${WORKDIR}/git"
PACKAGECONFIG ??= " \
--
2.44.0
[-- Attachment #3: buildhistory-diff-full.txt --]
[-- Type: text/plain, Size: 2945 bytes --]
packages/core2-64-poky-linux/btrfs-tools/btrfs-tools-dbg: PV changed from "6.8" to "6.8.1"
packages/core2-64-poky-linux/btrfs-tools/btrfs-tools-dbg: PKGSIZE changed from 25049752 to 25055168 (+0%)
packages/core2-64-poky-linux/btrfs-tools/btrfs-tools-dbg: PKGV changed from 6.8 [default] to 6.8.1 [default]
packages/core2-64-poky-linux/btrfs-tools/btrfs-tools-dev: PV changed from "6.8" to "6.8.1"
packages/core2-64-poky-linux/btrfs-tools/btrfs-tools-dev: PKGSIZE changed from 218986 to 218990 (+0%)
packages/core2-64-poky-linux/btrfs-tools/btrfs-tools-dev: PKGV changed from 6.8 [default] to 6.8.1 [default]
packages/core2-64-poky-linux/btrfs-tools/btrfs-tools-doc: PV changed from "6.8" to "6.8.1"
packages/core2-64-poky-linux/btrfs-tools/btrfs-tools-doc: PKGV changed from 6.8 [default] to 6.8.1 [default]
packages/core2-64-poky-linux/btrfs-tools/btrfs-tools-locale: PV changed from "6.8" to "6.8.1"
packages/core2-64-poky-linux/btrfs-tools/btrfs-tools-locale: PKGV changed from 6.8 [default] to 6.8.1 [default]
packages/core2-64-poky-linux/btrfs-tools/btrfs-tools-src: PV changed from "6.8" to "6.8.1"
packages/core2-64-poky-linux/btrfs-tools/btrfs-tools-src: PKGSIZE changed from 4179121 to 4179759 (+0%)
packages/core2-64-poky-linux/btrfs-tools/btrfs-tools-src: PKGV changed from 6.8 [default] to 6.8.1 [default]
packages/core2-64-poky-linux/btrfs-tools/btrfs-tools-staticdev: PV changed from "6.8" to "6.8.1"
packages/core2-64-poky-linux/btrfs-tools/btrfs-tools-staticdev: PKGV changed from 6.8 [default] to 6.8.1 [default]
packages/core2-64-poky-linux/btrfs-tools/btrfs-tools: PV changed from "6.8" to "6.8.1"
packages/core2-64-poky-linux/btrfs-tools/btrfs-tools: PKGSIZE changed from 5824850 to 5828948 (+0%)
packages/core2-64-poky-linux/btrfs-tools/btrfs-tools: PKGV changed from 6.8 [default] to 6.8.1 [default]
packages/core2-64-poky-linux/btrfs-tools: PKGV changed from 6.8 [default] to 6.8.1 [default]
packages/core2-64-poky-linux/btrfs-tools: PV changed from "6.8" to "6.8.1"
Changes to packages/core2-64-poky-linux/btrfs-tools (sysroot):
/usr/lib/python3.12/site-packages/btrfsutil-6.8.1-py3.12.egg-info was added
/usr/lib/python3.12/site-packages/btrfsutil-6.8.1-py3.12.egg-info/dependency_links.txt was added
/usr/lib/python3.12/site-packages/btrfsutil-6.8.1-py3.12.egg-info/PKG-INFO was added
/usr/lib/python3.12/site-packages/btrfsutil-6.8.1-py3.12.egg-info/SOURCES.txt was added
/usr/lib/python3.12/site-packages/btrfsutil-6.8.1-py3.12.egg-info/top_level.txt was added
/usr/lib/python3.12/site-packages/btrfsutil-6.8-py3.12.egg-info was removed
/usr/lib/python3.12/site-packages/btrfsutil-6.8-py3.12.egg-info/dependency_links.txt was removed
/usr/lib/python3.12/site-packages/btrfsutil-6.8-py3.12.egg-info/PKG-INFO was removed
/usr/lib/python3.12/site-packages/btrfsutil-6.8-py3.12.egg-info/SOURCES.txt was removed
/usr/lib/python3.12/site-packages/btrfsutil-6.8-py3.12.egg-info/top_level.txt was removed
[-- Attachment #4: buildhistory-diff.txt --]
[-- Type: text/plain, Size: 955 bytes --]
Changes to packages/core2-64-poky-linux/btrfs-tools (sysroot):
/usr/lib/python3.12/site-packages/btrfsutil-6.8.1-py3.12.egg-info was added
/usr/lib/python3.12/site-packages/btrfsutil-6.8.1-py3.12.egg-info/dependency_links.txt was added
/usr/lib/python3.12/site-packages/btrfsutil-6.8.1-py3.12.egg-info/PKG-INFO was added
/usr/lib/python3.12/site-packages/btrfsutil-6.8.1-py3.12.egg-info/SOURCES.txt was added
/usr/lib/python3.12/site-packages/btrfsutil-6.8.1-py3.12.egg-info/top_level.txt was added
/usr/lib/python3.12/site-packages/btrfsutil-6.8-py3.12.egg-info was removed
/usr/lib/python3.12/site-packages/btrfsutil-6.8-py3.12.egg-info/dependency_links.txt was removed
/usr/lib/python3.12/site-packages/btrfsutil-6.8-py3.12.egg-info/PKG-INFO was removed
/usr/lib/python3.12/site-packages/btrfsutil-6.8-py3.12.egg-info/SOURCES.txt was removed
/usr/lib/python3.12/site-packages/btrfsutil-6.8-py3.12.egg-info/top_level.txt was removed
reply other threads:[~2024-05-15 17:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=0101018f7d4fdc9b-d465dbdd-317a-449b-a303-450880fcbbe1-000000@us-west-2.amazonses.com \
--to=auh@yoctoproject.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).