At some point dev-python/twisted removed a deprecated method with is used by the ssl tests in dev-python/epsilon-0.6.0. The result is a number of error messages in the build log along the lines of =============================================================================== [ERROR]: epsilon.test.test_sslverify.OpenSSLOptions.testAbbreviatingDistinguishedNames Traceback (most recent call last): File "/var/tmp/portage/dev-python/epsilon-0.6.0/work/Epsilon-0.6.0-2.6/epsilon/test/test_sslverify.py", line 139, in testAbbreviatingDistinguishedNames self.assertEquals(sslverify.DN(CN='a', OU='hello'), exceptions.NameError: global name 'sslverify' is not defined =============================================================================== Reproducible: Always Steps to Reproduce: 1. emerge =dev-python/twisted-10.1.0 2. emerge epsilon Actual Results: SSL tests fail Expected Results: SSL tests pass I have seen references to a patch to change setUpClass to setUp which apparently fixes this. I don't know if this is an official change. https://launchpad.net/ubuntu/+source/epsilon/0.6.0-3 Perhaps dev-python/epsilon-0.6.0 needs a dependency to link it to a lower version of dev-python/twisted. I know that if =dev-python/twisted-8.2.0 used then the SSL tests pass..
Created attachment 264529 [details] Build Log
Please paste your `emerge --info' output in a comment.
Created attachment 264733 [details] emerge --info =dev-python/epsilon-0.6.0 Rather moot since the bug is a code issue documented elsewhere
I believe this is the development site. In the development stream the file that fails is removed. http://bazaar.launchpad.net/~divmod-dev/divmod.org/trunk/revision/2672
Created attachment 294579 [details, diff] ebuild patch according to http://bazaar.launchpad.net/~divmod-dev/divmod.org/trunk/revision/2672, the tests for ssl can and should be removed, and why they're still there who knows. The timezone 1 I may just may be wrong but I doubt it. 14:15:16 is hour min seconds in the test. oddly enough, 14:15:16 != 09:15:16. Now is the format being tested or the capacity to add 5 to 9 to make 14. That means that there must be something in the arg being tested that stipulates its timezone a -5, or is it +5. Whichever, there is no sign of it I can see. So the test was trying to equate 9 a.m. with 2 p.m. or 1400 hrs. Or am I missing something??? The python test makers seem to do this. Python team please review and test
Fixed with rev bump. Thanks, Ian.
