Github messages for voidlinux
 help / color / mirror / Atom feed
From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: today's update breaks fonts in texlive
Date: Thu, 21 Jan 2021 04:10:08 +0100	[thread overview]
Message-ID: <20210121031008.v3gVTqFZCcG-CUpATjhUXLjhWR4gIpe5GXcYxO7R4Ac@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: 718 bytes --]

New comment by ahesford on void-packages repository

https://github.com/void-linux/void-packages/issues/28051#issuecomment-764203443

Comment:
I doubt the `aleph` error is related to this issue and I agree that it's harmless, but it is new with these texlive updates.

- Ouput from `fmtutil-sys` run as in the XBPS trigger, but without `--quiet`: [fmtutil-sys.log](https://github.com/void-linux/void-packages/files/5846587/fmtutil-sys.log)
- Output of the failed `aleph` run mentioend in `fmtutil-sys` output: [lamed.log](https://github.com/void-linux/void-packages/files/5846588/lamed.log)
- List of installed TeXLive packages: [tlpkgs.txt](https://github.com/void-linux/void-packages/files/5846589/tlpkgs.txt)


  parent reply	other threads:[~2021-01-21  3:10 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
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 [this message]
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=20210121031008.v3gVTqFZCcG-CUpATjhUXLjhWR4gIpe5GXcYxO7R4Ac@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).