Package Details: ocrmypdf 16.3.1-1

Git Clone URL: https://aur.archlinux.org/ocrmypdf.git (read-only, click to copy)
Package Base: ocrmypdf
Description: A tool to add an OCR text layer to scanned PDF files, allowing them to be searched
Upstream URL: https://github.com/ocrmypdf/OCRmyPDF
Licenses: MPL2
Submitter: dreuter
Maintainer: fbrennan (pigmonkey)
Last Packager: pigmonkey
Votes: 111
Popularity: 2.52
First Submitted: 2014-01-27 11:36 (UTC)
Last Updated: 2024-05-21 15:33 (UTC)

Pinned Comments

fbrennan commented on 2023-05-12 22:54 (UTC)

The flag was invalid and has been removed with no action taken as no new version was released. There's nothing to do for this package; no new release has been made. Rebuild, as @eclairevoyant has said.

Latest Comments

« First ‹ Previous 1 .. 8 9 10 11 12 13 14 15 16 17 18 .. 22 Next › Last »

brianmercer commented on 2020-01-13 00:01 (UTC)

Version 9.2.0 release notes state that qpdf is no longer required as a dependency.

I built it without qpdf and it seemed to compile and run fine.

sagittarius commented on 2019-12-09 14:30 (UTC) (edited on 2019-12-11 13:47 (UTC) by sagittarius)

Please update to 9.1.1 Just change the source link and the SHA256 and it works as is.

$ ocrmypdf --version

9.1.1

Edit PKGBUILD

pkgver=9.1.1

source=("https://files.pythonhosted.org/packages/af/7f/234e357557233d618c5b40d066389de6203c48a1697653285af541fff582/ocrmypdf-9.1.1.tar.gz")

sha256sums=('656dd9cec46b2c3a8a1a4b98e7bb00dd95adb98229d63d397b422679cfbbb88e')

If necessary, rebuild python-pdfminer.six

brianmercer commented on 2019-12-02 14:58 (UTC)

Current version 9.0.5-1 is broken because of an update of python-pdfminer.six in the aur to version 20191110-1.

Error: "The 'pdfminer.six<=20191020,>=20181108' distribution was not found and is required by ocrmypdf"

Please update, thanks.

fbrennan commented on 2019-11-09 05:20 (UTC) (edited on 2019-11-09 05:20 (UTC) by fbrennan)

Github archives are unusable without hacks for Python AUR packages. That's because they don't include the .git directory, required by python-setuptools. The PyPI archive must be used.

jbarlow commented on 2019-11-09 05:12 (UTC)

@brianmercer CI is set up to build wheels and deploy to PyPI whenever a git tag is pushed, so tags should always be consistent with PyPI. But it's probably cleaner to install the .tar.gz from PyPI than Git - smaller download since it's not pulling the whole history.

brianmercer commented on 2019-11-08 18:23 (UTC)

I'm no expert on PKGBUILD.

Is there any downside to rewriting the PKGBUILD to use git tags instead of versions from pypi? It looks like @jbarlow is pretty diligent with the github tags. https://github.com/jbarlow83/OCRmyPDF/tags

And PKGBUILD supports git tags. https://wiki.archlinux.org/index.php/VCS_package_guidelines#The_pkgver.28.29_function

Does an ocrmypdf-git package need to be by commit or can it be by tag or release? Do the aur managers like yay (which I use) check devel versions by commit or can it check by tags?

pigmonkey commented on 2019-11-06 17:11 (UTC)

I'd be happy to help maintain the package if fbrennan is no longer interested.

rien333 commented on 2019-11-06 09:50 (UTC) (edited on 2019-11-06 09:50 (UTC) by rien333)

This is several versions out of date: https://github.com/jbarlow83/OCRmyPDF/releases. An update would be great, especially because there is a fix for a fatal ocrmypdf crash (see https://github.com/jbarlow83/OCRmyPDF/issues/448)

jbarlow commented on 2019-11-05 10:31 (UTC)

@brianmercer That is completely correct. ruffus, defusedxml, lxml should all be removed. -Upstream

brianmercer commented on 2019-11-05 02:47 (UTC)

It looks like version 9.0 removed the dependency on ruffus. And version 7.0 removed the dependency on defusedxml. And version 3.0 removed the dependency on lxml.

« First ‹ Previous 1 .. 8 9 10 11 12 13 14 15 16 17 18 .. 22 Next › Last »