At the Thud branch of meta-python, I see the python3-attrs
(meta-python/recipes-devtools/python/python3-attrs_18.1.0.bb) recipe is
still depending on '${PYTHON_PN}-cryptography'.
I think depending on '${PYTHON_PN}-crypto' is enough.
With 'crypto' i.s.o. 'cryptography' the following packages where
No worries. Does this resolve the original github issue you created?
On Thu, Apr 12, 2018 at 11:09 AM, jan vermaete
wrote:
> my mistake...
> Thanks for the info
>
> On Thu, Apr 12, 2018 at 4:12 PM, Derek Straka wrote:
> > There is a usage of hashlib
my mistake...
Thanks for the info
On Thu, Apr 12, 2018 at 4:12 PM, Derek Straka wrote:
> There is a usage of hashlib (provided by ${PYTHON_PN}-crypt) in _make.py.
>
> derek@sparta:/tmp$ dpkg -c
> upstream/build/tmp/deploy/ipk/core2-64/python-crypt_2.7.14-r1_core2-64.ipk
>
There is a usage of hashlib (provided by ${PYTHON_PN}-crypt) in _make.py.
derek@sparta:/tmp$ dpkg -c
upstream/build/tmp/deploy/ipk/core2-64/python-crypt_2.7.14-r1_core2-64.ipk
drwxrwxrwx root/root 0 2018-03-24 09:28 ./
drwxr-xr-x root/root 0 2018-03-24 09:28 ./usr/
drwxr-xr-x
I'm afraid this patch just revert the file to the previous state.
As far as I can see, there is no need at all to have something of
crypto nor crypotgraphy needed for this python package.
--
Jan Vermaete
"For every complex problem there is an answer that is clear, simple,
and wrong." - H.L.
Signed-off-by: Derek Straka
---
meta-python/recipes-devtools/python/python-attrs.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta-python/recipes-devtools/python/python-attrs.inc
b/meta-python/recipes-devtools/python/python-attrs.inc
index