Bug#771127: What shall we do for the sphinxcontrib diag stuff?
Thomas Goirand <zigo <at> debian.org>
2014-11-27 00:08:00 GMT
Dear release team,
There's a number of sphinxcontrib package which have RC bugs in Jessie,
because of missing build-depends. Namely:
- #768707 [S|+P| ] [src:sphinxcontrib-blockdiag]
- #768708 [S|+P| ] [src:sphinxcontrib-nwdiag]
- #768739 [S|+P| ] [src:sphinxcontrib-actdiag]
- #768765 [S|+P| ] [src:sphinxcontrib-seqdiag]
On all of the 4 cases, the issue is that python-sphinx-testing, and
python3-sphinx-testing didn't make it on time for the release.
So we have 2 ways to fix the issue:
- 1/ Allow python-sphinx-testing to get in Jessie
- 2/ Remove all sphinx-testing tests and build-depends from the above
4 packages, and unblock them from Sid so that they migrate to Jessie.
It is my understanding that the goal of the distribution freeze is to
improve Q/A. sphinx-testing is just there for Q/A, so makes a lot of
sense to allow it to get in Jessie. It doesn't serve any other purpose
but providing Q/A for the above 4 packages. Not allowing it to get in,
and choosing option 2 wouldn't help improving quality, quite the
opposite. The only reason why you would refuse to get sphinx-testing in,
would be because you just want to respect establish rules and not make
exception (which I would understand, but not support).