Created attachment 223004 [details]
* portlint: OK (looks fine.)
* testport: OK (poudriere: 12.2, amd64 tested)
* maketest: OK (173 passed, 1 skipped, 1 xfailed)
Build and package info is available at https://gitlab.com/swills/freebsd-ports/pipelines/266092718
Hi Goran, hi Terje,
As far as I can say until now, this update also needs an update of devel/py-msal and sysutils/conan. Both give same type of error:
py37-msal-1.9.0 depends on package: py37-pyjwt>=1.0.0<2 - not found
conan-1.34.0 depends on package: py37-pyjwt>=1.4.0,<2.0.0 - not found
Could you investigate into them, please?
Another issue: The changelog for www/py-pyjwt says cryptography >= 3 is needed. For now, we do not have cryptography-3.x in the ports, because of some trouble with OpenSSL. Did you try, if cryptography-2.x also works?
I will check depending ports. For cryptography, 3.3 is already in ports: https://www.freshports.org/security/py-cryptography/
While msal is OK with newer JWT (https://github.com/AzureAD/microsoft-authentication-library-for-python/blob/dev/setup.py#L76), conan isn't (https://github.com/conan-io/conan/blob/develop/conans/requirements.txt#L1). I'll talk to upstream about it.
(In reply to Goran Mekić from comment #3)
Oops, you are right. I must have looked into one of my older svn repos ;)
Conan upstream ticket: https://github.com/conan-io/conan/issues/8609
What is the best course of action? Having pyjwt1 and pyjwt in ports?
(In reply to Goran Mekić from comment #6)
> What is the best course of action? Having pyjwt1 and pyjwt in ports?
Hmm, I really don't know because I don't work with any of those ports.
If you can't wait to update www/py-pyjwt because you need the www/py-flask-jwt-extended update, it's probably best to have an old port and a current port for www/py-pyjwt. Renaming the old one to something like www/py-pyjwt1 seems plausible to me in this case.
If you are not in a hurry, you could wait until conan has updated its dependencies upstream ...
Have you already had contact with the maintainer of www/py-pyjwt?