mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Oliver Graute <oliver.graute@gmail.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCHv1] openssl: version bump to 1.1.1a
Date: Wed, 9 Jan 2019 14:27:41 +0100	[thread overview]
Message-ID: <20190109132741.GA31039@graute-opti> (raw)
In-Reply-To: <1547037072.15888.28.camel@diehl.com>

On 09/01/19, Denis OSTERLAND wrote:
> Hi Oliver,
> 
> AFAIK OpenSSL 1.0 -> 1.1 is a bigger step.

I know, so I started with this little changes to get feedback as early
as possible.

> On which architectures have you tried it?
> Do you compiled ALL_YES?

no, I just compiled for debian-armel, for the other architectures we
need to patch 10-main.conf accordingly.
> 
> Am Dienstag, den 08.01.2019, 14:45 +0100 schrieb Oliver Graute:
> > this patch bump openssl to LTS version 1.1.1a
> > 
> > - added debian-armel to Configurations/10-main.conf for compiling on arm
> I would use the patches from http://deb.debian.org/debian/pool/main/o/openssl/openssl_1.1.1a-1.debian.tar.xz
> to replace the patches imported from openssl1.0_1.0.2o-1.debian.tar.xz.
> 
> The patches 0100 and 0101 can be dropped, if it builds in parallel, I guess.

I'll look into it
> 
> > - dropped the other patches, are these still necessary?
> You should delete this patches.
> Actually your patches does not delete them.

yes you a right.

Best regards,

Oliver

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

  parent reply	other threads:[~2019-01-09 13:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-08 13:45 Oliver Graute
2019-01-09 12:31 ` Denis OSTERLAND
2019-01-09 13:23   ` Ladislav Michl
2019-01-09 13:27   ` Oliver Graute [this message]
2019-01-09 14:14   ` Michael Olbrich
2019-01-09 14:23     ` Oliver Graute

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=20190109132741.GA31039@graute-opti \
    --to=oliver.graute@gmail.com \
    --cc=ptxdist@pengutronix.de \
    /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