From: Randy MacLeod <randy.macleod@windriver.com>
To: Wang Mingyu <wangmy@fujitsu.com>,
Alexander Kanavin <alex.kanavin@gmail.com>
Cc: openembedded-core@lists.openembedded.org, "Jia,
Hongxu" <Hongxu.Jia@windriver.com>
Subject: Re: [OE-core] [AUH] python3-rdflib: upgrading to 7.6.0 SUCCEEDED
Date: Tue, 24 Feb 2026 11:41:44 -0500 [thread overview]
Message-ID: <6733c658-47d6-488b-8f0a-ea19bf20df47@windriver.com> (raw)
In-Reply-To: <0101019c720ee382-b27e2993-68bf-4034-a5b8-1bc9fd0d4663-000000@us-west-2.amazonses.com>
[-- Attachment #1: Type: text/plain, Size: 4235 bytes --]
Hello Wang, and everyone,
Alex mentioned in the YP tech call today that he's on vacation starting
tomorrow, iirc.
Alex,
I assume that you won't be sending a patch series for the
succeeding AUH upgrades.
Wang,
Have you or do you plan to work on that?
If not, Hongxu and maybe others at WR will work on that.
I'm going to focus on the failed AUH upgrade set of recipes.
../Randy
On 2026-02-18 1:41 p.m., Auto Upgrade Helper via lists.openembedded.org
wrote:
> Hello,
>
> this email is a notification from the Auto Upgrade Helper
> that the automatic attempt to upgrade the recipe(s) *python3-rdflib* to *7.6.0* has Succeeded.
>
> Next steps:
> - apply the patch: git am 0001-python3-rdflib-upgrade-7.5.0-7.6.0.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 athttps://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler
>
> Regards,
> The Upgrade Helper
>
> -- >8 --
> From 6a230684782cbe47a4f0e5fe6c2268da57091fea Mon Sep 17 00:00:00 2001
> From: Upgrade Helper<auh@yoctoproject.org>
> Date: Wed, 18 Feb 2026 13:46:27 +0000
> Subject: [PATCH] python3-rdflib: upgrade 7.5.0 -> 7.6.0
>
> ---
> ...dflib_7.5.0.bb => python3-rdflib_7.6.0.bb} | 25 +++++++++++++++++--
> 1 file changed, 23 insertions(+), 2 deletions(-)
> rename meta/recipes-devtools/python/{python3-rdflib_7.5.0.bb => python3-rdflib_7.6.0.bb} (34%)
>
> diff --git a/meta/recipes-devtools/python/python3-rdflib_7.5.0.bb b/meta/recipes-devtools/python/python3-rdflib_7.6.0.bb
> similarity index 34%
> rename from meta/recipes-devtools/python/python3-rdflib_7.5.0.bb
> rename to meta/recipes-devtools/python/python3-rdflib_7.6.0.bb
> index e421aa2bac..1b830e8aa9 100644
> --- a/meta/recipes-devtools/python/python3-rdflib_7.5.0.bb
> +++ b/meta/recipes-devtools/python/python3-rdflib_7.6.0.bb
> @@ -1,10 +1,31 @@
> +# 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:
> +#
> +# --- LICENSE
> +# +++ LICENSE
> +# @@ -1,6 +1,6 @@
> +# BSD 3-Clause License
> +#
> +# -Copyright (c) 2002-2025, RDFLib Team
> +# +Copyright (c) 2002-2026, RDFLib Team
> +# All rights reserved.
> +#
> +# Redistribution and use in source and binary forms, with or without
> +#
> +#
> +
> SUMMARY = "RDFLib is a pure Python package for working with RDF"
> HOMEPAGE ="https://github.com/RDFLib/rdflib"
> SECTION = "devel/python"
> LICENSE = "BSD-3-Clause"
> -LIC_FILES_CHKSUM ="file://LICENSE;md5=7006e973486c4700556f6d58cba0ab6c"
> +LIC_FILES_CHKSUM ="file://LICENSE;md5=0ac0171cee5250c44d7d49847ae53a3e"
>
> -SRC_URI[sha256sum] = "663083443908b1830e567350d72e74d9948b310f827966358d76eebdc92bf592"
> +SRC_URI[sha256sum] = "6c831288d5e4a5a7ece85d0ccde9877d512a3d0f02d7c06455d00d6d0ea379df"
>
> inherit pypi python_poetry_core
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#231360):https://lists.openembedded.org/g/openembedded-core/message/231360
> Mute This Topic:https://lists.openembedded.org/mt/117879875/3616765
> Group Owner:openembedded-core+owner@lists.openembedded.org
> Unsubscribe:https://lists.openembedded.org/g/openembedded-core/unsub [randy.macleod@windriver.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
--
# Randy MacLeod
# Wind River Linux
[-- Attachment #2: Type: text/html, Size: 6090 bytes --]
next prev parent reply other threads:[~2026-02-24 16:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-18 18:41 [AUH] python3-rdflib: upgrading to 7.6.0 SUCCEEDED auh
2026-02-24 16:41 ` Randy MacLeod [this message]
2026-02-24 17:12 ` [OE-core] " Alexander Kanavin
2026-02-26 2:43 ` Hongxu Jia
2026-02-26 3:14 ` Mingyu Wang (Fujitsu)
2026-02-26 14:26 ` Randy MacLeod
2026-02-27 1:53 ` Mingyu Wang (Fujitsu)
2026-02-27 13:57 ` Randy MacLeod
2026-03-02 6:56 ` Hongxu Jia
2026-03-02 7:25 ` Mingyu Wang (Fujitsu)
2026-03-03 9:42 ` Mingyu Wang (Fujitsu)
2026-03-03 10:01 ` Hongxu Jia
2026-03-04 10:11 ` Alexander Kanavin
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=6733c658-47d6-488b-8f0a-ea19bf20df47@windriver.com \
--to=randy.macleod@windriver.com \
--cc=Hongxu.Jia@windriver.com \
--cc=alex.kanavin@gmail.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