I've had a look into the possibility of back porting python-lxml 3.2 and
it looks like doing so will also require back porting a newer
python-setuptools which in turn will require back porting other packages.
I'm not comfortable with the idea of back porting so many packages that
I'm not familiar with just to satisfy this dependency.
The most recent version that will easily back port to wheezy is
python-lxml 2.3.5-1. All dependencies are already in wheezy and this is
the version that would resolve the current conversion bug. I've done a
trial back port of that version and will test calibre a little in a VM
running against it.
This would resolve the current bug with an additional update to the
calibre back port to add >= 2.3.5-1 as a dependency. However, whether
calibre makes uses of any other functionality from python-lxml that was
added between 2.3.5-1 and the version it lists as a dependency on their
site (3.2.1) I couldn't say.
The options appear to be, back port 2.3.5-1 and hope calibre doesn't
utilise anything from a newer version in a way that would break. Or,
remove the existing calibre back port as document conversion is a pretty
critical feature to leave broken by the back port.
Any suggestions for better ways to solve this or should I go ahead with
a 2.3.5-1 testing and back port?
Regards,
Gary
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
