Re: Getting ready for Python 3.5
It looks like we have a Build-Depends loop. python-sphinx (sphinx) -> python3-gi (pygobject) -> python3-cairo (py3cairo) -> python-sphinx All FTBFS in the PPA. I'm guessing this loop was introduced after the addition of Python 3.4, since it should affect every major Python version transition. I'm going to try to break the loop by doing a temporary upload of python3-cairo without the sphinx B-D, then restore that if/when I can get the other two to build. Suggestions welcome. Cheers, -Barry pgpli42jUjbi3.pgp Description: OpenPGP digital signature
Re: Getting ready for Python 3.5
Hi Barry, On Thu, 25 Jun 2015 09:38:49 -0400, Barry Warsaw wrote: > It looks like we have a Build-Depends loop. > > python-sphinx (sphinx) -> python3-gi (pygobject) -> python3-cairo (py3cairo) > -> python-sphinx > > All FTBFS in the PPA. I'm guessing this loop was introduced after the > addition of Python 3.4, since it should affect every major Python version > transition. > > I'm going to try to break the loop by doing a temporary upload of > python3-cairo without the sphinx B-D, then restore that if/when I can get > the other two to build. > > Suggestions welcome. Sphinx needs python3-gi only for tests, so I think it will be easier to break the loop here. Search for "jstest" in debian/rules and comment that line out. -- Dmitry Shachnev signature.asc Description: OpenPGP digital signature
Re: Getting ready for Python 3.5
On Jun 25, 2015, at 04:57 PM, Dmitry Shachnev wrote: >Sphinx needs python3-gi only for tests, so I think it will be easier to >break the loop here. Search for "jstest" in debian/rules and comment that >line out. Thanks, it might indeed be easier this way. py3cairo is a mess. :/ Cheers, -Barry pgpyAce0R4pV_.pgp Description: OpenPGP digital signature
