From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4 1/2] libopenssl: bump version to 1.1.1a
Date: Thu, 24 Jan 2019 00:03:12 +0100 [thread overview]
Message-ID: <87tvhzht8v.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <e09d9674-3ee7-7d9f-5579-063e44691582@mind.be> (Arnout Vandecappelle's message of "Wed, 23 Jan 2019 23:44:26 +0100")
>>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> writes:
Hi,
>> > 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.
Ok. 1.1.0 was released 2.5 years ago (August 2016). How come we still
need fixes for quite some packages? All abandoned software? Should we
get rid of some of those packages?
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2019-01-23 23:03 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
2019-01-23 23:03 ` Peter Korsgaard [this message]
2019-01-25 23:27 ` Arnout Vandecappelle
-- strict thread matches above, loose matches on Subject: below --
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=87tvhzht8v.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--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