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
severity 1082810 normal
thanks
OpenPGP_signature.asc
Description: OpenPGP digital signature
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.
, Santiago Vila wrote:
El 28/9/24 a las 12:31, Jeff escribió:
What is different about your setup?
LOGNAME=root
If that is the case, I wonder if this really should be severity=serious.
Maybe severity=normal?
OpenPGP_signature.asc
Description: OpenPGP digital signature
I can't reproduce this. The tests pass elsewhere in chroots:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/gscan2pdf.html
What is different about your setup?
OpenPGP_signature.asc
Description: OpenPGP digital signature
I think it's a git change. The text "Auto packing the repository in
background for optimum performance." is being written to stderr, not
stdout, which is dumb IMO as it's not an error. A quick fix is 'cd
/etc; git config gc.auto 0'.
--
m: +61 402 511 927
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
Package: ddcci-dkms
Version: 0.4.2-4
Severity: important
Dear Maintainer,
after trying to install package via apt it reports that the DKMS module could
not be compilled, giving the following output:
root@desu:~# apt install ddcci-dkms
Reading package lists... Done
Building dependency tree... Don
reopen 1025664
thanks
I can still reproduce this in v2.31 in testing.
OpenPGP_signature.asc
Description: OpenPGP digital signature
On 20/11/2023 17:51, Soumyanath Chatterjee wrote:
soumyanath@ganak-desktop:~$ LD_LIBRARY_PATH=/lib/x86_64-linux-gnu/
gscan2pdf
This one works.
Please suggest what changes I need to make to run it normally
For me, this isn't a problem with gscan2pdf, but with the way that
libsane was compile
What about:
sudo ldconfig
cat /etc/ld.so.conf.d/x86_64-linux-gnu.conf
If you start gscan2pdf as follows:
LD_LIBRARY_PATH=/lib/x86_64-linux-gnu/ gscan2pdf
?
Can you start xsane, simple-scan or scanimage ?
OpenPGP_signature.asc
Description: OpenPGP digital signature
It looks like the version of libusb libsane was built against is not the
same as the one you are running with.
There are some similarities here:
https://askubuntu.com/questions/1264001/error-installing-xsane-sane-hplip-etc-with-undefined-symbol-libusb-set-optio
What does the following return?
Please reinstall the packages:
sudo apt reinstall libsane1 libimage-sane-perl
and try to start gscan2pdf again.
OpenPGP_signature.asc
Description: OpenPGP digital signature
On 15/11/2023 12:19, Soumyanath Chatterjee wrote:
I find line 8 is commented out
I take it, therefore, that you didn't comment out the line yourself
sometime in the past?
How did you install gscan2pdf?
ls -l /usr/lib/x86_64-linux-gnu/libsane.so.1
lrwxrwxrwx 1 root root 17 Sep 17 2020
/us
On 13/11/2023 16:24, Soumyanath Chatterjee wrote:
DB<1> use Image::Sane ':all';
Can't load
'/usr/lib/x86_64-linux-gnu/perl5/5.30/auto/Image/Sane/Sane.so' for
module Image::Sane: /usr/lib/x86_64-linux-gnu/libsane.so.1: undefined
symbol: l
ibusb_set_option at /usr/share/perl/5.30/XSLoader.pm
Please start an interactive Perl session with:
perl -d -e 1
Then execute the following:
use Image::Sane ':all';
print SANE_NAME_PAGE_HEIGHT, "\n";
and report the response.
Afterwards, you can quit with q
OpenPGP_signature.asc
Description: OpenPGP digital signature
Please start gscan2pdf from the command line with the --log option:
gscan2pdf --log=log
then quit, and post the log file, which gscan2pdf should have compressed
with xz.
OpenPGP_signature.asc
Description: OpenPGP digital signature
How are you starting gscan2pdf?
What does the following return?
apt list libimage-sane-perl
Regards
Jeff
OpenPGP_signature.asc
Description: OpenPGP digital signature
On 4/15/23 11:11 PM, Martin-Éric Racine wrote:
[...]
Noted.
In principle, I have version 10 ready to upload. However, given the
Bookworm freeze, the best I could do is push it to experimental.
Thanks for your time and efforts on this.
I did not realize that Bookworm's development cycle had p
Package: dhcpcd
Version: 9.4.1-21
Severity: important
Tags: newcomer upstream
X-Debbugs-Cc: debian-b...@allycomm.com
Dear Maintainer,
TL;DR -- Apparently fixed upstream in dhcpcd-9.5.0 or later (-10.0.0 available)
* What led up to the situation?
Installed later version of nftables from "test
severity 1030982 normal
thanks
Reducing the severity down to normal until the problem can be reproduced
and debugged.
On 11/02/2023 15:50, Janusz S. Bień wrote:
The failure log was
[log1 (application/octet-stream, attachment)]
That file ends with:
DEBUG - signal 'started-process' emitted with message: Scanning page 1 of 1
INFO - gscan2pdf: scanning image of size 1275x1784 pixels at 24 bits/pixel
INFO - gscan2
I still don't understand. The log you provided covered a successful
scan, with a couple of post-processing steps.
Please provide a log where the scan job failed.
OpenPGP_signature
Description: OpenPGP digital signature
In the log you provide, you seem to have a successful scan. Is the
problem therefore only the warning message?
If the other device does not work, please provide a log file created
when scanning with the other device.
OpenPGP_signature
Description: OpenPGP digital signature
There's no segfault there.
Please start gscan2pdf from the command line with the --log=log
option, if necessary, hit OK to select the crashed session, reproduce
the problem (i.e. the segfaul), quit, and post the log file, which
gscan2pdf may have compressed with xz.
OpenPGP_signature
Descript
Please start gscan2pdf from the command line with the --log=log option,
reproduce the problem, quit, and post the log file, which gscan2pdf may
have compressed with xz.
OpenPGP_signature
Description: OpenPGP digital signature
On Tue, Jan 24, 2023 at 02:32:07PM +0100, Santiago Ruano Rincón wrote:
> > Tests yesterday seem to indicate successful results, but again I've only
> > tested a few combinations in a VM (to keep the feedback loop short).
> >
> > From the installer team point of view, I'd welcome a swift upload wi
nks everybody for the inputs. I've applied Paul's solution, and the
> generated .deb can be downloaded from here:
>
> https://salsa.debian.org/debian/ifupdown/-/jobs/3841392/artifacts/raw/debian/output/ifupdown_0.8.41~1.gbp3a6fae+salsaci+20230123+42_amd64.deb
>
> Would it be
On Sat, Oct 29, 2022 at 10:33:26AM +, Oleg A. Arkhangelsky wrote:
> Since the unit type is oneshot, we can have multiple ExecStart statements.
>
> Note that we have to use '--ignore-errors'. Otherwise if we have real
> hotplug interface that is not present at the moment of restart, `ifup`
> r
The patch resolves the issue with no other apparent side effects.
This is my primary daily-use desktop system.
Package: Akregator
Version: 4:20.08.3-1
As of 11.6, Stable continues to include Akregator 4:20.08.3-1, which
includes this bug:
https://bugs.kde.org/show_bug.cgi?id=429444
https://invent.kde.org/pim/akregator/-/commit/546db72108cba99a1881e97349ce55db5d1da88e
Testing includes 4:22.08.3-1 and pres
Indeed. I've just build a deb for 4.13 and the problem is solved.
Would you mind uploading 4.13?
OpenPGP_signature
Description: OpenPGP digital signature
It looks like this has been fixed in 4.13:
https://lists.gnucash.org/pipermail/gnucash-user/2022-December/104391.html
OpenPGP_signature
Description: OpenPGP digital signature
On 19/12/2022 13:59, martin f krafft wrote:
Regarding the following, written by "Jeff" on 2022-12-19 at 09:26 Uhr +:
Yup. This patch fixes things:
I just tried with the patch applied, and I still get
[image2 @ 0x5609ccef9e40] The specified filename
'/home/s
On 17/12/2022 10:00, martin f krafft wrote:
Regarding the following, written by "Jeff" on 2022-12-16 at 16:44 Uhr +:
I think that this is this bug in unpaper:
https://github.com/unpaper/unpaper/issues/113
<https://github.com/unpaper/unpaper/issues/113>
Oka
Thanks for the report.
On 16/12/2022 11:05, martin f krafft wrote:
for every page processed by unpaper, I get two errors:
1. [image2 @ 0x558772ceee40] The specified filename
'/home/ssd/madduck/.tmp/gscan2pdf-SMFz/OHSkXwKy5v.pnm' does not
contain an image sequence pattern or a pattern i
reassign 1023659 unpaper 7.0.0-0.1
thanks
OpenPGP_signature
Description: OpenPGP digital signature
On 08/11/2022 15:06, Francesco Potortì wrote:
If I enable the "Postprocessing / Clean up images" option with default values,
I get errors from unpaper. Here they are:
[image2 @ 0x564ee7da3540] Encoder did not produce proper pts, making some up.
[image2 @ 0x564ee7da3540] The specified filename
gscan2pdf doesn't depend on autopkgtest directly. It has:
Testsuite: autopkgtest-pkg-perl
in the control file. Is that somehow incorrect?
OpenPGP_signature
Description: OpenPGP digital signature
Package: python3.10
Severity: normal
X-Debbugs-Cc: jep...@gmail.com
Dear Maintainer,
Hi!
Apologies to bringing this to your attention as a bystander, but I've become
aware
of an incompatibility between setuptools >= 60.0.0 and debian's python package.
I'm not actually using an affected version
ackages in stable are, well, stable, and I made no
changes to those parts of gscan2pdf, I wonder what happened in the rest
of the environment between stable and testing. I'd be interested to
confirm this by pushing the stable version of gscan2pdf through testing
s390x a couple of times.
se the timeouts when they happen.
Regards
Jeff
OpenPGP_signature
Description: OpenPGP digital signature
hosts diff from the buildd ones?
Thanks for your help.
Regards
Jeff
OpenPGP_signature
Description: OpenPGP digital signature
Thanks for the report.
This has been fixed upstream (but not yet in a release):
https://sourceforge.net/p/gscan2pdf/bugs/404/
https://sourceforge.net/p/gscan2pdf/code/ci/608c52b8f1ccb31c8572c8c5b62ae31f67196092/
I'll get a new release out ASAP.
Regards
Jeff
OpenPGP_signature
Descri
as these really shouldn't have
anything to do with gscan2pdf - maybe a dependency, e.g. gtk+.
But these also occur in runs which pass, such as:
https://ci.debian.net/data/autopkgtest/stable/amd64/g/gscan2pdf/23364484/log.gz
I'd be grateful for any suggestions
Regards
Jeff
Open
klinuxcnc, it doesn't use OpenGL and probably also doesn't use
Img. However, it's much less friendly (IMO)
Jeff
Control: tags unblock -1 by 1007752
Control: notforwarded -1
Control: tags block 1009448 by -1
OpenPGP_signature
Description: OpenPGP digital signature
Control: tags -1 - bookworm confirmed fixed-upstream ftbfs
thanks
OpenPGP_signature
Description: OpenPGP digital signature
In test 13, libpdf-builder-perl produces the attached PDF, which neither
Firefox nor Evince complains about, and prior to v9.56.0, ghostscript
accepted happily.
With v9.56.1:
$ gs -q -dNOPAUSE -dBATCH -sDEVICE=pnggray -g20x20 -dPDFFitPage
-dUseCropBox -sOutputFile=out.png out.pdf
Error: /typ
forwarded 1009448
https://github.com/PhilterPaper/Perl-PDF-Builder/issues/184
thanks
OpenPGP_signature
Description: OpenPGP digital signature
To confirm - I've just put the 3 packages for gs 9.56.1 (and nothing
else) from sid on my testing machine, and now I see the same failures.
OpenPGP_signature
Description: OpenPGP digital signature
My machine running testing currently has ghostscript 9.55.0, and there
it still builds fine. So I'm guessing the problem is between 9.55.0 and
9.56.0.
Indeed since the failure with 9.56.0, 9.56.1 has been uploaded.
I've just tried building it with 9.56.1 but it still has the same two
failures
Going through what changed between the previous successful build
https://buildd.debian.org/status/fetch.php?pkg=libpdf-builder-perl&arch=all&ver=3.023-1&stamp=1631870648&raw=0
and the failure:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libpdf-builder-perl.html
I see the
On 11/04/2022 15:35, martin f krafft wrote:
Then I think a better UI/UX for user-defined tools, and possibly the
ability to invoke any subset of them automatically during the scan would
do just fine.
I'm sure the UI/UX could be improved. I'd love to hear any suggestions.
If you look at the po
On 10/04/2022 20:36, martin f krafft wrote:
Regarding the following, written by "Jeff" on 2022-04-10 at 12:52 Uhr +:
Can't this be achieved with a user defined tool?
Sure thing, for instance:
|convert -size 2480x3508 -depth 300x300 -transparent white in.pdf out.pd
Can't this be achieved with a user defined tool?
OpenPGP_signature
Description: OpenPGP digital signature
On 31/03/2022 11:20, bwak...@gmail.com wrote:
gscan2pdf crashes after changing the date to to 1934-1-1 or 1934-01-01
just before saving to pdf
Date::Calc::Date_to_Time(): date out of range at
/usr/bin/site_perl/gscan2pdf line 2817
Good catch. Most file systems don't support file dates before 1
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.
Thank you for making such a great distribution!!! I have always used Debian. So
sorry for reporting the bug!
-- Package-specific info:
** Environment settings:
INTERFACE="gtk"
** /home/kmcguire/.reportbugrc:
reportbug_version "7.10.3+deb11u1"
mode novice
ui gtk
realname "j
Is there a specific sender address that it will suffice to whitelist, or
does the list need to permit mail from any address, regardless of
subscription status?
On Wed, 15 Dec 2021 21:08:28 +0100 Stephen Kitt wrote:
> Hi Jeff,
>
> On Tue, 14 Dec 2021 09:13:42 +0000, Jeff Blake wrote:
> [...]
> > Inspector and convertutf are the worst offenders in terms of being
> > unnecessary and complex. The disable/catapult.patch could al
On Tue, 7 Dec 2021 19:43:10 +0100 Tomas Pospisek wrote:
> On 06.12.21 20:43, Noah Meyerhans wrote:
> > On Sun, Dec 05, 2021 at 07:58:17PM +0300, Dmitry Alexandrov wrote:
> So what's happening with chromium in both sid and stable? I saw on
> d-release that it was removed from testing (#9
Thanks for the investigation and confirmation!
--
Jeff Squyres
jsquy...@cisco.com<mailto:jsquy...@cisco.com>
I haven't populated it with an actual
> graph so there's nothing to send with MPI_Alltoall.
>
>
--
Jeff Squyres
jsquy...@cisco.com
Can you provide a small reproducer of the issue?
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.
Thanks for the patch. Committed upstream. This isn't critical for
bullseye, so it won't hit unstable until after the release.
OpenPGP_signature
Description: OpenPGP digital signature
On 13/04/2021 15:29, Francesco Potortì wrote:
Ok, thanks. Should I send you the log you requested previously,
relative to compression?
Did the new version of PDF::Builder solve the problem?
Did selecting compression=Auto or compression=Flate solve the problem?
If so, then another log file wo
tags 985887 patch
thanks
I've cherry-picked enough of this patch to fix this from master at
https://github.com/PhilterPaper/Perl-PDF-Builder/commit/d03b59847ecfbf3c7c31b8c1901d3878dba08040#diff-44803d0b8089ee5eb36d750b5be96b6038d4f32687973371d4c67310afc81ae1
i.e. the author should be Phil Perr
On 27/03/2021 13:58, Francesco Potortì wrote:
That's because I have written my own compression script using
ghostscript and use it as post-processing tool (which I disabled when
sending the report). It seems to do a better job at compressing than
almost all tools out there. I have it at:
http:/
Thanks for the log file. You seem to have selected compression=none
(which resulted in a REALLY big PDF). Was that deliberate? Please try
compression=Auto.
This seems to be a bug in PDF::Builder (libpdf-builder-perl). I'll see
if I can work up a patch.
OpenPGP_signature
Description: OpenPG
Thanks for the report.
Please start gscan2pdf from the command line:
gscan2pdf --log=log
reproduce the problem, quit, and post the input image, log file and the
resulting PDF.
OpenPGP_signature
Description: OpenPGP digital signature
severity 983677 normal
tags 983677 moreinfo
thanks
On 05/03/2021 21:59, Rainer Dorsch wrote:
One thing which is special on my setup, maybe that triggers something on your
side, understanding in detail how gscan2pdf works: I let power management put
my PC to suspend, if I am away. I have the scan
I've been looking at this every day and am trouble reproducing this with
the test backend, or finding something I've changed recently that can
have caused this.
Do you know when this last worked?
Can you install some older releases (e.g. from the debian archive or
from sourceforge[1]) and giv
Discovered mdio_bcm_unimac module is missing from the installer
initrd. This will stop the installer on the RPI4 from connecting to
the network.
On Thu, Feb 18, 2021 at 9:06 AM Debian Bug Tracking System
wrote:
>
> Thank you for filing a new Bug report with Debian.
>
> You can follow progress on
Package: installation-reports
Boot method: netboot
Image version:
https://d-i.debian.org/daily-images/arm64/daily/netboot/debian-installer/arm64/linux
2021-02-18 02:07 26M
Date: 2021-02-18 14:05:00
Machine: RPi4
Processor:
Memory: 4GiB
Partitions:
Output of lspci -knn (or lspci -nn):
Base Sys
This was a netboot attempt.
Package: installation-reports
Boot method:
Image version:
https://d-i.debian.org/daily-images/arm64/daily/netboot/debian-installer/arm64/linux
2021-02-17 02:07
Date: 2021-02-17 19:14
Machine: RPI4
Processor:
Memory: 4G
Partitions:
Output of lspci -knn (or lspci -nn):
Base System Installation
reopen 980202
thanks
imagemagick 8:6.9.11.60+dfsg-1 does not include the bugfix that was
promised here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980202#41
OpenPGP_signature
Description: OpenPGP digital signature
This is more or less a duplicate of #980202
To unblock gscan2pdf, in case -60 didn't fix things, I uploaded
gscan2pdf-2.11.0-1 yesterday and replaced imagemagick with
graphicsmagick for the tests in question.
However, this doesn't solve the problem in imagemagick, which is
described in #9802
On 23/01/2021 17:53, Cristy wrote:
Thanks for the problem report. We can reproduce it and will have a patch
to fix it in the GIT main branch @
https://github.com/ImageMagick/ImageMagick6 later today. The patch will
be available in the beta releases of ImageMagick @
https://imagemagick.org/down
This seems to be a bug in imagemagick preventing imagemagick from
migrating from unstable to testing:
https://tracker.debian.org/pkg/imagemagick
https://ci.debian.net/packages/g/gscan2pdf/testing/amd64/
OpenPGP_signature
Description: OpenPGP digital signature
Thanks for the head up.
I note that it built fine in sid a month ago:
https://buildd.debian.org/status/fetch.php?pkg=gscan2pdf&arch=all&ver=2.10.2-1&stamp=1608242025&raw=0
but that it didn't a couple of days ago in reproducible-builds:
https://tests.reproducible-builds.org/debian/rb-pkg/unstab
ts:
* at present, the user should get some feedback that qpdfview cannot
create annotations in djvu
* a wishlist bug that the functionality be added.
Regards
Jeff
OpenPGP_signature
Description: OpenPGP digital signature
This seems to only affect djvu documents. With PDFs, it works as advertised.
OpenPGP_signature
Description: OpenPGP digital signature
On 17/12/2020 20:05, Marc Dequènes (duck) wrote:
That's a tad rude. I understand you're preparing the release but the
meaning of a bug is not up to discussion, problems in unstable, and even
in experimental have always been considered bugs. As the package was
almost unusable since my scans were
Thanks for the report.
The version of libtiff-tools in testing still outputs to stderr, so I am
inclined to say this is not (yet) a Debian bug, and certainly not important.
Indeed, your patch will break the version of gscan2pdf in testing.
Does the attached patch also fix your problem?
diff -
1 - 100 of 1560 matches
Mail list logo
