From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: today's update breaks fonts in texlive
Date: Wed, 20 Jan 2021 19:28:00 +0100 [thread overview]
Message-ID: <20210120182800.gdzn-Yq3h7GqL-mU6br1biMA3TGcKl0EjZ-2Sfg5AFM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28051@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1512 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/issues/28051#issuecomment-763844526
Comment:
During the upgrade, the following error was printed for each `texlive-*` package that was configured:
```
fmtutil [ERROR]: running `aleph -ini -jobname=lamed -progname=lamed *lambda.ini </dev/null' return status: 1
```
Downgrading `texlive-core` to `2020.55416_2` (and the `texlive-most` meta) instead prints
```
fmtutil [ERROR]: running `pdftex -ini -jobname=pdflatex-dev -progname=pdflatex-dev -translate-file=cp227.tcx *pdflatex.ini </dev/null' return status: 1
fmtutil [ERROR]: returning error due to option --strict
fmtutil [ERROR]: running `xetex -ini -jobname=xelatex-dev -progname=xelatex-dev -etex xelatex.ini </dev/null' return status: 1
fmtutil [ERROR]: returning error due to option --strict
fmtutil [ERROR]: running `luahbtex -ini -jobname=lualatex-dev -progname=lualatex-dev lualatex.ini </dev/null' return status: 1
fmtutil [ERROR]: returning error due to option --strict
fmtutil [ERROR]: running `luatex -ini -jobname=dvilualatex-dev -progname=dvilualatex-dev dvilualatex.ini </dev/null' return status: 1
fmtutil [ERROR]: returning error due to option --strict
fmtutil [ERROR]: running `pdftex -ini -jobname=latex-dev -progname=latex-dev -translate-file=cp227.tcx *latex.ini </dev/null' return status: 1
fmtutil [ERROR]: returning error due to option --strict
```
but allows me to compile the aforementioned document again.
next prev parent reply other threads:[~2021-01-20 18:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 9:02 [ISSUE] " dkwo
2021-01-20 13:13 ` ericonr
2021-01-20 18:00 ` ifreund
2021-01-20 18:01 ` ahesford
2021-01-20 18:28 ` ahesford [this message]
2021-01-20 22:53 ` fosslinux
2021-01-20 23:25 ` fosslinux
2021-01-21 0:28 ` q66
2021-01-21 0:47 ` ahesford
2021-01-21 0:49 ` fosslinux
2021-01-21 0:51 ` fosslinux
2021-01-21 3:10 ` ahesford
2021-01-21 14:10 ` ahesford
2021-01-21 14:10 ` [ISSUE] [CLOSED] " ahesford
2023-05-30 11:09 ` Begasus
2023-05-30 11:19 ` ahesford
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=20210120182800.gdzn-Yq3h7GqL-mU6br1biMA3TGcKl0EjZ-2Sfg5AFM@z \
--to=ahesford@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).