control: retitle -1 sigil: make it work with python 3.5 control: tag -1 sid - patch (sid to avoid an autoremoval from testing with no gain)
On Tue, Jan 12, 2016 at 11:43:54PM -0500, Scott Kitterman wrote:
> sigil should have depends on a python3 interpreter. The attached patch will
> do this and also make the package binNMUable to support a change in the
> default python3 version. Despite the python2.7 recommends you have now, this
> application does appear to be built for python3.
No.
sigil is not binNMU safe. For example a locally test-rebuild against
libpython3.5 succeeds, but then segfaults.
Furthermore, it doesn't strictly require the python interpreter to work,
but it's only needed to launch external plugins, so Recommends is
correct here. There is libpython3.4 in Depends which is instead more
correct.
Then there is the problem that aforementioned plugins are made to work
either with python 2.7 or python 3.4 only, which is pity in this case.
I'll try to think of a solution and to engage upstream for this soon.
> Please let me know if you're OK with an NMU or if you'd like to take care of
> it.
I'd very welcome a NMU fixing this properly, but sadly this is not the
right solution :(
> It would be nice to get this resolved quickly to support the current
> python3.5 transition.
afaik the python 3.4 → 3.5 default change is not tied with sigil, so it
shouldn't affect it.
Though yes, it'll affect subsequent python 3.4 removal. If I'm unable
to fix this in time I think I'm able to temporarly disable/break
external plugins support.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: http://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
signature.asc
Description: PGP signature
