Ah I finally found the relevant upstream ticket: https://bitbucket.org/pypa/setuptools/issue/168/ez_setuppy-failing-sporadically-when which appears resolved with setuptools-3.5.2
Next is testing of a version >= 3.5.2 Regards, On Thursday, May 15, 2014 9:53:36 AM UTC+2, Ralf Stephan wrote: > > It may be possible to test newer package versions in patchbot without > official ticket by forking Sage on github, installing the package in the > local > Sage, publish the changed branch on github, and use that branch as > base_repo with patchbot. This may work also with unsafe tickets because > the cloning into /tmp copies upstream/ too. I'm testing that soon. > > If this doesn't work then my fork of patchbot soon will have a version > with a --keep-tmp option that doesn't delete failed installs in /tmp so > that the setuptools problem can be postmortemed. I have stopped > making pull requests at robertb/patchbot. > > https://github.com/rwst/patchbot > > Regards, > > On Tuesday, May 13, 2014 9:51:17 PM UTC+2, Peter Bruin wrote: >> >> I started a patchbot based on 6.3.beta1, and the problem has >> unfortunately popped up again with the new setuptools version: >> >> >> http://patchbot.sagemath.org/log/16348/debian/wheezy/sid/x86_64/3.2.0-57-generic/selmer/2014-05-13%2019:57:47%20+0100 >> >> >> Op woensdag 7 mei 2014 10:05:32 UTC+1 schreef Ralf Stephan: >>> >>> http://trac.sagemath.org/ticket/16300 >>> >>> People running patchbot with errors on setuptools install please try >>> version 2.2b1 of setuptools and report if this changes the behaviour >>> or not. >>> >>> Regards, >>> >> -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
