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
Updates to the most recent version of glmark2. In particular, this fixes
problems where the benchmark would fail to start due to improper
handling of EGL_NO_DISPLAY with EGL 1.5
Signed-off-by: Joshua Watt
---
meta-oe/recipes-benchmark/glmark2/glmark2_git.bb | 4 ++--
1 file changed, 2
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
Signed-off-by: Khem Raj
---
.../renderdoc/{renderdoc_1.6.bb => renderdoc_1.7.bb}| 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta-oe/recipes-graphics/renderdoc/{renderdoc_1.6.bb =>
renderdoc_1.7.bb} (95%)
diff --git
