Hi Dmitry, I propose this solution: remove all the Debian patches (actually the python3 patch seems correctly handled by 2to3 at build time)
add a new patch to disable the only test actually requiring an internet connection: --- pygithub-1.25.2.orig/github/tests/AllTests.py +++ pygithub-1.25.2/github/tests/AllTests.py @@ -84,7 +84,7 @@ from Issue133 import * from Issue134 import * from Issue139 import * from Issue140 import * -from Issue142 import * +#from Issue142 import * from Issue158 import * from Issue174 import * from Issue214 import * I tried locally and on DebOMatic and everything was good. http://debomatic-amd64.debian.net/distribution#unstable/pygithub/1.25.2-4/ Not sure if it is enough, but it seems to be all good with that trivial patch. (I hope no other patches are needed) Let me know if it is ok for you, or you want to drop all the testsuite. (Disabling single tests needs more work at each upstream release, but gives more confidence about the correct program behaviour) thanks again, Gianfranco Il Venerdì 7 Agosto 2015 21:32, Jakub Wilk <jw...@debian.org> ha scritto: * Gianfranco Costamagna <costamagnagianfra...@yahoo.it>, 2015-08-07, 19:26: >>This particular bug appears to caused by >>python3-exception-syntax-error.patch, which throws away 2to3, for a >>reason I don't understand. The patch description says "use_2to3 flag >>is not supported by python-3.4", which makes little sense. use_2to3 is >>a setuptools option, and of course it works in Python 3.4, too. > >I guess you mean "python3.4-fix-setup.patch" Ooops. Right, that's what I meant. -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
