port for letsencrypt ?

Kubilay Kocak koobs at FreeBSD.org
Sat Sep 26 01:17:50 UTC 2015


On 25/09/2015 9:43 PM, Kurt Jaeger wrote:
> Hi!
> 
>> Currently, letsencrypt binary fails to run:
> 
> Hmm, cyclic dependency while building py27-mock for letsencrypt:
> 
> ===>  Staging for py27-tox-1.7.2_1
> ===>   py27-tox-1.7.2_1 depends on package: py27-virtualenv>=1.11.2 - found
> ===>   py27-tox-1.7.2_1 depends on package: py27-py>=1.4.17 - found
> ===>   py27-tox-1.7.2_1 depends on package: py27-pytest>0 - not found
> ===>   py27-pytest-2.7.1 depends on package: py27-mock>0 - not found
> 

pytest/mock should not (and are unlikely to actually be) be build/run
requirements, even though they are declare in setup.py:install_requires:

https://github.com/letsencrypt/letsencrypt/blob/master/setup.py#L32

Not withstanding, mock is only for python 2.6.

virtualenv shouldn't be required either, as it is a deployment specific
component.

Upstream needs to fix their dependency declarations, which we should be
patching locally in the meantime.



More information about the freebsd-python mailing list