Package Details: calibre-git 5.14.0.r108.g6e32092098-1

Git Clone URL: (read-only, click to copy)
Package Base: calibre-git
Description: Ebook management application
Upstream URL:
Licenses: GPL3
Conflicts: calibre, calibre-common, calibre-python3
Provides: calibre
Replaces: calibre-common-git, calibre-python3-git
Submitter: eschwartz
Maintainer: eschwartz
Last Packager: eschwartz
Votes: 15
Popularity: 0.24
First Submitted: 2015-08-09 15:02
Last Updated: 2021-04-11 18:49

Dependencies (50)

Required by (5)

Sources (4)

Latest Comments

1 2 3 Next › Last »

malcolm commented on 2021-06-05 21:12

The build stops when displaying this

Could not find QtWebEngineProcess

I have all the dependencies of calibre installed, as well as qt5-webengine (5.15.4-3) python-pyqtwebengine (5.15.4-1)

eschwartz commented on 2020-12-07 13:19

This has been previously requested on the bugtracker for community/calibre too (in that case, the user wanted calibre-server to be split out), and was just as invalid there.

calibre isn't multiple programs in one package. It is one unified codebase with a number of entry points into it. Qt5-base is used essentially everywhere. The conversion pipeline directly relies on a headless plugin with mandatory x11 client libraries, even though ebook-convert doesn't run in a GUI, but doesn't require a running xorg server. etc.

Inporting any part of the codebase will inevitably result in most or all of the dependencies being used, simply because a lot of functionality you might not think is related, nevertheless is.

lenormf commented on 2020-12-07 07:55

Any way you could please split this package into separate ones, to allow installing Xorg-less utilities like calibredb on a server without pulling X11 dependencies?

eschwartz commented on 2019-11-22 06:34

I've pushed an update I've been experimenting with -- calibre-python3-git and calibre-git now depend on a "common" package, and you can install one or both as you wish. I'd still advise having the calibre2 version around, though...

eschwartz commented on 2019-11-15 02:24

Yeah, let me go rebuild my custom repo for python3.8 right now.

chrisjbillington commented on 2019-11-15 01:59

@eschwartz, thanks for this package. When you have time, would you be able to rebuild it for python 3.8 in your custom repo? Many thanks!

c-reeder commented on 2019-10-31 23:14

@eschwartz, thanks for the response! Okay, so.....pacman -Qkk qt5-base reports no errors and according to pacman -Qi qt5-base, I'm using the official version from the repos maintained by "Antonio Rojas".

I just did a chroot test, and sure compiled no problem. Could it have to do with the fact that I also have some mingw-64-qt packages installed? I would think not, but it's the only other QT-providing package that I can think of that I have installed.

eschwartz commented on 2019-10-30 03:07

@doctorguapo, I have no idea why that would happen. Does it build in a clean chroot? Does pacman -Qkk qt5-base report any issues? Can you double-check in the output of pacman -Qi qt5-base that you're using the package from the official repos?

For some reason, it would seem you're missing some formats in the output of:

python -c "from PyQt5.QtGui import QImageReader; print(['utf-8') for f in QImageReader.supportedImageFormats()])"

c-reeder commented on 2019-10-25 22:04

For whatever reason, everything compiles fine for me, but when I get to the check() phase, several tests fail with the same error:

ValueError: Failed to export image as JPEG with error: Unsupported image format

Then at the end, it gives me:

AssertionError: Items in the second set but not the first: 'jpg' 'gif' 'svg' 'ico' : Qt doesn't seem to be able to load some of its image plugins. Available plugins: {'xpm', 'xbm', 'pgm', 'ppm', 'png', 'bmp', 'pbm'}

This seems very strange to me given that according to jpg is one of the file types supported by default.

eschwartz commented on 2019-04-24 19:03

Given recent efforts to port calibre to python3, which are finally reaching an interesting stage, I have turned this into a split package providing a python3 component. Some things work, some things don't, so I strongly expect you'll want to have the python2 version available at a minimum... so they will share many files and the python3 version will depend on the python2 version.

I provide prebuilt packages in my custom repository, signed by my TU packaging key:

See for more discussion on the port.