From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Andrej Valek <andrej.valek@siemens.com>,
Khem Raj <raj.khem@gmail.com>,
Randy MacLeod <randy.macleod@windriver.com>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>,
Armin Kuster <akuster808@gmail.com>
Subject: Re: [PATCH] ca-certificates: prevent executing update-ca-certificates from host system
Date: Thu, 24 Aug 2017 15:26:46 +0100 [thread overview]
Message-ID: <1503584806.32591.198.camel@linuxfoundation.org> (raw)
In-Reply-To: <8994061e-1012-1a4d-e6d7-47e978646841@siemens.com>
On Thu, 2017-08-24 at 16:23 +0200, Andrej Valek wrote:
> I have seen your patch, but it is not fixing my described issue.
> A command update-ca-certificates will be not available due to missing
> native stuff.
I changed the postinst so it doesn't need a native update-ca-
certificates though?
Its similar to one of your original patches but fixes the dependency
issues and explains why the current approach is broken (path mismatch)
and why its safe to do this (allarch recipe and script).
Cheers,
Richard
next prev parent reply other threads:[~2017-08-24 14:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-17 14:44 [PATCH] ca-certificates: prevent executing update-ca-certificates from host system Andrej Valek
2017-08-17 16:31 ` Richard Purdie
2017-08-18 6:26 ` Andrej Valek
2017-08-18 9:35 ` Richard Purdie
2017-08-18 10:05 ` Andrej Valek
2017-08-18 15:46 ` Randy MacLeod
2017-08-21 6:12 ` Andrej Valek
2017-08-23 12:07 ` Andrej Valek
2017-08-23 12:44 ` Richard Purdie
2017-08-23 19:00 ` Khem Raj
2017-08-24 10:38 ` Andrej Valek
2017-08-24 14:16 ` Richard Purdie
2017-08-24 14:23 ` Andrej Valek
2017-08-24 14:26 ` Richard Purdie [this message]
2017-08-25 6:05 ` Andrej Valek
2017-08-25 8:25 ` Richard Purdie
2017-08-25 12:31 ` Andrej Valek
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=1503584806.32591.198.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=akuster808@gmail.com \
--cc=andrej.valek@siemens.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
--cc=randy.macleod@windriver.com \
/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