On 2015/05/15 19:15, Johan Huldtgren wrote:
> >- any idea why there's a @mode 444 in py-oauthlib's PLIST for the egg-info
> >directory(!) and files? that looks wrong.
>
> Because without it I get this:
>
> Error: weird mode for
> /usr/local/lib/python2.7/site-packages/oauthlib-0.7.2-py2.7.egg-info/PKG-INFO:
> 440
> Error: modes don't match for
> /usr/local/lib/python2.7/site-packages/oauthlib-0.7.2-py2.7.egg-info/PKG-INFO
>
> ... (for all files in that dir)
The distfile unpacks with no group-readable permissions.
Simplest fix is probably
post-extract:
chmod -R o+rX ${WRKSRC}
> Regardless, I fixed up the port adding test depends, port builds and seems
> to work, however 'make test' fails:
>
<...>
> assertion = jwt.encode(claim, key, 'RS256')
> File "/usr/local/lib/python2.7/site-packages/jwt/api.py", line 122, in
> encode
> raise NotImplementedError('Algorithm not supported')
> NotImplementedError: Algorithm not supported
>
> ======================================================================
> ERROR: test_authorization_grant
> (tests.oauth2.rfc6749.test_server.SignedTokenEndpointTest)
> ----------------------------------------------------------------------
So I found this:
https://github.com/idan/oauthlib/issues/317
| "Yes. You have to use PyJWT < 0.4.0 for oauthlib 0.7.2. For PyJWT 0.4 or
| later, you need master head."
So either we need an older PyJWT, or we need oauthlib head. I wouldn't be
averse to using head from a github checkout, but that is what needs
py-cryptography.
> tests which might require py-cryptography (which we don't have, I took a
> quick stab at porting to see if that would fix it, but it got very messy
> very quick). And I'm not sure how to make it only test some things, or if
> I'm even right about this.
I have started a port for py-cryptography, it shouldn't be too bad (and
we should have it in the tree anyway), but it needs additional ports,
I'll write a separate mail about that so it's easier for people to see
rather than hidden at the bottom of this :-)
