[Python-modules-team] Bug#869098: python2.7 2.7.13-4 causes EOFError breakage in python-sphinx

[Julian Andres Klode]

Control: forwarded -1 https://github.com/sphinx-doc/sphinx/issues/4006

On Sun, Sep 17, 2017 at 10:48:27AM +0200, Matthias Klose wrote:
> Control: reassign -1 python-sphinx
> 
> On 14.09.2017 14:18, Julian Andres Klode wrote:
> > On Thu, Jul 20, 2017 at 03:40:52PM +0100, Neil Williams wrote:
> >> Package: python2.7
> >> Version: 2.7.13-4
> >> Severity: serious
> >> Justification: causes other packages to FTBFS
> >>
> >> With 2.7.13-4 installed, I am unable to build documentation as sphinx
> >> errors out:
> >>
> >> sphinx-build -b html -d _build/doctrees  -n -j 4 . _build/html
> >> Running Sphinx v1.4.9
> >> making output directory...
> >> loading pickled environment... not yet created
> >> loading intersphinx inventory from https://docs.python.org/2/objects.inv...
> >> building [mo]: targets for 0 po files that are out of date
> >> building [html]: targets for 91 source files that are out of date
> >> updating environment: 91 added, 0 changed, 0 removed
> >> reading sources... [100%] test-repositories .. writing-tests                                                                                  
> >> waiting for workers...
> >>
> >> Exception occurred:
> >>   File "/usr/lib/python2.7/dist-packages/sphinx/util/parallel.py", line 97, in _join_one
> >>     exc, result = pipe.recv()
> >> EOFError
> > 
> > Given that this is a regression in 2.7.13-4, can we please revert
> > unstable to 2.7.13-3 again (as 2.7.14~rc1+really2.7.13-1 or something).
> 
> ... and now identified as an issue in sphinx. reassigning.

And here's the upstream commit fixing it, to provide some context:

https://github.com/sphinx-doc/sphinx/commit/2f8a342839bb36dd3622fb4ce3f874121b22c7ab

> 
> > Having an rc-buggy python in unstable that breaks reverse dependencies for two months
> > is not really acceptable
> 
> the only thing here which is not really acceptable is your behaviour of finger
> pointing.

I was merely suggesting that you do the same I'd do for my
packages - if there's an RC critical bug I can't find the
cause of for weeks, I'd move it to experimental, and
revert unstable to the last known good version. Especially
if it breaks building reverse deps.

One major annoyance for me personally was that this RC bug
interacted awfully with apt and apt-listbugs. apt-listbugs
pinned python2.7 to prevent the upgrade, and apt then wanted
to remove python2.7-dev and python2.7-dbg and friends every
single dist-upgrade. This is of course apt's stupidity. I
expect things get a bit better when we can pin by Source.

-- 
Debian Developer - deb.li/jak | jak-linux.org - free software dev
                  |  Ubuntu Core Developer |
When replying, only quote what is necessary, and write each reply
directly below the part(s) it pertains to ('inline').  Thank you.