From: Derek Straka <derek@asterius.io>
To: jan vermaete <jan.vermaete@gmail.com>
Cc: openembeded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-python][PATCH] python-attrs: Adjust the RDEPENDS to include crypt rather than cryptography
Date: Thu, 12 Apr 2018 11:24:28 -0400 [thread overview]
Message-ID: <CADNbA1rcENxDEY4-i7=bsPVS4nYU092rdo=OGjYcbbwyF3pcpw@mail.gmail.com> (raw)
In-Reply-To: <CABF_=yjBxXZQUYgfHhr94_Kkkxnrs4UV8CJBRe30N3wRp-+eaw@mail.gmail.com>
No worries. Does this resolve the original github issue you created?
On Thu, Apr 12, 2018 at 11:09 AM, jan vermaete <jan.vermaete@gmail.com>
wrote:
> my mistake...
> Thanks for the info
>
> On Thu, Apr 12, 2018 at 4:12 PM, Derek Straka <derek@asterius.io> 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
> > drwxrwxrwx root/root 0 2018-03-24 09:28 ./
> > drwxr-xr-x root/root 0 2018-03-24 09:28 ./usr/
> > drwxr-xr-x root/root 0 2018-03-24 09:28 ./usr/lib/
> > drwxr-xr-x root/root 0 2018-03-24 09:28 ./usr/lib/python2.7/
> > -rw-r--r-- root/root 7842 2018-03-24 09:28
> > ./usr/lib/python2.7/hashlib.py
> > -rw-r--r-- root/root 6891 2018-03-24 09:28
> > ./usr/lib/python2.7/hashlib.pyc
> > drwxr-xr-x root/root 0 2018-03-24 09:28
> > ./usr/lib/python2.7/lib-dynload/
> > -rwxr-xr-x root/root 25184 2018-03-24 09:28
> > ./usr/lib/python2.7/lib-dynload/_hashlib.so
> > -rwxr-xr-x root/root 6520 2018-03-24 09:28
> > ./usr/lib/python2.7/lib-dynload/crypt.so
> > -rw-r--r-- root/root 358 2018-03-24 09:28
> ./usr/lib/python2.7/md5.py
> > -rw-r--r-- root/root 376 2018-03-24 09:28
> ./usr/lib/python2.7/md5.pyc
> > -rw-r--r-- root/root 393 2018-03-24 09:28
> ./usr/lib/python2.7/sha.py
> > -rw-r--r-- root/root 419 2018-03-24 09:28
> ./usr/lib/python2.7/sha.pyc
> >
> > derek@sparta:/tmp$ grep -r hashlib attrs/
> > attrs/src/attr/_make.py:import hashlib
> > attrs/src/attr/_make.py: sha1 = hashlib.sha1()
> > attrs/src/attr/_make.py: sha1 = hashlib.sha1()
> > attrs/src/attr/_make.py: sha1 = hashlib.sha1()
> >
> > On Thu, Apr 12, 2018 at 9:33 AM, jan vermaete <jan.vermaete@gmail.com>
> > wrote:
> >>
> >> 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. Mencken
> >> --
> >> _______________________________________________
> >> Openembedded-devel mailing list
> >> Openembedded-devel@lists.openembedded.org
> >> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
> >
> >
>
>
>
> --
> Jan Vermaete
> "For every complex problem there is an answer that is clear, simple,
> and wrong." - H.L. Mencken
>
next prev parent reply other threads:[~2018-04-12 15:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-12 13:33 [meta-python][PATCH] python-attrs: Adjust the RDEPENDS to include crypt rather than cryptography jan vermaete
2018-04-12 14:12 ` Derek Straka
2018-04-12 15:09 ` jan vermaete
2018-04-12 15:24 ` Derek Straka [this message]
2018-11-26 20:49 ` jan vermaete
-- strict thread matches above, loose matches on Subject: below --
2018-04-11 12:30 Derek Straka
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='CADNbA1rcENxDEY4-i7=bsPVS4nYU092rdo=OGjYcbbwyF3pcpw@mail.gmail.com' \
--to=derek@asterius.io \
--cc=jan.vermaete@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
/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.