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

Bug#1054218: marked as done (texlive-latex-base: pdflatex failures on big-endian architectures (s390x))

Your message dated Thu, 09 Nov 2023 22:05:55 +0000
with message-id <E1r1D9v-00ApEm-KI@fasolo.debian.org>
and subject line Bug#1054218: fixed in texlive-bin 2023.20230311.66589-7
has caused the Debian Bug report #1054218,
regarding texlive-latex-base: pdflatex failures on big-endian architectures (s390x)
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.)


-- 
1054218: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054218
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: texlive-latex-base
Version: 2023.20231007-1
Severity: normal
X-Debbugs-Cc: stuart@debian.org

Dear Maintainer,

The unittests of the 'plastex' package run pdflatex to generate some
figures, and then extract the text from the figures to verify that
various implementation details of the package are working. These tests
pass on all release architectures except s390x. They also fail on ppc64.
The common feature of the failures is that the architecture is
big-endian.

The failures are all similar to:

  AssertionError: 'hi' != '\x00\x00'

i.e. the text that is found in the PDF (either by gs or pdftotext) is
the same number of bytes as the original text, but is all \0. The
extraction is platform-independent — the attached s390x.pdf yields \0\0
for its text no matter what arch pdftotext or gs is run on.

The PDFs all _look_ OK in any PDF viewer, it's just the text extraction
that fails.

If the pdf is generated via latex followed by dvipdf then the extracted
text is correct (up to whitespace); if the pdf is generated by lualatex
then he extracted text is correct.

It seems that pdflatex is mishandling embedding the text on big endian
systems. Speculating wildly... it looks a bit like pdflatex is taking
the wrong byte out of a multibyte character representation, and ending
up with \0 rather than the byte of interest, but I don't know how
pdflatex is representing the characters internally or how it is encoding
them into the PDF.

While I don't expect that there are many direct users of pdflatex on s390x,
testing migration within Debian now requires successful completion of
unittests on s390x, and so arch-specific bugs on s390x become relevant.

Attached:
  test.tex (one of the little .tex files plastex generates in its tests)
  amd64.pdf (output of "pdflatex test.tex" on amd64)
  s390x.pdf (output of "pdflatex test.tex" on s390x)

(access to s390x and ppc64 courtesy of Debian's porter boxes
zelenka.debian.org and perotto.debian.net)

regards
Stuart

Attachment: amd64.pdf
Description: Adobe PDF document

Attachment: s390x.pdf
Description: Adobe PDF document

\nonstopmode\AtBeginDocument{\thispagestyle{empty}}\documentclass{article}\usepackage{microtype}\DisableLigatures{encoding = *, family = *}\begin{document}\newif\iffoo\footrue\iffoo hi\else bye\fi\end{document}

--- End Message ---
--- Begin Message --- 
Source: texlive-bin
Source-Version: 2023.20230311.66589-7
Done: Hilmar Preusse <hille42@web.de>

We believe that the bug you reported is fixed in the latest version of
texlive-bin, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1054218@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Hilmar Preusse <hille42@web.de> (supplier of updated texlive-bin package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Thu, 09 Nov 2023 21:39:01 +0000
Source: texlive-bin
Architecture: source
Version: 2023.20230311.66589-7
Distribution: unstable
Urgency: medium
Maintainer: Debian TeX Task Force <debian-tex-maint@lists.debian.org>
Changed-By: Hilmar Preusse <hille42@web.de>
Closes: 1054218
Changes:
 texlive-bin (2023.20230311.66589-7) unstable; urgency=medium
 .
   * Add patch to fix pdflatex's ToUnicode map on Big Endian
     (Closes: #1054218).
   * Suggest texlive-binaries-sse2 only on arches, where it is
     available.
   * Add "hintview" to list of suggested package of texlive-binaries.
   * Extend the list of arches, where luajit binaries are available: arm64.
   * Extend gbp.conf: "gbp pull" should update pristine-tar branch too.
Checksums-Sha1:
 fc62d20cbea1d0747883f9dd1dc08de1d40c3542 3493 texlive-bin_2023.20230311.66589-7.dsc
 c7b99ea59ecd94c5ca8c1e438108a43bed4eb6cf 151356 texlive-bin_2023.20230311.66589-7.debian.tar.xz
 eb74d85a62c74411a3290d3e1fa9ad77920d90de 6024 texlive-bin_2023.20230311.66589-7_source.buildinfo
Checksums-Sha256:
 3f1f5b1284b2900b33b1b3adac1b20b93e2590e731711a9f1ede5e62c7f66899 3493 texlive-bin_2023.20230311.66589-7.dsc
 5089fdc044d78a35caa536b26a7c237c9f7df7d5107acf5ba1862f31598e6ef6 151356 texlive-bin_2023.20230311.66589-7.debian.tar.xz
 2065f81d9d064eb5a6452616827376e134e939233b51a0a231f1c3a47204f7ed 6024 texlive-bin_2023.20230311.66589-7_source.buildinfo
Files:
 f8fa5f9e6322abad7ec111ad517188c8 3493 tex optional texlive-bin_2023.20230311.66589-7.dsc
 2b89a4885577bb0a3ee9652df33c5be3 151356 tex optional texlive-bin_2023.20230311.66589-7.debian.tar.xz
 75b6e6dcfaf1fc73d74276a3e1ed5911 6024 tex optional texlive-bin_2023.20230311.66589-7_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQKTBAEBCgB9FiEEaXGmC/nkbIhxf16kxiZYRqvgLIsFAmVNU+NfFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDY5
NzFBNjBCRjlFNDZDODg3MTdGNUVBNEM2MjY1ODQ2QUJFMDJDOEIACgkQxiZYRqvg
LIv9Cw/+IAQGg+IDRwHcZw8hPPRWX0MaS9LkpoPyvyUOUnD/o95oDl/DSOQGUkdo
DCeFBuuiCfu1wR8MKQfd0d3znVzabqhUr1CJHCgarelW/0URDAm9yeM4684nPS2F
7uxIEDW+6TsZ6z5tCcE4jUDCY8Uec79kdrMLYH6iQTHNTT1Eiugpuw5ETykCOSCi
mdnYm+nFuN/4Cq0iyt3qzpGXi+aEs6mgzkssG3VCBtHGkhMu1XeXg0cjkeztC6nJ
YoWqILyFY9zXgrty4cOCVApTF+ZzE5hfpUjNkKwiJIsEJcmLX6YEG1mO+tgNVTiE
qk/rWE4yH1MGJIv+CV9o4G5AotAxDuAQafim0C1auK7rkXzmLmS4NrJ4KeY42nDo
hlo5zox2gVIL1FyrcIjGCjDQKeWN5Vj0EabT9Vjrxrnhk34iAzqe8KA+ANi0P0Qz
4dTNyQNalzHjvj3Jqz2KtUfrarYEyVb/Le1dPgewMPROrSfCT59Ox3a+hy5v+Zdd
5N8GMBqBxCWM5sg+RKYV7XisOvRTXyHQ3nchwqzjTauKUEkZlkbkDNv60bCHIsDD
TqGF+48XrSGmsviT/twbcYgQAJo5HpKqjooEs0J87HT4sGZGrfnN9JDxFn86+6+B
v0j0vOEd8VyROfr/eWYvxC7+nxuZySkPhM4x9WXNfQI4MqgWUKw=
=T2DW
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: