[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#813562: Project maintainer here



I'd suggest putting ocrmypdf in a submodule with the Debian things outside. Then setup tools should pick up tags correctly rather than generating whatever "git describe" decides to call the current revision in your merged repo.
On Sat, Feb 13, 2016 at 16:46 Sean Whitton <spwhitton@spwhitton.name> wrote:
Hello,

Thank you for your e-mail.

On Sat, Feb 13, 2016 at 01:35:10AM +0000, James R Barlow wrote:
> On Fri, 12 Feb 2016 at 17:05 Sean Whitton <spwhitton@spwhitton.name> wrote:
>     I have a non-packaging question that I'd like to take this opportunity
>     to ask you: in your changelog entry for 3.2, it's explained that the new
>     "lossless reconstruction" feature is disabled by --deskew and
>     --clean-final but otherwise PDF contents are now added to but not
>     modified by OCRmyPDF.  I had observed that OCRmyPDF makes my PDFs much
>     smaller without making them any harder to read, presumably by changing
>     the content, and I rather liked this feature.  Can I turn it back on?
>     Or was --clean-final doing this and turning that on would be enough?
> Oh, interesting. By smaller I take it mean the file size was reduced, not
> resampling of images. Any chance you can send me an example input PDF? (Dropbox
> is best.)

Sure, I'll do that once I can make my 3.2 package build.

> If you build the package around a wheel or tarball obtained from PyPI,
> setuptools_scm should be able to get the version out. It will fail to determine
> the version from a Github tarball.

I'm trying to build out of git: I have a branch with the Debian control
files and I merged your 3.2 tag into that.  Do you know how I can make
setuptools_scm successfully determine the version from that?  How do you
do your builds during development?

--
Sean Whitton

Reply to: