Arch Linux User Repository

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...

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

@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!

@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 arojas@archlinux.org".

I just did a chroot test, and sure enough....it 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.

@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([f.data().decode('utf-8') for f in QImageReader.supportedImageFormats()])"

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 https://doc.qt.io/qt-5/qtimageformats-index.html jpg is one of the file types supported by default.

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: https://wiki.archlinux.org/index.php/Unofficial_user_repositories#eschwartz

See https://github.com/kovidgoyal/calibre/pull/870 for more discussion on the port.

I don't understand your meaning at all. For one, neither of those two are dependencies at all -- one is a makedepends and the other is a checkdepends. On top of that, why would sip have anything to do with Wayland vs. xorg? At least xorg-server-xvfb is genuinely an xorg-related package, if only it weren't merely a checkdepends.

on wayland the dependency xorg-server-xvfb-1.20.3-1-x86_64, and sip seems surprising?

@evamvid I've tried adding the -git suffix to rapydscript-ng but to no avail, makepkg still outputs

==> ERROR: 'pacman' failed to install missing dependencies.
==> WARNING: Failed to remove installed dependencies.