Also need this.
--- /home/jeff/sid-chroot/transition/tesseract-5.3.4/debian/control
2024-03-19 23:45:47.0 -0700
+++ /home/jeff/leptonica/transition/tesseract-5.3.4/debian/control
2024-10-05 14:30:47.928986783 -0700
@@ -13,7 +13,7 @@
Package: tesseract-ocr
Architecture: any
Depends: ${s
leptonlib 1.83.1-4 uploaded to unstable. Also did NMU for dependency level
2 (tesseract, jbig2enc, k2pdfopt). Possibly I did the NMU too soon and the
autobuilders will get confused; will find out soon enough.
Hi Sebastian, may I proceed with transition?
Control: tags - moreinfo
control: tags 1081319 - moreinfo
libleptonica6 has been accepted into experimental, and I am ready to
proceed.
I have filed bugs with patches for the reverse dependencies that need
changes.
Bug numbers are 1081969 1081968 1081970
Currently waiting for leptonica6 to clear the NEW queue and enter
experimental.
Source: tesseract
Version: 5.3.4-1.1
Severity: normal
Tags: patch
X-Debbugs-Cc: j...@debian.org
Library name is changing from liblept to libleptonica. Transition bug
is 1081319
diff -r -u ../transition.bak/tesseract-5.3.4/debian/rules
tesseract-5.3.4/debian/rules
--- ../transition.bak/tesseract
Package: kylin-scanner
Severity: normal
Tags: patch
X-Debbugs-Cc: j...@debian.org
Leptonica is changing its library name from liblept to libleptonica.
Transition bug is 1081319.
--- ../transition.bak/kylin-scanner-1.0.0/src/src.pro 2020-09-03
09:38:45.0 +
+++ kylin-scanner-1.0.0/sr
>
>
> \
diff -u -r /transition.bak/jbig2enc-0.29/configure.ac ./configure.ac
--- /transition.bak/jbig2enc-0.29/configure.ac 2017-01-30 17:27:36.0 +
+++ ./configure.ac 2024-09-12 16:39:05.0 +
@@ -73,7 +73,7 @@
fi],
[libtool_patch_use_rpath=$enable_rpath])
-AC_CHECK_LIB([
Source: jbig2enc
Version: 0.29-2.1
Severity: normal
Tags: patch upstream
X-Debbugs-Cc: j...@debian.org
Leptonica API has changed over the years, and we need to make some
small changes as the newer Leptonica enters Debian. The leptonlib
transition bug is 1081319
-- System Information:
Debian Rel
The library name has changed from liblept to libleptonica. So I have now
changed the package name from liblept5 to libleptonica6. This is uploaded
to experimental as leptonlib_1.84.1-3. I am including the revised Ben file
below and attaching the patch for the most complex reverse dependency. All
re
Package: release.debian.org
Severity: normal
X-Debbugs-Cc: lepton...@packages.debian.org, j...@debian.org
Control: affects -1 + src:leptonlib
User: release.debian@packages.debian.org
Usertags: transition
Upstream has changed the name of the library.
BEFORE: liblept.so.5
AFTER: libleptonica.so
Yes, I made a mistake with respect to 1.2.2. Upstream's official patch is
here. I am going to attempt a high urgency upload during the next houw with
1.2.2 + this patch. If that fails for any reason, NMU welcome without
delay.
https://chromium.googlesource.com/webm/libwebp/+/4f1839957115fa4713ed74
libwebp 1.2.1-7 has been successfully uploaded to unstable.
Anthony and Iustin, help is very strongly appreciated for the NMUs.
# remove the moreinfo tag
tags 1003548 - moreinfo
thanks
Sebastian, may we move forward with ibwebp?
To make it super clear, here is the updated formal request with updated Ben
file.
===
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
Hello Release Team,
We would like to transition libwebp to a new upstream version 1.2.1-6
The package has been corrected with version 1.2.1-6 which has
been uploaded to experimental.
Please let us know if we can proceed with the upload to unstable. Also
a binNMU rebuild of reverse dependencies would be required afterwards.
Maintainer is "less active" but still in good contact with upstream. I was
going to package the latest version several months ago, but there was a
soname bump and transitions were not allowed due to Debian's release cycle.
Happy to work with anyone on updating webp.
BCC: Stefan Weil since I don't know if he wants his email posted in
bugs.debian.org
Regarding: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949638
Thank you, Peter.
1. The URL for the patch is 404.
2. There may be some subtlety with -march=native, specifically related to
detection of SIMD
leptonica-progs also?
Hi Janusz,
Tesseract 4 uses tesseract-ocr-deu and tesseract-ocr-script-frak.
Tesseract 3 uses tesseract-ocr-deu-frak
I am worried about confusing users. If we include both sets of language
data in Debian, there will a huge number of choices, and some users
might feel overwhelmed. However, Alexand
> tesseract-ocr package provides arch-independent service (cli)
The command line interface (cli) application 'tesseract' in the
tesseract-ocr package is written in C++. It is not architecture
independent. Therefore I don't think it should be marked as
Multi-Arch: foreign.
Believed fixed in Debian package 1.76.0-1
Status of various vulnerabilities, as per upstream:
* CVE-2018-7442: potential injection attack because '/' is allowed
in gplot rootdir.
Functions using this command have been disabled by default in the
distribution,
Tesseract in Debian just added a build time smoke test AND Stefan fixed
the big-endian
problem. Should be live tomorrow in Sid. Assuming that works well, Graham
should be
able to re-activate the disabled OCRMyPDF tests. Note that this is Debian
only; Ubuntu
18.04 is out the door so no longer perti
Given the date, it sounds like we have an emergency situation.
I'm really stuck here. My only known access to a big endian is an emulator
with Wheezy.
http://create.stephan-brumme.com/big-endian/
That's good enough for checking suspicious parts of Leptonica. I tried and
found nothing. But i
I think the right thing is to update to the latest jhove release (1.20) but
looks like the build system has changed dramatically. Would love to get a
little help from someone who works with Java packages on a more regular
basis.
Okay, uploading now. Thanks for all the help!
On Mon, Apr 23, 2018 at 4:06 PM, Manuel A. Fernandez Montecelo <
manuel.montez...@gmail.com> wrote:
> 2018-04-23 23:22 GMT+02:00 Manuel A. Fernandez Montecelo
> :
> >
> > This additionally runs the tests,
> > can be disabled with another override_dh_a
Is it sufficient to put Build-Depends: debhelper (>= 11.0.0) in
debian/control and 11 in debian/compat ?
Taking a look
It is possible that older versions are not vulnerable.
$ sudo apt-get install leptonica-progs
$ TMPDIR=/var/tmp fileinfo /tmp/foo.jpg
Error in fopenReadStream: file not found
Error in pixReadHeader: image file not found
Error in writeImageFileInfo: failure to read header of /tmp/foo.jpg
$ filein
This is the patch I used for Leptonica 1.74. It should work fine for
earlier versions.
Upstream used a different approach for addressing the problem in version
1.75.
do-not-mess-with-paths.diff.gz
Description: GNU Zip compressed data
I've been running a PowerPC emulator to track down a different bug.
Not so hard. But it is not fast. Anything specific (and small) that we
want to test for this bug?
http://create.stephan-brumme.com/big-endian/
This is just about strings, right? So something like this will fix the
problem
and resolve this bug? Or am I missing something?
char buf[L_BUF_SIZE];
- fscanf(fp, "Rootname: %s\n", buf);
+ fscanf(fp, "Rootname: %L_BUF_SIZE_MINUS_ONEs%\n", buf);
Hi Bill,
Thanks for the bug report. This is a little tricky, because if you only
install one of the Azerbaijan language packages, the user will see
error messages.
I guess we just don't have a mechanism in Debian for "if you install
one, you need the other as well". That's unfortunate because it
Thanks will fix ASAP.
On Sun, Feb 4, 2018 at 3:08 PM, Andreas Beckmann wrote:
> Package: tesseract-ocr-srp-latn
> Version: 4.00~git15-45ed289-5
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
>
> Hi,
>
> during a test with piuparts I noticed your package is no longer
Package: ftp.debian.org
Severity: normal
We have completed a major consolidation of Tesseract packaging
with the 4.0 release. Previously I used a separate source package
for each language. Now a single source package provides everything.
Please retain the following source packages:
tesseract
tes
Most likely we'll have a fix into Debian within 48 hours.
I've reproduced by setting TMPDIR to /var/tmp. Talking to Leptonica author.
Peter, what do you have set for TMPDIR environment variable? (You can check
this with "env")
I cannot reproduce this problem on Debian Unstable. We have a mystery.
$ tesseract /tmp/ANY/PATH/phototest.tif - -
Page 1
This is a lot of 12 point text to test the
ocr code and see if it works on all types
of file format.
The quick brown dog jumped over the
lazy fox. The quick brown dog jumped
Will investigate.
Attempted fix for Tesseract fix uploaded just now.
I've just uploaded a fix attempt for bug 884903 with Tesseract
4.00~git2188-cdc35338-2. I think it will fix this problem.
We'll get this fixed upstream, and in the meantime I'll try patch enough
into
the Debian package to get the dependencies to build. For gimagereader,
that's a single string -> std::string
Taking a look.
Package: ftp.debian.org
Severity: normal
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878986
okay.
Sure, I can do that. In a related question, do you have any idea how move
tesseract-lang from NEW to Experimental? It has been languising there
since August 23.
Beginning transition. Uploaded to unstable.
>Do the packages in
https://release.debian.org/transitions/html/auto-libwebp.html
>build fine against the new libwebpmux ?
There was a bug the libwep control file. I fixed that and uploaded
0.6.0-2 to experimental just now. Then I did some testing on AMD64 to
answer your question. Everything on th
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
This is a clean ABI bump. I've updated the symbols file appropriately.
New package has been uploaded to experimental.
Please be aware that the primary binary library package (libwebp6) i
If you know who to ask and are willing, I appreciate it.
Otherwise, I'll figure it out eventually.
Yes, I concur. I also checked with upstream (myself) and he agrees too.
On Fri, Mar 10, 2017 at 9:28 AM, Mattia Rizzolo wrote:
> Source: jablicator
> Version: 1.0.1
> Severity: serious
>
> Dear maintainer,
>
> The package doesn't seem to have much popularity these days, with a
> popcon of only 2
What action do people want for this bug beyond the ABI repair in 3.04.01-3?
Sorry, I wasn't aware of the guest account thing. Probably my fault for not
reading
email carefully enough. I am a Debian Developer and will sponsor this
request. Fill
out the information "Information guest needs to supply to sponsoring DD"
and I will
sign it.
https://dsa.debian.org/doc/guest-acco
I've just uploaded 1.74.1-1 to Debian, which contains something
similar to Sean's patch.
Tesseract 4 is known to not work on big endian. Stefan (on CC) is excited
to
take a look if someone can give him access to a big endian machine.
There are no known endian problems with Tesseract 3 or Leptonica, but if any
are definitively found they will get immediate attention.
I am not going to
Ubuntu may have the patch for this. If so, okay to NMU.
https://patches.ubuntu.com/libw/libwebp/libwebp_0.5.1-2ubuntu1.patch
Mhonarc development is not particularly active, and I'm hesitant to mess
with this.
On Sat, Nov 12, 2016 at 5:04 AM, rpnpif wrote:
> Package: mhonarc
> Version: 2.6.19-1
> Severity: wishlist
>
> Dear Maintainer,
>
> The MIME types are hardcoded in mhmimetypes.pl.
> A link with libfile-libmagic-p
Working with upstream on this.
Okay, clearly not webp. Sorry for the noise.
Makefile:1711: recipe for target 'lua/intf/cli.luac' failed
Bas> and vlc FTBFS on mips* before the libwebp NMUs.
Emilio> That needs to be looked at.
Do I understand correctly that the FTBFS is unrelated to webp?
webp 0.5.1 is now in unstable, will see if anything explodes
I have build-tested the reverse dependencies against the new libwebp
version.
>Have you build-tested the reverse dependencies against the new libwebp
version?
I've build tested a bunch of them successfully, and the rest are still
running.
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
This is a new upstream release and includes a soname bump on all three
shared libraries. I've only expressed the primary one in the Ben file;
please update as appropraite. Note that libwe
Thanks. Of course review in conjunction with upstream will do greps
and code searches and stuff like that. But it always possible to miss
something so reports are appreciated. For the files you mentioned:
src/utils.c: will get serious attention in conjunction with upstream
src/xtractprotos.c: che
No, I'm not sure. Leptonica is big and requires a thorough review in
conjunction with
upstream. Thank you for helping identify convertTiffMultipageToPS(), and
please report
anything else you happen to notice on mainline paths. Highly appreciated.
I am removing the following programs from the leptonica-progs package
due to hardcoded predictable paths in /tmp. Between this and the earlier
patch, this solves all reported problems and therefore this particular bug
will be closed. There are additional hardcoded paths in the Leptonica
library it
I will work with upstream on a permanent improvement. In the meantime,
I'm adding a small patch in 1.73-3 that will help with the specific problem
being discussed in de.comp.os.unix.linux.misc.
Acknowledged and taking action.
Believed fixed with 2.6.19-2.
retitle 815919 nmu: tesseract_3.04.01-4 openalpr_2.2.3-1
gimagereader_3.1.2+git368fa8f-2 sikuli_1.0~x~rc3.tesseract3-dfsg1-12
thanks
There are some good reasons to do this sooner rather than later.
Subject: transition: tesseract-ocr
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: transition
Severity: normal
As described in bug #815056, there was a packaging mistake that led to
the brief existance of libtesseract4. This problem has been corrected
and we are
IRC people tell me that a transition bug will fix everything. There is
an existing transition bug #815919.
I've been advised on Debian Devel IRC mainly by juliank to stick
to libtesseract3 and not do libtesseract3a. See bug 815056.
Personally, I am in over my head but the IRC folks sound confident
that this is the right course of action.
P.S. Tersseract 3.04.01-4 has a breaks/replace against the ill fa
jbreiden: Just report a transition bug for release.debian.org to
+transition back
So they rebuild the stuff against the old ABI again
Thanks for working with me and sorry about the trouble.
I don't know what you mean by not closing bug #815056
properly. The bug tracker says it is closed.
https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=no&src=tesseract
If I look at the package tracking system, it seems to be claiming
It must be mad that there is no libtesseract4 anymore. I'm going
to try to get help for that on IRC.
Yikes. I wasn't expecting this for mhonarc 2.6.19. Patches from a perl
programmer appreciated. Will also check with upstream.
I'm in over my head, so I asked for help. The folks on debian-devel
IRC channel advised me to not bump soname and instead attempt
an ABI repair. It was supposed to be harmless to gimagereader.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815056
I'm really not sure what to do at this point.
3.04.01-2 was a messy mistake that was live for relatively short time.
So far, I've been advised by experts to ignore this particular problem.
See bug 815056 for details. Sorry for the trouble.
> There was an accidental ABI breakage a while ago
> And I thought that bumping to libtesseract4 was the right thing to do
...
The important question is: How did this ABI break happen?
Upstream change or only an effect of the C++ transition?
> I had been assuming upstream change
> But actually I
Why? I was asked strongly by a Debian Developer in 794489 to
bump the libtesseract version. I suspect 742027 was related.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794489
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=742027
I historically have a lot of trouble with transitions, and th
Time to admit it, I'm never going to do this. Not opposed to someone else
making an attempt. Note that the next webp release is going to break ABI
compatibility.
Tesseact does need a soname bump as per bug #794489 irrespective
of GCC 5.
I haven't done it, partly due to lack of time, and partly because one of
the comments in that bug was demotivating.
Unless this is an emergency, let's wait for the next Leptonica point
release rather than patching into the Debian package. Upstream
has been notified.
I should have bumped the soname with the 3.04 release, this
is further evidence of that. Will see if upstream has another
point release ready soon, and if so I might combine.
Note that I've done the Tesseract packaging for the last couple
of years, so this problem (and any others) is entirely my f
The authoritative Debian bug for this is #699609 and I would
merge them if it was just a bit easier to do so.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699609
I'd like to think if this were widespread, I'd be hearing about it
from multiple sources. So any sort of confirmation (or refutation)
from others is appreciated.
That's unexpected. Can you please tell me if you also have trouble with
English using the attached image?
tesseract phototest.tif -
Using apt-rdepends -r libtesseract3, I think the affected packages are
gimagereader and libsikuli-script-jni.
>could you please comment on Juliens mail? Do you plan to
>do the proposed changes?
Depends how many packages are affected. Transitions are
a bunch of work, and I think we are also in some special
situation due to the GCC transition. So if it is just one binMNU
then I think that might be the way t
Sounds right to me. My bad.
More progress. Training scripts now ship with 'tesseract-ocr'
package, with some Debian specific instructions in README.debian.
We'll probably be in this state for quite a while.
Thanks, I'll investigate today.
careful, these three languages can't have this or we
get a circular dependency
tesseract-ocr-eng
tesseract-ocr-osd
tesseract-ocr-equ
That's weird. Just to make my life a little easier,
can you also attach non-PDF output, and specifically
identify one of the lines that was eaten by PDF?
Making some progress; they are on github in the
'langdata' repository. Much packaging work still
required, particularly around tesstrain.sh
Sorry, I was under the impression upsteam had integrated the patch. NMU
acceptable, or I can do it when I find time.
1 - 100 of 285 matches
Mail list logo