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

Bug#815027: marked as done (RFS: ocrmypdf/4.0.7-1 [ITP] -- add an OCR text layer to PDF files)

Your message dated Fri, 4 Mar 2016 15:01:03 +0000
with message-id <20160304144849.GA16456@chase.mapreri.org>
and subject line Re: Bug#815027: RFS: ocrmypdf/4.0.5-1 [ITP] -- add an OCR text layer to PDF files
has caused the Debian Bug report #815027,
regarding RFS: ocrmypdf/4.0.7-1 [ITP] -- add an OCR text layer to PDF files
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
815027: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815027
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package ocrmypdf.

OCRmyPDF generates a searchable PDF/A file from a regular PDF containing
only images.  It uses the Tesseract OCR engine and so supports the 39
languages that Tesseract does.

It is a convenient wrapper around Tesseract, unpaper, qpdf and other
tools for processing scans, obviating the need for a user to construct a
haphazard shell script connecting these tools together.  There are many
such scripts floating around online, but ocrmypdf is much more carefully
put together.

* Package name    : ocrmypdf
  Version         : 4.0.1-1
  Upstream Author : James R. Barlow <jim@purplerock.ca>
* URL             : https://github.com/jbarlow83/OCRmyPDF
* License         : MIT
  Section         : graphics

Download with dget:

    dget -x http://mentors.debian.net/debian/pool/main/o/ocrmypdf/ocrmypdf_4.0.1-1.dsc

Or build it with gbp:

    git clone https://git.spwhitton.name/ocrmypdf
    git checkout pristine-tar   # to create the branch locally, so gbp uses it
    git checkout debian/4.0.1-1
    git verify-tag debian/4.0.1-1 # if you have my key
    gbp buildpackage

Thanks.

-- 
Sean Whitton

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message --- 
On Thu, Mar 03, 2016 at 10:09:11PM -0700, Sean Whitton wrote:
> On Thu, Mar 03, 2016 at 12:39:04AM +0000, Mattia Rizzolo wrote:
> > * somehow, it doesn't build on my local pbuilder (attached full build
> >   log), I'd welcome hints about what went wrong here.
> 
> The errors suggest that the test suite can't write the files it needs
> to.  Maybe because your pbuilder runs in tmpfs?

yes, I keep the build place (where chroots are extracted) in tmpfs.

> After the build fails
> and you are dropped to a shell, does `echo "hello" > tests/resources/foo
> && rm -r tests` work?

yes, it does, seamlessly.

Though, I unmounted tmpfs from BUILDPLACE and it indeed works o.O
why do tests depend on such detail -.-
I can't even think how it notices so (haven't look at the code at all).

> Anyway, I've upgraded to 4.0.7 in the repository and it builds in an
> up-to-date sid pbuilder on my machine.  Perhaps you could try again with
> the new version.

same errors as before.
I'll be curious to see what will happen on the reproducible builds
infra, where pbuilder runs on tmpfs too, if it'll fail expect a bug
report :P

> > * on sbuild (on debomatic) it did build, but autopkgtest failed
> > http://debomatic-amd64.debian.net/distribution#unstable/ocrmypdf/4.0.5-1/autopkgtest
> 
> I think I've fixed this; adt-run passes on my machine.  I'm waiting for
> an account on debomatic so it would be great if you could upload it
> there again.

Well, the chroot seems to be outdated, and apt fails to download
packages...  Guess ci.d.n will check it for us instead :)

> > Another thing: what would you think about keeping the packaging of this
> > in collab-maint?  I shall assume you don't have access to it, but I'd be
> > happy to advocate you for that!
> 
> If the package became collaboratively maintained then I would be happy
> to upload it there, but while it's just me, I'd prefer just to leave it
> where it is for simplicity.

Severl people (including me) use collab-maint as a good place to dump
all packages that don't really need to be in a separate place; from my
pov it also semplifies NMUs, as I can do my work in git and then publish
it in the same place the maintainer keep its work, instead of doing
stuff using just the tarballs, and then forcing the maintainer to
incorporate my work.
Anyway, up to you, if you like to keep it that way, by all means, do! :)


Uploaded to the archive, shall hit NEW soon.

Thanks for your contribution to Debian! :D

-- 
regards,
                        Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540      .''`.
more about me:  http://mapreri.org                              : :'  :
Launchpad user: https://launchpad.net/~mapreri                  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-

Attachment: signature.asc
Description: PGP signature


--- End Message ---
Reply to: