Date: Sat, 26 Sep 2015 11:17:39 +1000 From: Kubilay Kocak <koobs@FreeBSD.org> To: Kurt Jaeger <pi@FreeBSD.org>, Carlos J Puga Medina <cpm@fbsd.es> Cc: jessekempf@gmail.com, nivit@FreeBSD.org, python@freebsd.org Subject: Re: port for letsencrypt ? Message-ID: <5605F233.7080604@FreeBSD.org> In-Reply-To: <20150925114301.GS982@fc.opsec.eu> References: <20150916144000.GX36682@home.opsec.eu> <20150916152353.GA27526@Silverstone.nc-us.unovitch.com> <1442578072.4799.4.camel@fbsd.es> <1442597708.2650190.387513745.7A2B4A7A@webmail.messagingengine.com> <1442670817.1557.2.camel@fbsd.es> <20150919142656.GA33712@biertje.skysmurf.nl> <1443180637.1566.7.camel@fbsd.es> <20150925114301.GS982@fc.opsec.eu>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5605F233.7080604>