On Wed, Mar 11, 2020 at 8:02 PM Scott Branden
wrote:
> So no changes to make. Could we get this added to master-next?
>
My concerns have been addressed.
Thank you everyone for the time you took to research the state of things.
Reviewed-by: Tim Orling
>
> On Tue, 10 Mar 2020 at 20:48,
So no changes to make. Could we get this added to master-next?
On Tue, 10 Mar 2020 at 20:48, Rajesh Ravi wrote:
> ++
>
> Hi Scott,
>
> A)I tried a lot no other recipe could resolve OP-TEE 3.8.0 build break.
> I posted this in OP-TEE as well as meta-openembedded forums.
> This is the only
On Tue, Mar 10, 2020 at 12:56 PM Vesa Jääskeläinen
wrote:
> Hi,
>
> Actually no.
>
> pythonX-cryptodome has need to conflict with pythonX-crypto.
>
> But python3-cryptodomex can coexists with either one of those as they
> have own namespace.
>
That is probably what I am remembering, since I had
Hi,
Actually no.
pythonX-cryptodome has need to conflict with pythonX-crypto.
But python3-cryptodomex can coexists with either one of those as they
have own namespace.
Some software need to unfortunately have both python3-cryptodome (brings
python3-crypto "API emulation") and
On 2020-03-09 10:50 p.m., Tim Orling wrote:
This probably should have an RCONFLICTS with python3-cryptodme (and
maybe even python3-crypto).
These three packages step all over each other with same functionality...
Good feedback Tim.
Rajesh, could you look if the other recipes do what is
This probably should have an RCONFLICTS with python3-cryptodme (and maybe
even python3-crypto).
These three packages step all over each other with same functionality...
On Mon, Mar 9, 2020 at 7:50 PM Scott Branden via Openembedded-devel <
openembedded-devel@lists.openembedded.org> wrote:
>
From: Rajesh Ravi
Add python3-pycryptodomex 3.9.4 recipe needed to build
such components as optee 3.8.0.
Signed-off-by: Rajesh Ravi
Signed-off-by: Scott Branden
---
.../python/python3-pycryptodomex_3.9.4.bb | 30 +++
1 file changed, 30 insertions(+)
create mode 100644
