All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 5/5] package/python3-cryptography: add python3 host variant
Date: Sun, 6 Jun 2021 23:10:13 +0200	[thread overview]
Message-ID: <20210606211013.GL168928@scaer> (raw)
In-Reply-To: <20210522083257.GY3208066@scaer>

Donald, All,

On 2021-05-22 10:32 +0200, Yann E. MORIN spake thusly:
> On 2021-05-22 00:42 +0000, Chan, Donald via buildroot spake thusly:
> > On 2021-05-20 01:49 +0000, Chan, Donald via buildroot spake thusly:
> > > > Add a python3 host variant since another downstream OSS component
> > > > (OP-TEE) uses buildroot and it will depend on a python3 host variant
> > > > of python-cryptography.
> > > So, those 5 patches are OK (but still, see below for some comments)),
> > > but there is still nothing that uses those new host packages in the
> > > Buildroot tree.
> [--SNIP--]
> > > In which case, adding those pacakges should be part of the series that
> > > updates optee_os.
> > It's a chicken and egg problem - the original OP-TEE ticket to migrate
> > to pyca/cryptography is https://github.com/OP-TEE/optee_os/issues/4599,
> > but if it's merged now, it will immediately break their CI because they
> > are still using buildroot 2021.02 (https://github.com/OP-TEE/manifest/blob/master/default.xml#L24).
> 
> Ah. that's the piece I was missing: the CI is using an unmodified,
> released version of Buildroot. That's neat! :-)
> 
> I can see the chicken-n-egg problem, now, thanks.
> 
> > So the best approach seems to be:
> > 1. Update buildroot with these new packages
> > 2. Wait till there is a new buildroot release, submit a PR to update their manifest
> > 3. Then submit another PR to migrate to pyca/cryptography
> > It's going to be a long process but it will cause the least amount of disruptions. 
> 
> I've reinistated these pactches in the "new" state, so they are back
> under consideration. We'll see what the opinion of the other maintainers
> are.
> 
> Peter, Thomas, Arnout: your thoughts?

Without further replies, I've applied this 5-patch series to master,
thanks.

Please review the individual commits, I had to do a few tweaks to the 5
packages.

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

      reply	other threads:[~2021-06-06 21:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-20  1:49 [Buildroot] [PATCH 5/5] package/python3-cryptography: add python3 host variant Chan, Donald
2021-05-21 16:22 ` Yann E. MORIN
2021-05-22  0:42   ` Chan, Donald
2021-05-22  8:32     ` Yann E. MORIN
2021-06-06 21:10       ` Yann E. MORIN [this message]

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=20210606211013.GL168928@scaer \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@busybox.net \
    /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.