From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC v1 1/2] libopenssl: bump version to 1.1.0h
Date: Thu, 3 May 2018 23:11:40 +0200 [thread overview]
Message-ID: <20180503231140.584503c5@gmx.net> (raw)
In-Reply-To: <20180502092124.500f37cc@windsurf.home>
Hello Thomas,
On Wed, 2 May 2018 09:21:24 +0200, Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:
> Hello Peter,
>
> On Tue, 17 Apr 2018 23:19:20 +0200, Peter Seiderer wrote:
> > - remove all parallel build patches (openssl build-system changed)
> >
> > - rebased 0001-Dont-waste-time-building-manpages-if-we-re-not-going.patch
> >
> > - replaced 0002-cryptodev-Fix-issue-with-signature-generation.patch with
> > upstream version
> >
> > - rebased 0003-Reproducible-build-do-not-leak-compiler-path.patch
> >
> > - fix uclibc build failure, use '-DOPENSSL_NO_ASYNC'
> >
> > - remove legacy enable-tlsext configure option
> >
> > - change legacy INSTALL_PREFIX to DESTDIR
> >
> > - remove 'libraries gets installed read only, so strip fails'
> > workaround (not needed anymore)
> >
> > - change engine directory from /usr/lib/engines to
> > /usr/lib/engines-1.1
> >
> > - change license file hash, no license change, only the following
> > hint was removed:
> >
> > Actually both licenses are BSD-style Open Source licenses.
> > In case of any license issues related to OpenSSL please
> > contact openssl-core at openssl.org.
> >
> > Signed-off-by: Peter Seiderer <ps.report@gmx.net>
>
> This patch has received several comments from different people
> reporting issues. Since your patch series was sent as RFC and people
> have reported problems, I'll mark the patches as Changes Requested in
> patchwork. But of course, please resend a new version when you have
> some time to work on this.
New version will follow soon, will keep it as RFC until more packages
depending on openssl are compile-/runtime tested with the new version
(or in case of too much failures maybe an extra openssl-1.1.0 package
is needed)...
Regards,
Peter
>
> Thanks!
>
> Thomas
prev parent reply other threads:[~2018-05-03 21:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-17 21:19 [Buildroot] [RFC v1 1/2] libopenssl: bump version to 1.1.0h Peter Seiderer
2018-04-17 21:19 ` [Buildroot] [RFC v1 2/2] openssh: add patch to fix openssl-1.1.0h compile Peter Seiderer
2018-04-20 15:29 ` [Buildroot] [RFC v1 1/2] libopenssl: bump version to 1.1.0h Ryan Coe
2018-04-29 8:17 ` Bernd Kuhls
2018-05-02 21:25 ` Peter Seiderer
2018-05-02 21:14 ` Peter Seiderer
2018-04-29 13:00 ` Bernd Kuhls
2018-05-03 21:05 ` Peter Seiderer
2018-05-01 7:46 ` Bernd Kuhls
2018-05-02 21:35 ` Peter Seiderer
2018-05-02 7:21 ` Thomas Petazzoni
2018-05-03 21:11 ` Peter Seiderer [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=20180503231140.584503c5@gmx.net \
--to=ps.report@gmx.net \
--cc=buildroot@busybox.net \
/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