Revised port and in attached tgz file with new version 2.0.2.

PyPi install from today's release persists with the requirements issue that Kurt mentioned.

That last commit noted below dumps requirements.txt to /usr/local as noted:

https://github.com/duosecurity/duo_universal_python/commit/0d283171a9f75a4bf5f71ceaf7093b0cdcf1c9e1

Not sure how to deal with it.. remove in post-install then regen PLIST? Patch the setup.py to remove the line that dumps it to /usr/local?

Other than that, the port is fine as per earlier comments below with COMMENT and CATEGORY change.

Thanks.

g

On 7/7/22 14:55, George Rosamond wrote:
Top-posting here...

Actually, please hold off on committing this as there was a new release on PyPi which I'll try, plus moved CATEGORY to sysutils since that's where login_duo is and I changed the COMMENT.

The port is bumped to 2.0.2 which includes this commit:

Ensure requirements.txt is included in the distribution artifacts
https://github.com/duosecurity/duo_universal_python/commit/0d283171a9f75a4bf5f71ceaf7093b0cdcf1c9e1. The github install seems to dump requirements.txt to /usr/local but I'll see how it goes with a PyPi install.

I'll send a new tarball for it later.

Thanks.

g

On 7/6/22 18:35, George Rosamond wrote:
On 7/6/22 18:17, Kurt Mosiejczuk wrote:
On Wed, Jul 06, 2022 at 05:59:27PM -0400, George Rosamond wrote:
attached.

from pkg/DESCR

This SDK allows a web developer to quickly add Duo's interactive,
self-service, two-factor authentication to any Python3 web login
form. Only Python 3 is supported.

I much prefer using PyPI when the package is available from there, but I
see that the tarball from PyPI is broken (setup.py refers to requirements.txt
which is not included in the tarball).

Understood on PyPi versus Github.

But I see requirements.txt out of the extraction:

$ cat /usr/ports/pobj/py-duo_universal-2.0.1-python3/duo_universal_python->
cryptography>=3.2
PyJWT>=2.0
pyOpenSSL>=19.0.0
requests>=2.22.0
wheel>=0.35.1



The RUN_DEPENDS should be sorted (devel comes before security and www...)

fixed.


I'd also like to see the name changed to just py-duo_universal (which reflects
the name used on PyPI).


Done.

With those changes, ok kmos for import

Thanks Kurt. Fixed tarball attached.

g

Attachment: py-duo_universal-2.0.2.tgz
Description: Binary data

Reply via email to