Michal Čihař <ni...@debian.org> writes: > The options for now seem to be either to disable documentation build or > just ignore the failure till new sphinx is available.
Thanks for clarifying the situation. If the architecture-dependent packages don't need to ship any generated documentation, you could also mitigate the problem by moving python-sphinx to Build-Depends-Indep and adjusting debian/rules to cope with the possibility that it might be absent (or too old to be of interest). Although the unsatisfiable build dependency would still formally be a bug, it would at least no longer affect the autobuilders. (The only other practical impact of such a bug would be to hold up migration to testing, but that's in deep freeze at the moment anyway.) Could you please consider such a change? Thanks! -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
