From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: wangmy <wangmy@fujitsu.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] enchant2: upgrade 2.3.3 -> 2.3.4
Date: Tue, 28 Feb 2023 23:17:38 +0100 [thread overview]
Message-ID: <Y/59glKJ9prAGatj@mail.local> (raw)
In-Reply-To: <1677577759-20868-2-git-send-email-wangmy@fujitsu.com>
Hello,
This failed on the autobuilders:
https://autobuilder.yoctoproject.org/typhoon/#/builders/117/builds/2471/steps/12/logs/stdio
https://autobuilder.yoctoproject.org/typhoon/#/builders/64/builds/6734/steps/11/logs/errors
On 28/02/2023 17:49:16+0800, wangmy wrote:
> From: Wang Mingyu <wangmy@fujitsu.com>
>
> Changelog:
> ===========
> - Document the personal wordlist format.
> - Improve the man pages in various ways, and make online versions, now linked
> from the web site.
> - Fix some potential crashes (double-free and NULL dereferences).
> - Update the build system to use autoconf 2.71.
>
> Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
> ---
> .../enchant/{enchant2_2.3.3.bb => enchant2_2.3.4.bb} | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
> rename meta/recipes-support/enchant/{enchant2_2.3.3.bb => enchant2_2.3.4.bb} (92%)
>
> diff --git a/meta/recipes-support/enchant/enchant2_2.3.3.bb b/meta/recipes-support/enchant/enchant2_2.3.4.bb
> similarity index 92%
> rename from meta/recipes-support/enchant/enchant2_2.3.3.bb
> rename to meta/recipes-support/enchant/enchant2_2.3.4.bb
> index c892f570c4..fe28d323c2 100644
> --- a/meta/recipes-support/enchant/enchant2_2.3.3.bb
> +++ b/meta/recipes-support/enchant/enchant2_2.3.4.bb
> @@ -12,7 +12,7 @@ DEPENDS = "glib-2.0"
> inherit autotools pkgconfig github-releases
>
> SRC_URI = "${GITHUB_BASE_URI}/download/v${PV}/enchant-${PV}.tar.gz"
> -SRC_URI[sha256sum] = "3da12103f11cf49c3cf2fd2ce3017575c5321a489e5b9bfa81dd91ec413f3891"
> +SRC_URI[sha256sum] = "1f7e26744db1c9a0fea61d2169f4e5c1ce435cf8c2731c37e3e4054119e994a0"
>
> GITHUB_BASE_URI = "https://github.com/AbiWord/enchant/releases"
>
> --
> 2.34.1
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#177827): https://lists.openembedded.org/g/openembedded-core/message/177827
> Mute This Topic: https://lists.openembedded.org/mt/97287062/3617179
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [alexandre.belloni@bootlin.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2023-02-28 22:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-28 9:49 [OE-core] [PATCH] diffoscope: upgrade 235 -> 236 wangmy
2023-02-28 9:49 ` [OE-core] [PATCH] enchant2: upgrade 2.3.3 -> 2.3.4 wangmy
2023-02-28 22:17 ` Alexandre Belloni [this message]
2023-02-28 9:49 ` [OE-core] [PATCH] libnotify: upgrade 0.8.1 -> 0.8.2 wangmy
2023-03-01 8:53 ` Alexandre Belloni
2023-02-28 9:49 ` [OE-core] [PATCH] python3-more-itertools: upgrade 9.0.0 -> 9.1.0 wangmy
2023-02-28 9:49 ` [OE-core] [PATCH] python3-zipp: upgrade 3.14.0 -> 3.15.0 wangmy
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=Y/59glKJ9prAGatj@mail.local \
--to=alexandre.belloni@bootlin.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