Skip to contentSkip to conversation

erofs-utils: upgrading to 20191016 SUCCEEDED

AUH [email protected] 2 participants 2 messages Jun 3, 2021

lore
Share & tools
lore
#0 lore raw

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *erofs-utils* to *20191016* has Succeeded.

Next steps:
- apply the patch: git am 0001-erofs-utils-upgrade-1.2.1-20191016.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

packages/core2-32-poky-linux/erofs-utils/erofs-utils-dbg: PV changed from "1.2.1" to "20191016" packages/core2-32-poky-linux/erofs-utils/erofs-utils-dbg: PKGV changed from 1.2.1 [default] to 20191016 [default] packages/core2-32-poky-linux/erofs-utils/erofs-utils-dbg: PKGSIZE changed from 167228 to 167232 (+0%) packages/core2-32-poky-linux/erofs-utils/erofs-utils-dev: PV changed from "1.2.1" to "20191016" packages/core2-32-poky-linux/erofs-utils/erofs-utils-dev: PKGV changed from 1.2.1 [default] to 20191016 [default] packages/core2-32-poky-linux/erofs-utils/erofs-utils-doc: PV changed from "1.2.1" to "20191016" packages/core2-32-poky-linux/erofs-utils/erofs-utils-doc: PKGV changed from 1.2.1 [default] to 20191016 [default] packages/core2-32-poky-linux/erofs-utils/erofs-utils-locale: PV changed from "1.2.1" to "20191016" packages/core2-32-poky-linux/erofs-utils/erofs-utils-locale: PKGV changed from 1.2.1 [default] to 20191016 [default] packages/core2-32-poky-linux/erofs-utils/erofs-utils-src: PV changed from "1.2.1" to "20191016" packages/core2-32-poky-linux/erofs-utils/erofs-utils-src: PKGV changed from 1.2.1 [default] to 20191016 [default] packages/core2-32-poky-linux/erofs-utils/erofs-utils-staticdev: PV changed from "1.2.1" to "20191016" packages/core2-32-poky-linux/erofs-utils/erofs-utils-staticdev: PKGV changed from 1.2.1 [default] to 20191016 [default] packages/core2-32-poky-linux/erofs-utils/erofs-utils: PV changed from "1.2.1" to "20191016" packages/core2-32-poky-linux/erofs-utils/erofs-utils: PKGV changed from 1.2.1 [default] to 20191016 [default] packages/core2-32-poky-linux/erofs-utils: PV changed from "1.2.1" to "20191016" packages/core2-32-poky-linux/erofs-utils: PKGV changed from 1.2.1 [default] to 20191016 [default]

From dce7793cff90c96310f4e2eaf85f31219fdfc2c8 Mon Sep 17 00:00:00 2001
From: Upgrade Helper <[email protected]>
Date: Wed, 2 Jun 2021 16:16:54 +0000
Subject: [PATCH] erofs-utils: upgrade 1.2.1 -> 20191016

---
 .../erofs-utils/{erofs-utils_1.2.1.bb => erofs-utils_20191016.bb} | 0
 1 file changed, 0 insertions(+), 0 deletions(-)
 rename meta/recipes-devtools/erofs-utils/{erofs-utils_1.2.1.bb => erofs-utils_20191016.bb} (100%)
meta/recipes-devtools/erofs-utils/erofs-utils_20191016.bb renamed from meta/recipes-devtools/erofs-utils/erofs-utils_1.2.1.bb +0 -0
similarity index 100%
rename from meta/recipes-devtools/erofs-utils/erofs-utils_1.2.1.bb
rename to meta/recipes-devtools/erofs-utils/erofs-utils_20191016.bb
Signature · 1 line
2.17.1
#1 lore raw

Bogus tag, please ignore. I have queued a patch to correct this. (there is currently no new version to update to)

Alex

Quoted 31 lines · On Thu, 3 Jun 2021 at 03:24, <[email protected]> wrote:

Hello,

this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *erofs-utils* to *20191016* has Succeeded.

Next steps:
- apply the patch: git am 0001-erofs-utils-upgrade-1.2.1-20191016.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