Github messages for voidlinux
 help / color / mirror / Atom feed
From: morrismuehl <morrismuehl@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: zlib-1.3 upgrade breaks lualatex
Date: Fri, 15 Sep 2023 16:19:48 +0200	[thread overview]
Message-ID: <20230915141948.B5xjGRp4RlVwnXsNQ143Duxn09dZclkOCxnomwVzdlA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45986@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1586 bytes --]

New comment by morrismuehl on void-packages repository

https://github.com/void-linux/void-packages/issues/45986#issuecomment-1721362364

Comment:
I can confirm this bug. Compilation with XeLateX also fails when incorporating eps files (xdvipdfmx spits out an error): 

**System Info** 

Void Linux 6.3.13_1 x86_64-glibc

````
 This is XeTeX, Version 3.141592653-2.6-0.999993 (TeX Live 2021/VoidLinux) (preloaded format=xelatex)
 restricted \write18 enabled.
entering extended mode
(./mwe.tex
LaTeX2e <2020-10-01> patch level 4
L3 programming layer <2021-02-18>
(/usr/share/texmf-dist/tex/latex/base/article.cls
Document Class: article 2020/04/10 v1.4m Standard LaTeX document class
(/usr/share/texmf-dist/tex/latex/base/size10.clo))
(/usr/share/texmf-dist/tex/latex/graphics/graphicx.sty
(/usr/share/texmf-dist/tex/latex/graphics/keyval.sty)
(/usr/share/texmf-dist/tex/latex/graphics/graphics.sty
(/usr/share/texmf-dist/tex/latex/graphics/trig.sty)
(/usr/share/texmf-dist/tex/latex/graphics-cfg/graphics.cfg)
(/usr/share/texmf-dist/tex/latex/graphics-def/xetex.def)))
(/usr/share/texmf-dist/tex/latex/l3backend/l3backend-xetex.def
(|extractbb --version)) (./mwe.aux)
(/usr/share/texmf-dist/tex/latex/base/ts1cmr.fd) [1] (./mwe.aux)PANIC: unprotected error in call to Lua API (zlib library version does not match - header: 1.2.13, library: 1.3)

xdvipdfmx:fatal: Image inclusion failed for "mwe.eps".

No output PDF file written.
 )
Error 256 (driver return code) generating output;
file mwe.pdf may not be valid.
Transcript written on mwe.log. 
``````

  parent reply	other threads:[~2023-09-15 14:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-09  4:21 [ISSUE] " tuxliban
2023-09-12 10:33 ` heuer
2023-09-12 11:05 ` heuer
2023-09-15 14:19 ` morrismuehl [this message]
2023-09-18 19:04 ` mhmdanas
2023-09-19  5:43 ` tuxliban
2023-09-19 22:06 ` [ISSUE] [CLOSED] " Piraty

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230915141948.B5xjGRp4RlVwnXsNQ143Duxn09dZclkOCxnomwVzdlA@z \
    --to=morrismuehl@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).