Package Details: calibre-git 9.3.1.r5.g0343c52821-1

Git Clone URL: https://aur.archlinux.org/calibre-git.git (read-only, click to copy)
Package Base: calibre-git
Description: Ebook management application
Upstream URL: https://calibre-ebook.com
Licenses: GPL3
Conflicts: calibre, calibre-common, calibre-python3
Provides: calibre
Submitter: eschwartz
Maintainer: alllexx88
Last Packager: alllexx88
Votes: 19
Popularity: 0.044462
First Submitted: 2015-08-09 15:02 (UTC)
Last Updated: 2026-02-22 22:07 (UTC)

Latest Comments

1 2 3 4 5 6 Next › Last »

alllexx88 commented on 2026-02-22 22:12 (UTC)

@Pulec thanks, I applied your fixes, as well as adding more dependencies and fixing a chroot build. I haven't once encountered test_websocket_basic failure, but since it was reported twice already, I did exclude it. test_piper, with the addition of protobuf dependency, now passes, so I removed the respective exclude.

Pulec commented on 2026-02-17 22:55 (UTC) (edited on 2026-02-18 01:49 (UTC) by Pulec)

as @costor said

new dependencies needed: onnxruntime-cpu espeak-ng-git (AUR)

but additionally for tests [python-tzlocal]*https://archlinux.org/packages/extra/any/python-tzlocal/) is needed

for mathjax missing tex-full it's better to edit the setup/mathjax.py, so in prepare:

+       sed -i 's/tex-full/tex/g' setup/mathjax.py

I didn't have issues with calibre.srv.tests.web_sockets.WebSocketTest.test_websocket_basic at first time, but on other build I did so:

python setup.py test --under-sanitize --exclude-test-name test_piper --exclude-test-name test_websocket_basic

But I did have issues the tests reading my ~/.config/calibre/global.py.json where language is set "language": "cs", and tests expected czech strings

fixed that with an updated check()

check() {
        cd "${pkgname%-git}"
        export LANG='en_US.UTF-8'
+       export CALIBRE_CONFIG_DIRECTORY="$(mktemp -d)"
        python setup.py test --under-sanitize --exclude-test-name test_piper
        python setup.py test_rs
- }
+}

I wish the build speed could be improved,, compiling lots of files takes a few minutes while barely using any I/O or CPU

Note: ebook-viewer expects

/usr/share/calibre/user-agent-data.json

calibre-bin has it in

/opt/calibre/resources/user-agent-data.json

costor commented on 2025-09-04 22:38 (UTC)

Needs additional dependencies onnxruntime-cpu and espeak-ng-git. Also needs sudo ln -s /usr/share/mathjax/input/tex{,-full}.js.

Builds still fails on calibre.srv.tests.web_sockets.WebSocketTest.test_websocket_basic test though.

simona commented on 2025-05-20 10:27 (UTC)

it is sometimes as a recurring problem the "gpg: reception from keyserver failed: Permission denied" and I have tried several times to get out of it but without success. the good thing is that sometimes I see it import keys without problems. it is a difficulty of mine. thx for reply.

alllexx88 commented on 2025-05-20 10:24 (UTC)

@simona have you tried?

# pacman-key --recv-keys 3CE1780F78DD88DF45194FD706BC317B515ACE7C

simona commented on 2025-05-19 16:46 (UTC)

missing pgp 3CE1780F78DD88DF45194FD706BC317B515ACE7C key

alllexx88 commented on 2025-05-11 09:14 (UTC)

@Muflone Noted, thanks for the explanation and the reference!

Muflone commented on 2025-05-10 18:56 (UTC) (edited on 2025-05-10 19:48 (UTC) by Muflone)

@alllexx88 the VCS packages have the pkgver function which is used to get the latest version when the rebuilt is done. This implies the users will automatically get the latest version without any need of you bumping the package pkgver.

See also https://wiki.archlinux.org/title/Arch_User_Repository#Flagging_packages_out-of-date

Note: VCS packages are not considered out of date when the pkgver changes; do not flag them as the maintainer will merely unflag the package and ignore you. AUR maintainers should not commit mere pkgver bumps.

alllexx88 commented on 2025-05-04 11:17 (UTC)

@alerque I agree about tests, it makes sense to have them. However, they needed fixing, so I fixed them and the build command, based on Archlinux calibre package. As for man pages, I wasn't "no longer installing" generated man pages: in fact, they weren't being generated at all before I adopted the package -- I only removed the copy command that failed due to man pages not present in the sources. But it makes sense to have them generated, so I added python setup.py man_pages to the build command and python-sphinx to makedepends, and I'm packaging them now.

As for bumping VCS package, can you point me to an Arch wiki page that says this? I haven't been able to find anything on https://wiki.archlinux.org/title/VCS_package_guidelines

Also, the auto update bot won't bump a package blindly: it checks for new commits daily, and bumps only if a test build is successful. The reasoning for bumping is to notify users using AUR helpers of an available update.

alerque commented on 2025-05-04 10:00 (UTC)

@allexx88

  • VCS packages do not need "bumping". Please don't do that, and take off the update bot. It's is never appropriate to auto bump a VCS package.

  • Removing the tests is not "fixing" the build.

  • No longer installing the generated man pages is not "fixing" the build.

1 2 3 4 5 6 Next › Last »