Package Details: tllocalmgr-git r84.bbd8488-2

Git Clone URL: (read-only, click to copy)
Package Base: tllocalmgr-git
Description: A shell and command-line utility to manage TeXLive on Arch Linux
Upstream URL:
Keywords: texlive
Licenses: GPL
Conflicts: texlive-localmanager, texlive-localmanager-git
Provides: texlive-localmanager=r84.bbd8488
Submitter: hv15
Maintainer: hv15
Last Packager: hv15
Votes: 11
Popularity: 0.41
First Submitted: 2020-02-02 21:08
Last Updated: 2021-06-30 18:04

Latest Comments

1 2 3 4 5 6 Next › Last »

schmui commented on 2021-06-30 15:05

Currenty, I get an error when building, it seems like the repo is missing?

fatal: repository '' not found

EDIT: Thanks, this seems to have been resolved!

greenbigfrog commented on 2021-05-25 13:14

error: failed to prepare transaction (could not satisfy dependencies)
:: installing texlive-core (2021.58710-2) breaks dependency 'texlive-core<2021' required by tllocalmgr-git

For anyone running into this, remember to just first update the AUR package. hv15 already updated it. I was too asleep too immediately realize what was going on...

hv15 commented on 2021-04-18 08:15

hi @TornaxO7, gensymb is part of the WAS package which is included in texlive-latexextra package. The error message is interesting, I'll have a look at this later.

TornaxO7 commented on 2021-04-17 20:11

If I'm executing install gensymb I'm getting the following error essage: Can't call method "revision" on an undefined value at /usr/bin/tllocalmgr line 421.

hv15 commented on 2021-03-27 13:19

Hi @d0lphin, it looks like something has gone wrong upstream, the URL (one of them, as its CDN'd) looks to point to an nearly empty archive: I suggest you contact the DVISVGM devs to look into this.

In the meantime, you can download the archive from, and modify the PKGBUILD at ~/.texlive/texmf-var/arch/builds/dvisvgm to use this archive instead. I suspect that the layout of the archive isn't the same as the tlnet one, you might have to tweak the PKGBUILD somewhat.


scrouthtv commented on 2021-03-27 12:11

Trying to install dvisvgm only gives me an empty package:


That is because dvisvgm installs into usr/bin/dvisvgm and /usr/share/man/man.1/dvisvgm.1.gz.

Is there any way to fix this easily? Thanks in advance.

hv15 commented on 2020-12-02 16:23

@abrac, I've pushed a new revision with a tentative solution to your problem. Basically, the texlive-tlpdb package is missing the 'pkgs' file which tllocalmgr uses to figure out the version of installed CTAN packages through pacman/AUR. If this file is missing, well tllocalmgr dies, but there isn't a very good reason for this. The main danger is that you might try to install some CTAN package which is already installed on the system. Pacman should detect this via an integrity check and cause the install to fail. Given this, I've changed the fatal error into a logged error. HTH

abrac commented on 2020-12-02 13:43

For some reason, when I install texlive-tlpdb, I am no longer able to use tllocalmgr. I get the following error:

$ tllocalmgr
Initializing ...
Cannot open /var/lib/texmf/arch/installedpkgs/texlive-tlpdb_2019-2.pkgs

hv15 commented on 2020-11-06 14:15

@cvelteren, as I said in the answers to @phenethylamin and @h30x, the issue is NOT with tllocalmgr. Packages like microtype.sty are grouped into the distribution packages, they are not installable through tllocalmgr.

Regarding texlive-core re-install, it is possible that the filename database of texlive is not being updated? Maybe it has become corrupt. Is microtype the only package which cannot be found on your system?

The version error seems to be related to git describe not being able to find any tags... do you (or @BigfootLives) have any git configs setup that would cause repos to be cloned shallowly. Doing so would omit any tag information. I am unable to reporduce this on my system, but I vaguely remember having experienced this on a CI system where the repo was being cloned shallowly.

cvelteren commented on 2020-11-06 13:47

@hv15 I have installed (and reinstalled) texlive-core, for some reason it didn't find it. Manual installation ended up fixing it, just here to highlight that it wouldn't work through this package. In addition the package version seems to be missing.