From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: auh@yoctoproject.org, Ross Burton <ross.burton@arm.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [AUH] pango: upgrading to 1.56.1 SUCCEEDED
Date: Mon, 03 Feb 2025 16:24:42 +0000 [thread overview]
Message-ID: <db7915d3754efd75c2bc07fc5b81b9e8a3702adf.camel@linuxfoundation.org> (raw)
In-Reply-To: <01010194c1ac03e5-85b47374-6f7f-404a-91f5-949edd047468-000000@us-west-2.amazonses.com>
On Sat, 2025-02-01 at 13:21 +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) *pango* to *1.56.1* has Succeeded.
>
> Next steps:
> - apply the patch: git am 0001-pango-upgrade-1.55.5-1.56.1.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
>
FWIW this has docs issues:
https://autobuilder.yoctoproject.org/valkyrie/#/builders/17/builds/856/steps/11/logs/stdio
Cheers,
Richard
prev parent reply other threads:[~2025-02-03 16:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-01 13:21 [AUH] pango: upgrading to 1.56.1 SUCCEEDED auh
2025-02-03 16:24 ` Richard Purdie [this message]
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=db7915d3754efd75c2bc07fc5b81b9e8a3702adf.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=auh@yoctoproject.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.