<div dir="ltr"><div dir="ltr">Hi Norbert,</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Nov 15, 2019 at 4:41 AM Norbert Preining <<a href="mailto:preining@logic.at">preining@logic.at</a>> wrote:</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
The binaries are in /usr/bin, I suppose?<br></blockquote><div><br></div><div>correct (though <a href="http://tlmgr.pl">tlmgr.pl</a> appears to be in /usr/share/texmf-dist/scripts/texlive/)</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Thus the binaries are in /[$HOME]/tex-local/texlive/2017/bin/[ARCH]/<br></blockquote><div><br></div><div>also correct.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
> a separate install, and I use this tlmgr to update this install *only*. I<br>
> am uncertain why, but this local install uses root permissions, but only<br>
<br>
What does that mean, uses root permissions? What are the permissions of<br>
the files?<br>
ls -l /[$HOME]/tex-local/texlive/2017/bin/[ARCH]/tlmgr<br></blockquote><div><br></div><div> $ ls -l [$HOME]/tex-local/texlive/2017/bin/x86_64-linux/tlmgr<br>lrwxrwxrwx 1 root root 41 25. Nov 2016 [$HOME]/tex-local/texlive/2017/bin/x86_64-linux/tlmgr -> ../../texmf-dist/scripts/texlive/<a href="http://tlmgr.pl">tlmgr.pl</a></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
<br>
Well, then the gentoo packages are broken, right? I guess they are 2018<br>
or 2019, right?<br></blockquote><div><br></div><div>the installed ones are 2017. I'm trying to update to 2019, and this is what's failing.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
They use the correct /usr/bin binaries, but the calls to fmtutil<br>
don't work, because fmtutil needs <a href="http://mktexlsr.pl" rel="noreferrer" target="_blank">mktexlsr.pl</a>, and gentoo seems having<br>
failed to install that one.<br></blockquote><div><br></div><div>/usr/share/texmf-dist/scripts/texlive/<a href="http://mktexlsr.pl">mktexlsr.pl</a> was installed by the texlive-basic-2019 gentoo package. So It's there.</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Looking at <a href="https://forums.gentoo.org/viewtopic-t-1098680-start-0.html" rel="noreferrer" target="_blank">https://forums.gentoo.org/viewtopic-t-1098680-start-0.html</a><br>
I see this is a common issue, and that means that either the gentoo<br>
packages are broken (what I assume), or there is a misconfiguration.<br>
<br>
Can you show me the content of<br>
/etc/texmf/texmf.d/05searchpaths.cnf<br></blockquote><div>[big code block incoming]</div><div>------------------------------------------------------------------</div><div>[following the preamble]:</div><div>TEXMFROOT = $SELFAUTODIR/share<br><br>% The main tree of distributed packages and programs:<br>TEXMFDIST = $TEXMFROOT/texmf-dist<br><br>% We used to have a separate /texmf tree with some core programs and files.<br>% Keep the variable name.<br>TEXMFMAIN = $TEXMFDIST<br><br>% The Gentoo site tree<br>TEXMFSITE = $TEXMFROOT/texmf-site<br><br>% Local additions to the distribution trees.<br>TEXMFLOCAL = $TEXMFROOT/../local/share/texmf<br><br>% TEXMFSYSVAR, where *-sys store cached runtime data.<br>TEXMFSYSVAR = $SELFAUTOPARENT/var/lib/texmf<br></div><div>% TEXMFSYSCONFIG, where *-sys store configuration data.<br>TEXMFSYSCONFIG = $SELFAUTOPARENT/etc/texmf<br><br>% Per-user texmf tree(s) -- organized per the TDS, as usual. To define<br>% more than one per-user tree, set this to a list of directories in<br>% braces, as described above. (This used to be HOMETEXMF.) ~ expands<br>% to %USERPROFILE% on Windows, $HOME otherwise.<br>TEXMFHOME = ~/texmf<br><br>% TEXMFVAR, where texconfig/updmap/fmtutil store cached runtime data.<br>TEXMFVAR = ~/.texlive/texmf-var<br><br>% TEXMFCONFIG, where texconfig/updmap/fmtutil store configuration data.<br>TEXMFCONFIG = ~/.texlive/texmf-config<br><br>% This is the value manipulated by tlmgr's auxtrees subcommand in the<br>% root texmf.cnf. Kpathsea warns about a literally empty string for a<br>% value, hence the empty braces.<br>TEXMFAUXTREES = {}<br><br>% List all the texmf trees. For an explanation of what they are, see the<br>% TeX Live manual.<br>%<br>% For texconfig to work properly, TEXMFCONFIG and TEXMFVAR should be named<br>% explicitly and before other trees.<br>%<br></div><div> TEXMFLOCAL precedes TEXMFDIST because locally-installed versions<br>% should take precedence over distribution files -- although it is<br>% generally a source of confusion to have different versions of a<br>% package installed, whatever the trees, so try to avoid it.<br>%<br>% The odd-looking $TEXMFAUXTREES$TEXMF... construct is so that if no auxtree is<br>% ever defined (the 99% common case), no extra elements will be added to<br>% the search paths. tlmgr takes care to end any value with a trailing comma.<br>TEXMF = {$TEXMFAUXTREES$TEXMFCONFIG,$TEXMFVAR,$TEXMFHOME,!!$TEXMFLOCAL,!!$TEXMFSYSCONFIG,!!$TEXMFSYSVAR,!!$TEXMFSITE,!!$TEXMFDI><br><br>% Where to look for ls-R files. There need not be an ls-R in the<br>% directories in this path, but if there is one, Kpathsea will use it.<br>% By default, this is only the !! elements of TEXMF, so that mktexlsr<br>% does not create ls-R files in the non-!! elements -- because if an<br>% ls-R is present, it will be used, and the disk will not be searched.<br>% This is arguably a bug in kpathsea.<br>TEXMFDBS = {!!$TEXMFLOCAL,!!$TEXMFSYSCONFIG,!!$TEXMFSYSVAR,!!$TEXMFSITE,!!$TEXMFDIST}<br><br>% The system trees. These are the trees that are shared by all users.<br>% If a tree appears in this list, the mktex* scripts will use<br>% VARTEXFONTS for generated files, if the original tree isn't writable;<br>% otherwise the current working directory is used.<br>SYSTEXMF = $TEXMFSYSVAR;$TEXMFLOCAL;$TEXMFSITE;$TEXMFDIST<br></div><div>% First writable tree here is used by Lua(La)TeX for the font cache.<br>% LuaLaTeX uses the value here, while ConTeXt uses the same variable but<br>% from texmfcnf.lua; therefore the two values should be kept in sync.<br>% (As should everything else in texmf.cnf <-> texmfcnf.lua.)<br>TEXMFCACHE = $TEXMFSYSVAR;$TEXMFVAR<br><br>% We use GLOBALVARTEXFONTS in order to always be able to search in the global<br>% font cache even if VARTEXFONTS is overridden.<br>GLOBALVARTEXFONTS = $SELFAUTOPARENT/var/cache/fonts<br><br>% Where generated fonts may be written. This tree is used when the sources<br>% were found in a system tree and either that tree wasn't writable, or the<br>% varfonts feature was enabled in MT_FEATURES in mktex.cnf.<br>VARTEXFONTS = $GLOBALVARTEXFONTS<br><br>% On some systems, there will be a system tree which contains all the font<br>% files that may be created as well as the formats. For example<br>% TEXMFVAR = /var/lib/texmf<br>% is used in many distros. In this case, set VARTEXFONTS like this<br>%VARTEXFONTS = $TEXMFVAR/fonts<br>% and do not mention it in TEXMFDBS (but _do_ mention TEXMFVAR).<br>%<br>% Remove $VARTEXFONTS from TEXMFDBS if the VARTEXFONTS directory is below<br>% one of the TEXMF directories (avoids overlapping ls-R files).<br></div><div>------------------------------------------------------------</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
and the output of<br>
/usr/bin/kpsewhich -var-value TEXMFROOT<br></blockquote><div><br></div><div>/</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
/usr/bin/kpsewhich -var-value TEXMFMAIN<br></blockquote><div><br></div><div>//texmf-dist/</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
/usr/bin/kpsewhich -var-value TEXMFDIST<br></blockquote><div><br></div><div>//texmf-dist</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
<br>
Furthermore, **HOW** do you try to update the gentoo packages, as root<br>
or using sudo?<br></blockquote><div><br></div><div>as root</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
In any case, send the value of $PATH for **root** when the update is<br>
started.<br></blockquote><div>/sbin:/bin:/usr/sbin:/usr/bin</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
To make this clear: You **MUST**NOT** have <br>
/[$HOME]/tex-local/texlive/2017/bin/[ARCH]/<br>
in the PATH of root!!!<br></blockquote><div><br></div><div>ordinarily I do not. I tried adding the local TL path, but that didn't help.</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
<br>
> > That is a Gentoo bug. They have not patched <a href="http://tlmgr.pl" rel="noreferrer" target="_blank">tlmgr.pl</a> so that it finds<br>
> > the correct modules.<br>
> ><br>
> <br>
> gentoo's devs keep telling me that this is an error with my own kpathsea<br>
> setup, and not with the packages. Further, they tell me to add the TUG TL<br>
<br>
That is wrong, at 99% ...<br>
<br>
> In short: I want to manage my user-directory TUG TL using its own tlmgr,<br>
> but use the system packages to update the system TL, and not have them<br>
> conflict, or interact in any way. How do I do this?<br>
<br>
- ensure the PATH for root is correct (depends on whether you use<br>
sudo, sudo -E, su, su -, ...)<br>
- ensure that the TEXMFROOT variable expands correctly.<br></blockquote><div><br></div><div>given that TEXMFROOT returns "/", is it safe to assume this variable is set incorrectly?</div><div><br></div><div>Thanks for the help!</div><div><br></div><div>A </div></div></div>