From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC v3 2/3] openssh: add patch to fix openssl-1.1.0h compile
Date: Sat, 25 Aug 2018 21:37:32 +0200 [thread overview]
Message-ID: <20180825213732.36005e3e@gmx.net> (raw)
In-Reply-To: <73a75fx6k1.ln2@ID-313208.user.individual.net>
Hello Bernd,
On Sat, 25 Aug 2018 08:37:59 +0200, Bernd Kuhls <bernd.kuhls@t-online.de> wrote:
> Am Tue, 08 May 2018 21:54:30 +0200 schrieb Peter Seiderer:
>
> > Signed-off-by: Peter Seiderer <ps.report@gmx.net>
> > ---
> > Changes v2 -> v3:
> > - no changes
> >
> > Changes v1 -> v2:
> > - no changes
>
> Hi Peter,
>
> this patch does not apply anymore on openssh-7.8.
Try one of the update versions of derived patch from [1] or [2]...
Regards,
Peter
[1] https://git.archlinux.org/svntogit/packages.git/log/trunk/openssl-1.1.0.patch?h=packages/openssh
[2] https://src.fedoraproject.org/cgit/rpms/openssh.git/log/openssh-7.3p1-openssl-1.1.0.patch
>
> Regards, Bernd
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
next prev parent reply other threads:[~2018-08-25 19:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-08 19:54 [Buildroot] [RFC v3 1/3] libopenssl: bump version to 1.1.0h Peter Seiderer
2018-05-08 19:54 ` [Buildroot] [RFC v3 2/3] openssh: add patch to fix openssl-1.1.0h compile Peter Seiderer
2018-08-25 6:37 ` Bernd Kuhls
2018-08-25 19:37 ` Peter Seiderer [this message]
2018-05-08 19:54 ` [Buildroot] [RFC v3 3/3] freeswitch: bump to git master 8f10ae54a18a19fc6ed938e4f662bd218ba54b5e Peter Seiderer
2018-06-09 14:22 ` [Buildroot] [RFC v3 1/3] libopenssl: bump version to 1.1.0h Ryan Coe
2018-06-11 20:07 ` Peter Seiderer
2018-08-18 23:29 ` Bernd Kuhls
2018-08-19 17:23 ` Peter Seiderer
2018-12-11 22:44 ` Arnout Vandecappelle
2018-12-13 20:11 ` Peter Seiderer
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=20180825213732.36005e3e@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