View Single Post
Old 05-29-2020, 11:27 AM   #2125
NiLuJe
BLAM!
NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.
 
NiLuJe's Avatar
 
Posts: 13,506
Karma: 26047202
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
For a bit of context, almost *every* distro has been packaging calibre in a subtly to overtly broken way (and usually also based on an hilariously outdated version, as @DNSB just showed), which is why it's *always* been considered an unsupported configuration. Might work well enough, or it might not. In any case, as soon as you start asking for support, the first answer will *always* be: come back after trying the actually supported setup (i.e., the upstream binary install).

The Python 2 EoL just made everything "worse" in that respect, but it's not a new thing.

If you want your distro's package to behave properly (or at least better), complain to its package maintainer. And point him/her to the Arch package, which is the gold standard for a downstream calibre package.

(Which won't change the fact that running Calibre under Python 3 is currently still considered experimental).

Last edited by NiLuJe; 05-29-2020 at 11:37 AM.
NiLuJe is offline   Reply With Quote