Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-alabaster* to 
*0.7.13* has Succeeded.

Next steps:
    - apply the patch: git am 0001-python3-alabaster-upgrade-0.7.12-0.7.13.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/python3-alabaster: PKGV changed from 0.7.12 
[default] to 0.7.13 [default]
packages/core2-32-poky-linux/python3-alabaster: SRC_URI changed from 
"https://files.pythonhosted.org/packages/source/a/alabaster/alabaster-0.7.12.tar.gz";
 to 
"https://files.pythonhosted.org/packages/source/a/alabaster/alabaster-0.7.13.tar.gz";
packages/core2-32-poky-linux/python3-alabaster: PV changed from "0.7.12" to 
"0.7.13"
packages/core2-32-poky-linux/python3-alabaster/python3-alabaster-dbg: PKGV 
changed from 0.7.12 [default] to 0.7.13 [default]
packages/core2-32-poky-linux/python3-alabaster/python3-alabaster-dbg: PV 
changed from "0.7.12" to "0.7.13"
packages/core2-32-poky-linux/python3-alabaster/python3-alabaster-dev: PKGV 
changed from 0.7.12 [default] to 0.7.13 [default]
packages/core2-32-poky-linux/python3-alabaster/python3-alabaster-dev: PV 
changed from "0.7.12" to "0.7.13"
packages/core2-32-poky-linux/python3-alabaster/python3-alabaster-doc: PKGV 
changed from 0.7.12 [default] to 0.7.13 [default]
packages/core2-32-poky-linux/python3-alabaster/python3-alabaster-doc: PV 
changed from "0.7.12" to "0.7.13"
packages/core2-32-poky-linux/python3-alabaster/python3-alabaster-locale: PKGV 
changed from 0.7.12 [default] to 0.7.13 [default]
packages/core2-32-poky-linux/python3-alabaster/python3-alabaster-locale: PV 
changed from "0.7.12" to "0.7.13"
packages/core2-32-poky-linux/python3-alabaster/python3-alabaster-src: PKGV 
changed from 0.7.12 [default] to 0.7.13 [default]
packages/core2-32-poky-linux/python3-alabaster/python3-alabaster-src: PV 
changed from "0.7.12" to "0.7.13"
packages/core2-32-poky-linux/python3-alabaster/python3-alabaster-staticdev: 
PKGV changed from 0.7.12 [default] to 0.7.13 [default]
packages/core2-32-poky-linux/python3-alabaster/python3-alabaster-staticdev: PV 
changed from "0.7.12" to "0.7.13"
packages/core2-32-poky-linux/python3-alabaster/python3-alabaster: PKGV changed 
from 0.7.12 [default] to 0.7.13 [default]
packages/core2-32-poky-linux/python3-alabaster/python3-alabaster: PKGSIZE 
changed from 41215 to 42187 (+2%)
packages/core2-32-poky-linux/python3-alabaster/python3-alabaster: PV changed 
from "0.7.12" to "0.7.13"
Changes to packages/core2-32-poky-linux/python3-alabaster (sysroot):
  /usr/lib/python3.11/site-packages/alabaster-0.7.12.dist-info moved to 
/usr/lib/python3.11/site-packages/alabaster-0.7.13.dist-info
Changes to packages/core2-32-poky-linux/python3-alabaster (sysroot):
  /usr/lib/python3.11/site-packages/alabaster-0.7.12.dist-info moved to 
/usr/lib/python3.11/site-packages/alabaster-0.7.13.dist-info

Attachment: 0001-python3-alabaster-upgrade-0.7.12-0.7.13.patch
Description: Binary data

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#175895): 
https://lists.openembedded.org/g/openembedded-core/message/175895
Mute This Topic: https://lists.openembedded.org/mt/96290263/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to