4 ms·

I'm running Calibre on Python 3 (via an Arch package provided by one of the people working on the port). It and mercurial/tortoisehg and the only remaining reas

I'm running Calibre on Python 3 (via an Arch package provided by one of the people working on the port). It and mercurial/tortoisehg and the only remaining reasons Python 2 is on my system. All of these things will be on Python 3 soon enough. Why doesn't Debian just ship the unreleased Python 3 port of Calibre? It's not like Debian restricts themselves to only formal upstream releases, they have never hesitated to backport patches to unreleased versions. If lacking Python 3 support is such a massive bug, wouldn't using patches that have not been officially released, that fix the bug, be acceptable? Debian testing isn't Debian stable, there is not a reasonable expectation that the code shipped is perfect. Mercurial also works on Python 3, though it's only a beta. I could understand not shipping it because version control bugs can be serious, but hey, someone's gotta test the beta. I've used it and it not encountered any bugs, but went back to py2 because tortoisehg won't work with Python 3 mercurial yet (and then bitbucket dropped mercurial support so now I'm moving everything to git, grumble grumble, probably will sadly stop using mercurial altogether within the next year).

Mathnerd314 7y ago
I think you mean this package? https://aur.archlinux.org/packages/calibre-python3-git/ https://aur.archlinux.org/packages/calibre-python3-git/ Judging from https://bugs.launchpad.net/calibre/+bug/1714107/comments/11 https://bugs.launchpad.net/calibre/+bug/1714107/comments/11 the Arch maintainer doesn't think highly of Debian as it has been buggy in the past. OTOH he's biased because he's on Arch. Here's a recent post from the Debian maintainer: https://www.preining.info/blog/2019/10/state-of-calibre-in-debian/ https://www.preining.info/blog/2019/10/state-of-calibre-in-d.... The tl;dr is that most/all of the work is done but he's holding off updating unstable to Python 3 because he doesn't want to break external plugins. He also mentions that he can't update to 4.0 or higher because Debian still hasn't updated Qt to 5.12. That seems slightly inaccurate as it's in experimental (https://packages.debian.org/experimental/qt5-default); https://packages.debian.org/experimental/qt5-default); I think the maintainer could do an upload of a Calibre 4.x using Qt 5.12 & Python 3 to experimental. But experimental is not in common use regardless. The post seems to be an extension of https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936270#87 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936270#87
_delirium 7y ago
It's definitely possible for Debian to package unofficial releases out of the upstream VCS. You can sometimes tell that's what happened because it'll have something like ~git20191005.f8ab33 in the Debian package's version number. In this particular case, the Debian maintainer seems to prefer to wait for upstream to release an official Python3-supporting version of Calibre though: https://github.com/norbusan/calibre-debian/blob/master/debian/NEWS https://github.com/norbusan/calibre-debian/blob/master/debia... It's basically up to the maintainer either way. The freeze for the next Debian release is at least months away (no date set yet), so it's not too urgent, and waiting for upstream is still reasonable at this point.

Mathnerd314 7y ago

I think you mean this package? https://aur.archlinux.org/packages/calibre-python3-git/ https://aur.archlinux.org/packages/calibre-python3-git/ Judging from https://bugs.launchpad.net/calibre/+bug/1714107/comments/11 https://bugs.launchpad.net/calibre/+bug/1714107/comments/11 the Arch maintainer doesn't think highly of Debian as it has been buggy in the past. OTOH he's biased because he's on Arch. Here's a recent post from the Debian maintainer: https://www.preining.info/blog/2019/10/state-of-calibre-in-debian/ https://www.preining.info/blog/2019/10/state-of-calibre-in-d.... The tl;dr is that most/all of the work is done but he's holding off updating unstable to Python 3 because he doesn't want to break external plugins. He also mentions that he can't update to 4.0 or higher because Debian still hasn't updated Qt to 5.12. That seems slightly inaccurate as it's in experimental (https://packages.debian.org/experimental/qt5-default); https://packages.debian.org/experimental/qt5-default); I think the maintainer could do an upload of a Calibre 4.x using Qt 5.12 & Python 3 to experimental. But experimental is not in common use regardless. The post seems to be an extension of https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936270#87 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936270#87

_delirium 7y ago

It's definitely possible for Debian to package unofficial releases out of the upstream VCS. You can sometimes tell that's what happened because it'll have something like ~git20191005.f8ab33 in the Debian package's version number. In this particular case, the Debian maintainer seems to prefer to wait for upstream to release an official Python3-supporting version of Calibre though: https://github.com/norbusan/calibre-debian/blob/master/debian/NEWS https://github.com/norbusan/calibre-debian/blob/master/debia... It's basically up to the maintainer either way. The freeze for the next Debian release is at least months away (no date set yet), so it's not too urgent, and waiting for upstream is still reasonable at this point.