From: Peter Korsgaard <peter@korsgaard.com>
To: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
Cc: Bernd Kuhls <bernd@kuhls.net>, Danny Wood <danny@rotronics.co.uk>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [Buildroot] [PATCH 1/1] package/libopenssl: bump version to 3.0.9
Date: Sat, 15 Jul 2023 16:39:19 +0200 [thread overview]
Message-ID: <87fs5pfdd4.fsf@48ers.dk> (raw)
In-Reply-To: <20230714232518.6ed70c07@windsurf> (Thomas Petazzoni via buildroot's message of "Fri, 14 Jul 2023 23:25:18 +0200")
>>>>> "Thomas" == Thomas Petazzoni via buildroot <buildroot@buildroot.org> writes:
> Hello,
> On Fri, 14 Jul 2023 18:23:39 +0200
> Bernd Kuhls <bernd@kuhls.net> wrote:
>> From: Danny Wood <danny@rotronics.co.uk>
>>
>> Rebase patches onto new version
>>
>> Remove 0005-crypto-perlasm-ppc-xlate.pl-add-linux64v2-flavour.patch,
>> 0006-Add-support-for-io_pgetevents_time64-syscall.patch, and
>> 0007-Fixup-support-for-io_pgetevents_time64-syscall.patch as these are
>> already applied upstream
>>
>> Downloaded from
>> https://lists.buildroot.org/pipermail/buildroot/2023-June/669230.html
>>
>> Signed-off-by: Bernd Kuhls <bernd@kuhls.net>
> How much build testing was done with this version bump? I know OpenSSL
> 3.x breaks a few APIs compared to OpenSSL 1.x.
> Could you do a test build with a significant number of packages using
> OpenSSL in Buildroot, to assess the damage caused by this version bump,
> and provide the defconfig used for this verification?
Danny already stated that he had built a significant amount of packages
(and provided an update to mariadb to fix a compatibility issue). Given
that our move to 3.x is long overdue (E.G. 1.1.1 goes EOL in September),
I think the best approach is just merging this as soon as possible and
then fix up any fallout before 2023.08.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-07-15 14:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-14 16:23 [Buildroot] [PATCH 1/1] package/libopenssl: bump version to 3.0.9 Bernd Kuhls
2023-07-14 21:25 ` Thomas Petazzoni via buildroot
2023-07-15 14:39 ` Peter Korsgaard [this message]
[not found] ` <87fs5pfdd4.fsf__37810.1900381566$1689431990$gmane$org@48ers.dk>
2023-07-15 15:07 ` Bernd Kuhls
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=87fs5pfdd4.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=bernd@kuhls.net \
--cc=buildroot@buildroot.org \
--cc=danny@rotronics.co.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox