Package Details: epub-tools 3.1-1

Git Clone URL: (read-only, click to copy)
Package Base: epub-tools
Description: Command line utilities for working with epub files
Upstream URL:
Licenses: ISC
Submitter: dno
Maintainer: dno
Last Packager: dno
Votes: 11
Popularity: 0.000000
First Submitted: 2013-02-02 13:59 (UTC)
Last Updated: 2023-09-06 04:35 (UTC)

Latest Comments

1 2 Next › Last »

m040601 commented on 2023-09-07 16:02 (UTC) (edited on 2023-09-07 16:27 (UTC) by m040601)

Relevant issue asking the developer and PKGBUILD maintainer to change the name from "epub-tools" to "epub-tools-bin",

m040601 commented on 2023-09-03 22:14 (UTC) (edited on 2023-09-03 22:38 (UTC) by m040601)

Thanks for the tool and maintaining the PKGBUILD.

Hope you can release a new version soon. I thought the project was dead, because of the "2018", then I noticed this "epub-tools" is actually not a "source" PKGBUILD but a "-bin" PKGBUILD.

You should take the chance and rename it to


Thanks in advance.

PS: More here,

dno commented on 2017-12-26 05:02 (UTC)

I made a radical change to this package. It's now assembled from linux binaries sitting on GitHub instead of building from source (on your machine) when the Arch package is created. This completely avoids a lot of the drama involved in having a working Haskell programming toolchain around.


JohnRobson commented on 2017-10-24 19:17 (UTC)

/usr/sbin/ld: /home/us/.stack/programs/x86_64-linux/ghc-tinfo6-nopie-8.0.1/lib/ghc-8.0.1/rts/libCffi.a(ffi64.o): relocation R_X86_64_32S against `.rodata' can not be used when making a shared object; recompile with -fPIC /usr/sbin/ld: final link failed: Nonrepresentable section on output collect2: error: ld returned 1 exit status `gcc' failed in phase `Linker'. (Exit code: 1) Exit code ExitFailure 1 while running ["ghc","-rtsopts","-threaded","-clear-package-db","-global-package-db","-hide-all-packages","-package","base","-main-is","StackSetupShim.mainOverride","-package","Cabal-","/home/us/.stack/setup-exe-src/setup-mPHDZzAJ.hs","/home/us/.stack/setup-exe-src/setup-shim-mPHDZzAJ.hs","-o","/home/us/.stack/setup-exe-cache/x86_64-linux-tinfo6-nopie/tmp-Cabal-simple_mPHDZzAJ_1.24.0.0_ghc-8.0.1"] in /tmp/stack22297/ Can't continue because stack install failed ==> ERROR: A failure occurred in package(). Aborting... ==> ERROR: Makepkg was unable to build epub-tools.

dno commented on 2016-10-27 00:53 (UTC)

sikmir: Thank you for catching this and reporting.

sikmir commented on 2016-10-26 21:03 (UTC)

dno: Add ghc to dependencies. No compiler found, expected minor version match with ghc-8.0.1 (x86_64-ncurses6) (based on resolver setting in /tmp/yaourt-tmp-sikmir/aur-epub-tools/src/epub-tools-2.9/stack.yaml). Try running "stack setup" to install the correct GHC into /home/sikmir/.stack/programs/x86_64-linux/ ==> ERROR: A failure occurred in package(). Aborting... ==> ERROR: Makepkg was unable to build epub-tools.

giddie commented on 2015-02-09 16:56 (UTC)

Thanks for mentioning the issue, though. I don't use Haskell myself, so cabal-install was pulled in as a dependence, and of course I ran into the same build issue. Maybe the PKGBUILD could catch the process failure and at least provide an error message to suggest update cabal?

dno commented on 2013-04-14 17:09 (UTC)

mikecr: You know, working on the latest, I had some other weirdness happen. Now not sure if what you're seeing wasn't part of that. For now I removed 'cabal-dev update' from the build() function. But everybody do 'cabal update' before building this, like you'd do a 'pacman -Sy' to freshen up, same idea.

dno commented on 2013-04-10 14:49 (UTC)

mikecr: If your cabal package list was old, this can happen. It's just like having stale pacman lists and needing to do an -Sy Bearing that in mind, I'm not sure if it's appropriate for me to make the build do a `cabal update` automatically. We generally don't automate that part of these tools, I guess so as to not hammer servers with it unnecessarily. What do you guys think?