From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Tim Orling <tim.orling@konsulko.com>
Cc: auh@yoctoproject.org, openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [AUH] python3-websockets: upgrading to 17.0 SUCCEEDED
Date: Sat, 01 Aug 2026 21:38:40 +0100 [thread overview]
Message-ID: <ed706c3879b38bb0e588725b3074f68008161949.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAOyo-84CvS6-hHAdU4T2+8PRs1U-N1-bwmrc-kbm-D-E+hf0hg@mail.gmail.com>
On Sat, 2026-08-01 at 13:07 -0700, Tim Orling wrote:
> On Fri, Jul 31, 2026 at 11:14 PM Richard Purdie <richard.purdie@linuxfoundation.org> wrote:
> > 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
> >
>
> This upgrade was already "on my list", so I will follow up on the
> ptest failures next week. Thank you for the feedback and the link.
Thanks, the newer version still has the ptest issue FWIW (with no ptest
results showing at all).
I've held off the uv-build upgrade as that doesn't work with the
current python3-crytopgraphy too!
Cheers,
Richard
next prev parent reply other threads:[~2026-08-01 20:38 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 ` [OE-core] " Richard Purdie
2026-08-01 20:07 ` Tim Orling
2026-08-01 20:38 ` Richard Purdie [this message]
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=ed706c3879b38bb0e588725b3074f68008161949.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