From: Alexander Kanavin <alex.kanavin@gmail.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 00/26] thud patch review
Date: Tue, 19 Mar 2019 11:22:11 +0100 [thread overview]
Message-ID: <D3413079-663B-47D2-8550-658159790D3B@gmail.com> (raw)
In-Reply-To: <20190319085532.GF1994@jama>
The commit you refer to changes the dependency from 1.1.0 to 1.1.1, so ca-certificates currently in thud already needs 1.1.
Alex
> On 19 Mar 2019, at 9.55, Martin Jansa <martin.jansa@gmail.com> wrote:
>
>> On Mon, Mar 18, 2019 at 07:36:29PM -0700, Armin Kuster wrote:
>> Responses should be made by Wed March 20th 22:00:00 UTC 2019
>>
>> The following changes since commit f5a57e939e626a5b7c6de5b51799ca602ed355ed:
>>
>> mesa: ship /etc/drirc in mesa-megadriver (2019-03-05 22:24:13 +0000)
>>
>> are available in the git repository at:
>>
>> git://git.yoctoproject.org/poky-contrib stable/thud-next
>> http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=stable/thud-next
>>
>> Alexander Kanavin (1):
>> ca-certificates: upgrade 20180409 -> 20190110
>
> This depends on openssl >= 1.1.1 since:
> https://salsa.debian.org/debian/ca-certificates/commit/d5e425c8405448e5034d1e16ca52be6a10cb3334
> some people might not use new openssl with thud.
>
> More detail in:
> http://lists.openembedded.org/pipermail/openembedded-core/2019-March/280234.html
>
> Cheers,
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
next prev parent reply other threads:[~2019-03-19 10:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-19 2:36 [PATCH 00/26] thud patch review Armin Kuster
2019-03-19 8:55 ` Martin Jansa
2019-03-19 10:22 ` Alexander Kanavin [this message]
2019-03-19 10:40 ` Martin Jansa
2019-03-19 11:35 ` Alexander Kanavin
2019-03-19 13:55 ` Martin Jansa
2019-03-19 16:31 ` Alexander Kanavin
2019-03-19 17:07 ` Martin Jansa
2019-03-19 14:52 ` akuster808
2019-03-19 15:40 ` Alexander Kanavin
2019-03-19 9:05 ` Vincent Prince
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=D3413079-663B-47D2-8550-658159790D3B@gmail.com \
--to=alex.kanavin@gmail.com \
--cc=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
/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.