I gather that accommodating all possible *python* versions is a developmental headache. The security update to *soffice*, which includes *unoconv* and *python-uno*, runs into an error with my python version. See the attached, redacted *apt* log.
First, let me say I *always* apply Debian updates as soon as they are available, and I *never* have a problem with them ... up to now. Second, I aver that I use the vanilla *python* and don't fool around with version levels. On my system:
/usr/bin/python --> /etc/alternatives/python --> /usr/bin/python2.6
... so I don't see how the update installation could have screwed up, and I doubt I am the first or only one to experience this error. I have production requirements for both *unoconv* and *python*.
QUESTION: How can I escalate this problem with *soffice* and Debian development?