From: Peter Korsgaard <peter@korsgaard.com>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: jwood+buildroot@starry.com, Martin Bark <martin@barkynet.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/ca-certificates: add support for cryptography > 3.0
Date: Mon, 14 Nov 2022 21:20:37 +0100 [thread overview]
Message-ID: <87o7t9i8yy.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20221106105124.GP3918838@scaer> (Yann E. MORIN's message of "Sun, 6 Nov 2022 11:51:24 +0100")
>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:
> Justin, All,
> On 2022-11-02 12:56 -0400, jwood+buildroot@starry.com spake thusly:
>> From: Justin Wood <jwood@starry.com>
>>
>> This patch was originally submitted upstream at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008244
>> by Wataru Ashihara <wsh@iij.ad.jp>. Minor changes by me to account for the Buildroot change in 0001-*.patch.
>>
>> Building ca-certificates with a newer cryptography is breaking without this patch, and building buildroots
>> `python-cryptography` package first doesn't change the broken behavior.
> I've reworded the commit log in a more logical manner (explain what
> breaks and why, then how we fix it).
> I also notice that the bug report states that cryptography 3.0 is also
> affected, so I tweaked the commit title accordingly.
>> Signed-off-by: Justin Wood <jwood@starry.com>
> Applied to master, thanks.
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).
--
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 20:20 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 [this message]
[not found] ` <CANWKTsML2wzXuh8tA8R-+=r0fXyZ5N3vwZ3JEHE33caEUZv+4w@mail.gmail.com>
2022-11-14 22:24 ` Peter Korsgaard
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=87o7t9i8yy.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=jwood+buildroot@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.