From: Peter Korsgaard <peter@korsgaard.com>
To: Justin Wood <jwood@starry.com>
Cc: buildroot@buildroot.org,
"Yann E. MORIN" <yann.morin.1998@free.fr>,
Martin Bark <martin@barkynet.com>
Subject: Re: [Buildroot] [PATCH 1/1] package/ca-certificates: add support for cryptography > 3.0
Date: Mon, 14 Nov 2022 23:24:34 +0100 [thread overview]
Message-ID: <87fseli38d.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CANWKTsML2wzXuh8tA8R-+=r0fXyZ5N3vwZ3JEHE33caEUZv+4w@mail.gmail.com> (Justin Wood's message of "Mon, 14 Nov 2022 15:25:27 -0500")
>>>>> "Justin" == Justin Wood <jwood@starry.com> writes:
> On Mon, Nov 14, 2022 at 3:20 PM Peter Korsgaard <peter@korsgaard.com> wrote:
>>
>> This is patching code we've added ourselves in patch 0001, so perhaps it
>> makes sense to invert the order of the patches, merge them or simply
>> drop the certdata2pem.py call completely? We don't build
>> host-python-cryptography automatically, so it can only happen if the
>> recently added optee-os option is selected (or a custom package), and
>> they happen to build before ca-certificates.
>>
>> Committed to 2022.08.x, thanks (we don't have host-python-cryptography
>> in 2022.02.x).
> Of note, in my setup I'm using a system-provided python for host-python,
> which has `cryptography` installed and available due to a linting tool we
> install. That is what caused it to fail for me in 2022.02.x.
Ahh, so you are having some local modifications causing this issue?
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-11-14 22:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 16:56 [Buildroot] [PATCH 1/1] package/ca-certificates: add support for cryptography > 3.0 jwood+buildroot
2022-11-06 10:51 ` Yann E. MORIN
2022-11-14 20:20 ` Peter Korsgaard
[not found] ` <CANWKTsML2wzXuh8tA8R-+=r0fXyZ5N3vwZ3JEHE33caEUZv+4w@mail.gmail.com>
2022-11-14 22:24 ` Peter Korsgaard [this message]
2022-12-06 16:58 ` Justin Wood via buildroot
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=87fseli38d.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=jwood@starry.com \
--cc=martin@barkynet.com \
--cc=yann.morin.1998@free.fr \
/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.