Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 00/26] thud patch review
Date: Tue, 19 Mar 2019 11:40:01 +0100	[thread overview]
Message-ID: <20190319104001.GG1994@jama> (raw)
In-Reply-To: <D3413079-663B-47D2-8550-658159790D3B@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1486 bytes --]

On Tue, Mar 19, 2019 at 11:22:11AM +0100, Alexander Kanavin wrote:
> 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

hmm right
https://salsa.debian.org/debian/ca-certificates/commit/1bc87e0b41a04551a93d4e784e158b044c18792a
was already included in 20180409, another thing to work around when
upgrading to thud.

Cheers,

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 201 bytes --]

  reply	other threads:[~2019-03-19 10:39 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
2019-03-19 10:40     ` Martin Jansa [this message]
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=20190319104001.GG1994@jama \
    --to=martin.jansa@gmail.com \
    --cc=alex.kanavin@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox