The problem would be fixed by moving python-xml from a 'suggests' back to a 'recommends' dependency. However, this would apparently violate Debian policy. The ideal solution would probably be something suggested in the Debian report:
"Maybe you might want to apply the following idea: patch (debian-side)
the warning/information messages to display that the user is required to
install the `python-xml' (or other...) package(s) to have this extension
working, that's why it was put as a `Suggests:' dependency. This way,
the user is told exactly what to do (e.g. `Please install the
"python-xml" package to have this extension working')"
Thanks for your report.
There has been some discussion of this in Debian - see http:// bugs.debian. org/cgi- bin/bugreport. cgi?bug= 389540 and the bugs linked in comments there.
The problem would be fixed by moving python-xml from a 'suggests' back to a 'recommends' dependency. However, this would apparently violate Debian policy. The ideal solution would probably be something suggested in the Debian report:
"Maybe you might want to apply the following idea: patch (debian-side)
the warning/information messages to display that the user is required to
install the `python-xml' (or other...) package(s) to have this extension
working, that's why it was put as a `Suggests:' dependency. This way,
the user is told exactly what to do (e.g. `Please install the
"python-xml" package to have this extension working')"