From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: auh@yoctoproject.org, Tim Orling <tim.orling@konsulko.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [AUH] python3-websockets: upgrading to 17.0 SUCCEEDED
Date: Sat, 01 Aug 2026 07:14:40 +0100 [thread overview]
Message-ID: <040de8e5eb3f8b57f00cfa691c8d5889103b7e50.camel@linuxfoundation.org> (raw)
In-Reply-To: <0101019fb18e1918-6e60db78-fa07-43d5-8bb5-0f1a3bf1758a-000000@us-west-2.amazonses.com>
On Thu, 2026-07-30 at 05:45 +0000, 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-websockets* to *17.0* has Succeeded.
>
> Next steps:
> - apply the patch: git am 0001-python3-websockets-upgrade-16.1.1-17.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 at https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler
>
> Regards,
> The Upgrade Helper
This creates ptest failures. I note a new point release in AUH today too.
https://autobuilder.yoctoproject.org/valkyrie/#/builders/56/builds/2047
Cheers,
Richard
next prev parent reply other threads:[~2026-08-01 6:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-30 5:45 [AUH] python3-websockets: upgrading to 17.0 SUCCEEDED auh
2026-08-01 6:14 ` Richard Purdie [this message]
2026-08-01 20:07 ` [OE-core] " Tim Orling
2026-08-01 20:38 ` Richard Purdie
2026-08-01 20:47 ` Tim Orling
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=040de8e5eb3f8b57f00cfa691c8d5889103b7e50.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=auh@yoctoproject.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=tim.orling@konsulko.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