| 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: | 130 |
| Popularity: | 2.85 |
| First Submitted: | 2014-01-27 11:36 (UTC) |
| Last Updated: | 2025-02-28 03:49 (UTC) |
@fbrennan I was using setuptools_scm_git_archive a few years ago, but it was causing some problems (details of which I don't remember), so I removed it. Maybe I should try it again.
Either way, easiest thing to do is wait for PyPI. Normally it's only 20 minutes behind Github.
@jbarlow At least with the way we're building it right now, we can't build Github tarballs due to a known issue in setuptools (or in Github?). Apparently setuptools puts its metadata inside the Git repository, and because Github's tarballs don't include a git repository, the package won't build from Github.
Last night I found out that I could patch your setup.py (see https://pypi.org/project/setuptools_scm_git_archive/ for details) and force it to build anyway, but I thought by that point I must be doing something wrong and you never intended for downstream packagers to do something like that, so decided to wait for PyPI.
Aww, thanks everyone. :)
v7.0.3 is PyPI as of a few days. Normally Github and PyPI are nearly in lockstep, but Travis was having network problems last weekend and failed to deploy v7.0.3 to PyPI (which it does for me). PyPI releases are just distributions of the tagged releases on Github. It's a little better to use PyPI's sdist since it is smaller than a Github checkout.
Thank you everyone. Maintaining the package is the least I could do because I use ocrympdf a lot, and I found the developer extremely cordial and helpful when I had a problem with it while OCR'ing an Esperanto PDF.
Regarding version 7.0.3, someone flagged the package over this, that version is not yet on PyPI. As far as I know, what's on Github is development, while what's on PyPI is stable. So I'm assuming 7.0.3 is beta since it's not yet on PyPI. As soon as it is on PyPI I will update the PKGBUILD.
If my understanding of this is wrong, feel free to enlighten me.
Thanks to the maintainers and jbarlow for this utility is clearly ULTIMATE (necessary, indispensable, decisive for manipulating PDF files).
I've used the git version of img2pdf, rebuild some AUR packages (python-pikepdf, pybind11, pngquant...) and it works great :D
I'm the author of ocrmypdf and pikepdf - great to see the community here working away on the update. Several changes here are due deprecated features being removed in Python 3.7.
As of pikepdf 0.3.1, just released today, pybind11.patch will be unnecessary.
A few comments on dependencies compared to https://pastebin.com/84Tb6K6S: - jbig2enc should be added - leptonica should be added explicitly (>= 1.76.0, implied by tesseract) - qpdf should be added explicitly (>= 8.1.0, implied by pikepdf)
@fbrennan Thanks for adopting it! Glad I could help out the community.
Here are two fixes that escaped my attention:
(1) PKGBUILD of ocrmypdf is missing one depends=( ... 'python-reportlab>=3.3.0' ... )
(2) PKGBUILD of python-xmp-toolkit similarly is missing one depends=(... 'python-pytz')
Everything should be checked with namcap -i <pkgbuild|final .xz=""> anyhow.</pkgbuild|final>
May I also suggest to you to ask the pikepdf guy on Github why pybind11.patch is needed and also if that is the correct fix.
Thank you for the guide @bsdice ...
I adopted the package and will push a revised package for 7.0.2. (Unfortunately, have to wait for the python-ruffus package to either be disowned or updated. Will update as soon as that's done.)
Unfortunately, I haven't had much time to maintain this package as of late. I'm orphaning it so that someone with more time can take over.
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.