[Impact]
python-mkdebian always adds a wrong KDE dependency whatever QT class is used in code. Package should add KDE dependency only if a KDE package is used.
[Test Case]
Use python-mkdebian on a QT only software always adds a KDE dependency
[Regression Potential]
No regression here because adding a wrong KDE dependency to a QT only software is a bug. If python-mkdebian fails to add a KDE dependency to a QT only software and this software really relies on python-kde4-dev, you should fix the software, not python-mkdebian.
[Impact]
python-mkdebian always adds a wrong KDE dependency whatever QT class is used in code. Package should add KDE dependency only if a KDE package is used.
[Development Fix] /code.launchpad .net/~angeloc/ python- distutils- extra/fix- for-1002076/ +merge/ 106549
Fixed upstream, merge proposal here: https:/
[Stable Fix] /code.launchpad .net/~angeloc/ python- distutils- extra/fix- for-1002076/ +merge/ 106549
Fixed upstream, merge proposal here: https:/
[Test Case]
Use python-mkdebian on a QT only software always adds a KDE dependency
[Regression Potential]
No regression here because adding a wrong KDE dependency to a QT only software is a bug. If python-mkdebian fails to add a KDE dependency to a QT only software and this software really relies on python-kde4-dev, you should fix the software, not python-mkdebian.