From: Rowaaaaan <Rowaaaaan@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] tlmgr is broken because Perl can't find TLConfig.pl
Date: Wed, 05 Jul 2023 00:32:31 +0200 [thread overview]
Message-ID: <20230704223231.EDb67tK9KGFSNDgZdevbHXvYmIc2UDyM2NX3k2IW8mE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40830@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1252 bytes --]
Closed issue by Rowaaaaan on void-packages repository
https://github.com/void-linux/void-packages/issues/40830
Description:
### Is this a new report?
Yes
### System Info
Void 6.0.9_1 x86_64 GenuineIntel uptodate rrrmFFFFFF
### Package(s) Affected
texlive-20210325_4
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
_No response_
### Expected behaviour
`tlmgr` in general should be working. For instance, `tlmgr update --all` should update the packages in my local repository.
### Actual behaviour
Doing any kind of action with `tlmgr` will output the following:
```
Can't locate TeXLive/TLConfig.pm in @INC (you may need to install the TeXLive::TLConfig module)
(@INC contains:
/texmf-dist/scripts/texlive/TeXLive/TLConfig.pm /texmf-dist/scripts/texlive /tlpkg
/usr/lib/perl5/site_perl /usr/share/perl5/site_perl /usr/lib/perl5/vendor_perl /usr/share/perl5/vendor_perl
/usr/lib/perl5/core_perl /usr/share/perl5/core_perl) at /usr/share/texmf-dist/scripts/texlive/tlmgr.pl line 61.
BEGIN failed--compilation aborted at /usr/share/texmf-dist/scripts/texlive/tlmgr.pl line 61.
```
### Steps to reproduce
1. Enter `tlmgr` --it doesn't matter what action you use.
2. Get the error.
prev parent reply other threads:[~2023-07-04 22:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-29 9:55 [ISSUE] " Rowaaaaan
2022-11-29 10:08 ` Rowaaaaan
2022-11-29 13:37 ` nsajko
2022-11-29 13:48 ` classabbyamp
2022-12-14 15:45 ` tornaria
2023-07-04 22:32 ` Rowaaaaan [this message]
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=20230704223231.EDb67tK9KGFSNDgZdevbHXvYmIc2UDyM2NX3k2IW8mE@z \
--to=rowaaaaan@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).