similarity index 30%
rename from meta/recipes-devtools/erofs-utils/erofs-utils_1.9.1.bb
rename to meta/recipes-devtools/erofs-utils/erofs-utils_1.9.2.bb
@@ -1,11 +1,51 @@
+# FIXME: the LIC_FILES_CHKSUM values have been updated by 'devtool upgrade'.
+# The following is the difference between the old and the new license text.
+# Please update the LICENSE value if needed, and summarize the changes in
+# the commit message via 'License-Update:' tag.
+# (example: 'License-Update: copyright years updated.')
+#
+# The changes:
+#
+# --- COPYING
+# +++ COPYING
+# @@ -1,15 +1,15 @@
+# -erofs-utils uses two different license patterns:
+# +erofs-utils uses two different licensing patterns:
+#
+# - - most liberofs files in `lib` and `include` directories
+# - use GPL-2.0+ OR Apache-2.0 dual license;
+# + - Most liberofs files in the `lib` and `include` directories
+# + use a dual GPL-2.0+ OR MIT license whenever possible.
+#
+# - - all other files use GPL-2.0+ license, unless
+# - explicitly stated otherwise.
+# + - All other files use the MIT license unless explicitly stated
+# + otherwise.
+#
+# -Relevant licenses can be found in the LICENSES directory.
+# +The relevant licenses can be found in the LICENSES directory.
+#
+# -This model is selected to emphasize that
+# -files in `lib` and `include` directory are designed to be included into
+# -3rd-party applications, while all other files, are intended to be used
+# -"as is", as part of their intended scenarios, with no intention to
+# -support 3rd-party integration use cases.
+# +This model was chosen to maximize the ability of erofs-utils to
+# +integrate with various ecosystems.
+# +
+# +However, liberofs uses a GPL-2.0+ OR MIT dual license because some
+# +parts should be shared with the Linux kernel.
+#
+#
+
SUMMARY = "Tools for erofs filesystems"
# liberofs also available under Apache 2.0
LICENSE = "GPL-2.0-or-later"
SECTION = "base"
-LIC_FILES_CHKSUM = "file://COPYING;md5=73001d804ea1e3d84365f652242cca20"
+LIC_FILES_CHKSUM = "file://COPYING;md5=63afa010baddc7d0905f9c31ac759f51"
HOMEPAGE = "https://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs-utils.git/tree/README"
-SRCREV = "d3fbccba6e409c100843563b416c47cd82c87ca0"
+SRCREV = "30711d4b2e234fe3e8aaeb779ade4cb609b0d920"
SRC_URI = "git://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs-utils.git;branch=master;protocol=https;tag=v${PV}"
UPSTREAM_CHECK_GITTAGREGEX = "v(?P<pver>(\d+(\.\d+)+))"
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe(s) *erofs-utils* to *1.9.2* has Succeeded. Next steps: - apply the patch: git am 0001-erofs-utils-upgrade-1.9.1-1.9.2.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 fe84ea3114d8e9f489d570a52b78f855c4b01315 Mon Sep 17 00:00:00 2001 From: Upgrade Helper <auh@yoctoproject.org> Date: Thu, 2 Jul 2026 05:20:13 +0000 Subject: [PATCH] erofs-utils: upgrade 1.9.1 -> 1.9.2 --- ...fs-utils_1.9.1.bb => erofs-utils_1.9.2.bb} | 44 ++++++++++++++++++- 1 file changed, 42 insertions(+), 2 deletions(-) rename meta/recipes-devtools/erofs-utils/{erofs-utils_1.9.1.bb => erofs-utils_1.9.2.bb} (30%)