All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4 1/2] libopenssl: bump version to 1.1.1a
Date: Wed, 23 Jan 2019 23:44:26 +0100	[thread overview]
Message-ID: <e09d9674-3ee7-7d9f-5579-063e44691582@mind.be> (raw)
In-Reply-To: <87sgxjjqo1.fsf@dell.be.48ers.dk>



On 23/01/2019 17:15, Peter Korsgaard wrote:
>>>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> writes:
> 
> Hi,
> 
>  >> >  I do hope that it could still go into 2019.02.
>  >> 
>  >> If that is our goal, then we might as well merge it ASAP to get more
>  >> test coverage?
>  >> 
>  >> What is the killer feature why we need openssl-1.1.x in 2019.02.x? TLS
>  >> 1.3 or just that 1.0.2 goes EOL at the end of the year?
> 
>  >  Both, I guess. Also that the whole known world (including Debian stable,
>  > released June 2017) has already switched to 1.1.x.
> 
> With 1.1.x I take it you mean 1.1.0, right? The 1.1.1 series (strange
> numbering convention) was only released back in September.

 With 1.1.x I mean 1.1.0 or 1.1.1. The breakage comes from the 1.1.0 bump; .0 to
.1 is fairly smooth.


 Regards,
 Arnout

> 1.1.0 is not a LTS so not suitable for 2019.02.x. 1.0.2 is supported
> until the end of 2019, so that is IMHO still OK for 2019.02.
> 
> I agree that having 1.1.1x in 2019.02.x would be nice, but a pity that
> quite some packages break with it (even if the whole known world has
> switched to it).
> 

  reply	other threads:[~2019-01-23 22:44 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-15 22:42 [Buildroot] [PATCH v4 1/2] libopenssl: bump version to 1.1.1a Peter Seiderer
2019-01-15 22:42 ` [Buildroot] [PATCH v4 2/2] freeswitch: bump to git master 8f10ae54a18a19fc6ed938e4f662bd218ba54b5e Peter Seiderer
2019-01-16  1:40 ` [Buildroot] [PATCH v4 1/2] libopenssl: bump version to 1.1.1a Ryan Coe
2019-01-16 11:46   ` Arnout Vandecappelle
2019-01-16 14:27     ` Peter Seiderer
2019-01-16  5:52 ` Baruch Siach
2019-01-16 13:58 ` Vadim Kochan
2019-01-17 18:43   ` Peter Seiderer
2019-01-22 11:23     ` Arnout Vandecappelle
2019-01-22 21:08       ` Peter Korsgaard
2019-01-23 14:29         ` Arnout Vandecappelle
2019-01-23 16:15           ` Peter Korsgaard
2019-01-23 22:44             ` Arnout Vandecappelle [this message]
2019-01-23 23:03               ` Peter Korsgaard
2019-01-25 23:27                 ` Arnout Vandecappelle
2019-01-16 11:43 Patrick Havelange
2019-01-16 14:24 ` 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=e09d9674-3ee7-7d9f-5579-063e44691582@mind.be \
    --to=arnout@mind.be \
    --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 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.