From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Christian Stewart <christian@paral.in>
Cc: Fabrice Fontaine <fontaine.fabrice@gmail.com>,
Buildroot Mailing List <buildroot@buildroot.org>
Subject: Re: [Buildroot] package/expat: please backport to 2021.11.x
Date: Tue, 22 Feb 2022 09:32:46 +0100 [thread overview]
Message-ID: <20220222093246.57ab1b0d@windsurf> (raw)
In-Reply-To: <CA+h8R2pwkhPn5SS-jPmXjS_gb07EsshRA5HMJewVRcY32RL6=g@mail.gmail.com>
On Mon, 21 Feb 2022 21:21:16 -0800
Christian Stewart <christian@paral.in> wrote:
> Expat v2.4.4 (vulnerable) download has been removed from sourceforge.
>
> So 2021.11.x build is broken with the older expat.
This is strange: if the expat tarball is no longer available from
sourceforge, Buildroot should fallback to sources.buildroot.net, which
contains the expat-2.4.4.tar.xz tarball, at
http://sources.buildroot.net/expat/.
Of course, it is better to update since there is a security issue in
2.4.4, but I'm wondering why you're saying that the build is broken: it
should not.
Best regards,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-02-22 8:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-22 5:21 [Buildroot] package/expat: please backport to 2021.11.x Christian Stewart via buildroot
2022-02-22 8:32 ` Thomas Petazzoni via buildroot [this message]
2022-02-22 8:48 ` Christian Stewart via buildroot
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=20220222093246.57ab1b0d@windsurf \
--to=buildroot@buildroot.org \
--cc=christian@paral.in \
--cc=fontaine.fabrice@gmail.com \
--cc=thomas.petazzoni@bootlin.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.