Bug#883155: fixed in inkscape 1.0~beta1+ds-1
Hey Mattia,
> Format: 1.8
> Date: Fri, 04 Oct 2019 23:08:14 +0200
> Source: inkscape
> Architecture: source
> Version: 1.0~beta1+ds-1
> Distribution: experimental
> Urgency: low
> Maintainer: Debian Multimedia Maintainers <debian-multimedia@lists.debian.org>
> Changed-By: Mattia Rizzolo <mattia@debian.org>
> Closes: 883155 933678 933688
> Changes:
> inkscape (1.0~beta1+ds-1) experimental; urgency=low
> .
> * New upstream version 1.0~beta1. Closes: #933678
> http://wiki.inkscape.org/wiki/index.php/Release_notes/1.0
> https://inkscape.org/release/inkscape-1.0beta1/
> + Also include the extensions. Closes: #933688
> * Drop the Drop_PS_and_PDF_support_in_MimeType patch.
> This was added without any real satisfying explanation many years ago,
> and I could figure why anybody would want this.
> Let's stop this unjustified divergence from upstream.
> * Add back Marc Jeanmougin's upstream key.
> * Drop all patches, mostly applied upstream.
> * Move everything from Python2 to Python3. Closes: #883155
> + d/p/python3: Add patch to call python3 instead of python while building.
> * d/control: Update Build-Depends.
> * Bump debhlper compat level to 12.
> * Remove an extension that work only on Windows. #930154
How close do you think we are to uploading inkscape with "Move
everything from Python2 to Python3. Closes: #883155" to unstable
(even in a 1.0 beta status)?
We are at a point where we can remove
python-bs4+python-soupsieve+python-html5lib+pyhton-lxml (which is a
closed set and needs to go at the same time) but that would break
inkscape, which Recommends python-lxml.
inkscape in unstable already has a missing Recommends (python-scour)
but i'm not sure how much breakage would cause if we remove
python-lxml too.
Can you give us your take on this? tbh i'd like to proceed with the 4
packages removal mentioned above rather quickly, as they are blocking
several other packages from removal.
Thanks,
Sandro
Reply to: