Re: pdflatex build error: Mismatched LaTeX support files detected

[Herbert Voss]

Am 19.06.23 um 22:16 schrieb Rich Shepard:

### 


fmtutil: Error! Not all formats have been built successfully.
Visit the log files in directory
  /usr/share/texmf-var/web2c
for details.
### 






Rich,

that looks like a mismatch between TeXLive from TUG 
(/usr/local/texlive/)

and from your  linux distribution (/usr/share/tex...)

what is the output of
which -a fmtutil-sys





This is a summary of all `failed' messages and warnings:
`pdfetex -ini  -jobname=amstex -progname=amstex 
-translate-file=cp227.tcx *amstex.ini' failed
`pdfetex -ini  -jobname=bamstex -progname=bamstex 
-translate-file=cp227.tcx bamstex.ini' failed


What do I read to learn how to properly build amstex and bamstex?


Running fmtutil-sys is in general done by the update manager of TeXLive and
only in specific cases by the user.

Herbert







In this case you get local format or system format files.


Different errors when run by user and root.

Thanks,

Rich


--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

texlive 2023 > WHAT DO I HAVE TO DO TO GET 2023 WORKING??

[Wolfgang Engelmann]

I checked with synaptic in my Debian 5.10179-1 (2023-05-12)
> 2020_20210202-3

and with
latex -v
> Tex Live 2022

and in /usr/local
is  /texlive/2022 and /texlive/2023

I have done in my ./profile according to (1-) the (2-)

1-
Post-install: setting PATH

After the installation finishes, you must add the directory of TeX Live 
binaries to your PATH—except on Windows, where the installer takes care 
of this. The installer shows the exact lines that should be added. As an 
example, for Bourne-compatible shells (e.g., in ~/.profile or ~/.bashrc):

  PATH=/usr/local/texlive/2023/bin/x86_64-linux:$PATH
Use the initialization file and syntax for your shell, your installation 
directory, and your binary platform name instead of x86_64-linux. After 
editing the init file, log out and log back in.


If you have multiple TeX installations on a given machine, you need to 
change the search path to switch between them—except on MacOSX.


2-
./profile
...
# if running bash
if [ -n "$BASH_VERSION" ]; then
# include .bashrc if it exists
if [ -f "$HOME/.bashrc" ]; then
. "$HOME/.bashrc"
fi
fi

# set PATH so it includes user's private bin if it exists
if [ -d "$HOME/bin" ] ; then
PATH="$HOME/bin:$PATH"
fi

#$HOME/.profile PATH
PATH=/usr/local/texlive/2023/bin/x86_64-linux:$PATH;export PATH
MANPATH=/usr/local/texlive/2023/texmf-dist/doc/man:$MANPATH;export MANPATH
INFOPATH=/usr/local/texlive/2023/texmf-dist/doc/info:$INFOPATH; export 
INFOPATH


WHAT DO I HAVE TO DO TO GET 2023 WORKING??
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: texlive 2023 > WHAT DO I HAVE TO DO TO GET 2023 WORKING??

[Wolfgang Engelmann]

Am 19.06.23 um 15:29 schrieb Herbert Voss:



Am 19.06.23 um 15:11 schrieb Wolfgang Engelmann:

do you have a file texlive.sh in /etc/profile.d/. ?
If yes, what's its contents.


export PATH=/usr/local/texlive/2022/bin/x86_64-linux:$PATH
export MANPATH=/usr/local/texlive/2022/texmf/doc/man:$MANPATH
export INFOPATH=/usr/local/texlive/2022/texmf/doc/info:$INFOPATH
unset TEXINPUTS
unset TEXMFCONFIG


as root change it to 2023






If no, what is the output of

which -a tex


/usr/local/texlive/2022/bin/x86_64-linux/tex
/usr/local/texlive/2022/bin/x86_64-linux/tex
/usr/bin/tex


it looks like an old instance from Debian's own texlive. Delete all files
depending to tex in /usr/bin/, e.g. tex, latex, luatex, ...


There A LOT of files in /usr/bin ..
I have sudo rm the tex latex lua
but what else should I remove?

So far after a restart
which -a tex
still gives 2022 >
/usr/local/texlive/2022/bin/x86_64-linux/tex
>> /usr/local/texlive/2022/bin/x86_64-linux/tex

Wolfgang


After a restart try

which -a latex

Is it now 2023?

Herbert

--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Display font shrunk

[Jean-Marc Lasgouttes]

Le 19/06/2023 à 17:42, Rich Shepard a écrit :

On Mon, 19 Jun 2023, Rich Shepard wrote:


I don't know what I did on the keyboard, but suddenly all my documents
display in about a 2pt font when I open them in LyX.


In Documents -> Settings -> Display -> Preferences the font settings 
haven't

changed; the point size is still 12.


Isn't this a zoom issue? What happens when you use Ctrl-plus ?

JMarc

--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: texlive 2023 > WHAT DO I HAVE TO DO TO GET 2023 WORKING??

[Wolfgang Engelmann]

Am 19.06.23 um 16:55 schrieb Tobias Hilbricht:

Am Montag, dem 19.06.2023 um 15:57 +0200 schrieb Wolfgang Engelmann:



Am 19.06.23 um 15:29 schrieb Herbert Voss:



Am 19.06.23 um 15:11 schrieb Wolfgang Engelmann:

do you have a file texlive.sh in /etc/profile.d/. ?
If yes, what's its contents.


export PATH=/usr/local/texlive/2022/bin/x86_64-linux:$PATH
export MANPATH=/usr/local/texlive/2022/texmf/doc/man:$MANPATH
export INFOPATH=/usr/local/texlive/2022/texmf/doc/info:$INFOPATH
unset TEXINPUTS
unset TEXMFCONFIG


as root change it to 2023


/usr/local/texlive/2022/bin/x86_64-linux/tex
/usr/local/texlive/2022/bin/x86_64-linux/tex
/usr/bin/tex


it looks like an old instance from Debian's own texlive. Delete all
files
depending to tex in /usr/bin/, e.g. tex, latex, luatex, ...


There A LOT of files in /usr/bin ..
I have sudo rm the tex latex lua
but what else should I remove?


Did you remove Debians "own" TeXLive install completely? Try to find
out if there are packages left from an old install with
apt list --installed | grep texlive
and then remove those packages.
Tobias


Tobias and Herbert,

thanks for the suggestions.
I am upgrading my Debian bullseye to bookworm.
Unfortunately it contains again texlive 2022 instaed of 2023.
It takes quite some time to finish the upgrade. If done, I will try to 
use the proposals for getting finally the desired 2023.


Wolfgang
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: texlive 2023 > WHAT DO I HAVE TO DO TO GET 2023 WORKING??

[Tobias Hilbricht]

Am Montag, dem 19.06.2023 um 15:57 +0200 schrieb Wolfgang Engelmann:
> 
> 
> Am 19.06.23 um 15:29 schrieb Herbert Voss:
> > 
> > 
> > Am 19.06.23 um 15:11 schrieb Wolfgang Engelmann:
> > > > do you have a file texlive.sh in /etc/profile.d/. ?
> > > > If yes, what's its contents.
> > > 
> > > export PATH=/usr/local/texlive/2022/bin/x86_64-linux:$PATH
> > > export MANPATH=/usr/local/texlive/2022/texmf/doc/man:$MANPATH
> > > export INFOPATH=/usr/local/texlive/2022/texmf/doc/info:$INFOPATH
> > > unset TEXINPUTS
> > > unset TEXMFCONFIG
> > 
> > as root change it to 2023
> > > 
> > > /usr/local/texlive/2022/bin/x86_64-linux/tex
> > > /usr/local/texlive/2022/bin/x86_64-linux/tex
> > > /usr/bin/tex
> > 
> > it looks like an old instance from Debian's own texlive. Delete all
> > files
> > depending to tex in /usr/bin/, e.g. tex, latex, luatex, ...
> 
> There A LOT of files in /usr/bin ..
> I have sudo rm the tex latex lua
> but what else should I remove?

Did you remove Debians "own" TeXLive install completely? Try to find
out if there are packages left from an old install with 
apt list --installed | grep texlive
and then remove those packages.
Tobias
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Display font shrunk

[Rich Shepard]

I don't know what I did on the keyboard, but suddenly all my documents
display in about a 2pt font when I open them in LyX.

How might I have unintentionally done this, and how do I fix it so I can
actually see what I'm writing?

TIA,

Rich
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Display font shrunk

[Rich Shepard]

On Mon, 19 Jun 2023, Rich Shepard wrote:


I don't know what I did on the keyboard, but suddenly all my documents
display in about a 2pt font when I open them in LyX.


In Documents -> Settings -> Display -> Preferences the font settings haven't
changed; the point size is still 12.

Rich
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: texlive 2023 > WHAT DO I HAVE TO DO TO GET 2023 WORKING??

[Wolfgang Engelmann]

Am 19.06.23 um 14:26 schrieb Herbert Voss:



Am 19.06.23 um 11:14 schrieb Wolfgang Engelmann:

I checked with synaptic in my Debian 5.10179-1 (2023-05-12)
> 2020_20210202-3

and with
latex -v
> Tex Live 2022

and in /usr/local
is  /texlive/2022 and /texlive/2023

I have done in my ./profile according to (1-) the (2-)



do you have a file texlive.sh in /etc/profile.d/. ?
If yes, what's its contents.


export PATH=/usr/local/texlive/2022/bin/x86_64-linux:$PATH
export MANPATH=/usr/local/texlive/2022/texmf/doc/man:$MANPATH
export INFOPATH=/usr/local/texlive/2022/texmf/doc/info:$INFOPATH
unset TEXINPUTS
unset TEXMFCONFIG



If no, what is the output of

which -a tex


/usr/local/texlive/2022/bin/x86_64-linux/tex
/usr/local/texlive/2022/bin/x86_64-linux/tex
/usr/bin/tex




Herbert



Thanks, Herbert.

I guess I have to change 2022 > 2023?

Wolfgang
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Time stamp is off

[R. H. van der Gaag]

> On 18 Jun 2023, at 20:24,   wrote:
> 
>> -Oorspronkelijk bericht-
>> Van: lyx-users  Namens R. H. van der Gaag
>> Verzonden: zondag 18 juni 2023 15:10
> ...
>> On 18 Jun 2023, at 15:01, Maria Gouskova  wrote:
>> 
>>> On Sun, Jun 18, 2023 at 7:22 AM R. H. van der Gaag
>>  wrote:
>>> Hi all,
>>> I noticed the time stamp on tracked changes is two hours off. Solutions 
>>> found
>> online seem to fail. Is there a way to get correct time stamps?
>>> 
>>> I cannot reproduce this here--my time stamps look correct. I am using LyX 
>>> 2.3.6
>> on Linux Mint 21, Cinnamon 5.4.12. (Btw, it helps when you include details 
>> of your
>> system and installation for questions like this).
>> 
>> Of course, sorry about that. This is on LyX 2.3.7, macOS 13.4, on an M1 
>> iMac. I am
>> in the Amsterdam timezone, and time stamps like \lyxadded{RH}{Sun Jun 18
>> 13:00:02 2023} are two hours behind. I worry about this a little bit: time
>> discrepancies can cause nasty synchronisation issues sometimes. This has not
>> happened so far, but since I am working on two machines, I have to be 
>> careful.
> 
> For me it also works correctly. I am in the same timezone (Amsterdam), and my 
> LyX date format is %c
> (Tools / Preferences / Output / General / Dateformat).
> Insert / Date gives Sun Jun 18 20:24:41 2023

Thanks for checking. Insert date gives the correct (Dutch) time here, too. But 
the time stamps added to the LaTeX preview are always exactly two hours behind. 
A riddle.

-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: texlive 2023 > WHAT DO I HAVE TO DO TO GET 2023 WORKING??

[Herbert Voss]

Am 19.06.23 um 11:14 schrieb Wolfgang Engelmann:

I checked with synaptic in my Debian 5.10179-1 (2023-05-12)
> 2020_20210202-3

and with
latex -v
> Tex Live 2022

and in /usr/local
is  /texlive/2022 and /texlive/2023

I have done in my ./profile according to (1-) the (2-)



do you have a file texlive.sh in /etc/profile.d/. ?
If yes, what's its contents.

If no, what is the output of

which -a tex

Herbert

--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: texlive 2023 > WHAT DO I HAVE TO DO TO GET 2023 WORKING??

[Tobias Hilbricht]

Am Montag, dem 19.06.2023 um 11:14 +0200 schrieb Wolfgang Engelmann:
> I checked with synaptic in my Debian 5.10179-1 (2023-05-12)
>  > 2020_20210202-3
> 
> and with
> latex -v
>  > Tex Live 2022
> 
> and in /usr/local
> is  /texlive/2022 and /texlive/2023
> 
> I have done in my ./profile according to (1-) the (2-)
> 
> 1-
> Post-install: setting PATH
> 
> After the installation finishes, you must add the directory of TeX
> Live 
> binaries to your PATH—except on Windows, where the installer takes
> care 
> of this. The installer shows the exact lines that should be added. As
> an 
> example, for Bourne-compatible shells (e.g., in ~/.profile or
> ~/.bashrc):
>    PATH=/usr/local/texlive/2023/bin/x86_64-linux:$PATH
> Use the initialization file and syntax for your shell, your
> installation 
> directory, and your binary platform name instead of x86_64-linux.
> After 
> editing the init file, log out and log back in.
> 
> If you have multiple TeX installations on a given machine, you need
> to 
> change the search path to switch between them—except on MacOSX.
> 
> 2-
> ./profile
> ...
> # if running bash
> if [ -n "$BASH_VERSION" ]; then
>  # include .bashrc if it exists
>  if [ -f "$HOME/.bashrc" ]; then
>  . "$HOME/.bashrc"
>  fi
> fi
> 
> # set PATH so it includes user's private bin if it exists
> if [ -d "$HOME/bin" ] ; then
>  PATH="$HOME/bin:$PATH"
> fi
> 
> #$HOME/.profile PATH
> PATH=/usr/local/texlive/2023/bin/x86_64-linux:$PATH;export PATH
> MANPATH=/usr/local/texlive/2023/texmf-dist/doc/man:$MANPATH;export
> MANPATH
> INFOPATH=/usr/local/texlive/2023/texmf-dist/doc/info:$INFOPATH;
> export 
> INFOPATH
> 
> WHAT DO I HAVE TO DO TO GET 2023 WORKING??

Hello Wolfgang,

I have installed TeXLive 2023 and preceeding versions according to
https://wiki.ubuntuusers.de/TeX_Live/#Manuell
and then to adapt $PATH according to
https://wiki.ubuntuusers.de/TeX_Live_DVD-Installation/#Anpassung-der-Pfade
and then to tell apt that I have TeXLive
https://wiki.ubuntuusers.de/TeX_Live_DVD-Installation/#Paketverwaltung-die-neue-TeX-Live-Version-mitteilen

I never had any problem with these instructions.
Tobias

-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: texlive 2023 > WHAT DO I HAVE TO DO TO GET 2023 WORKING??

[Herbert Voss]

Am 19.06.23 um 15:11 schrieb Wolfgang Engelmann:

do you have a file texlive.sh in /etc/profile.d/. ?
If yes, what's its contents.


export PATH=/usr/local/texlive/2022/bin/x86_64-linux:$PATH
export MANPATH=/usr/local/texlive/2022/texmf/doc/man:$MANPATH
export INFOPATH=/usr/local/texlive/2022/texmf/doc/info:$INFOPATH
unset TEXINPUTS
unset TEXMFCONFIG


as root change it to 2023






If no, what is the output of

which -a tex


/usr/local/texlive/2022/bin/x86_64-linux/tex
/usr/local/texlive/2022/bin/x86_64-linux/tex
/usr/bin/tex


it looks like an old instance from Debian's own texlive. Delete all files
depending to tex in /usr/bin/, e.g. tex, latex, luatex, ...

After a restart try

which -a latex

Is it now 2023?

Herbert
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: texlive 2023 > WHAT DO I HAVE TO DO TO GET 2023 WORKING??

[Herbert Voss]

Wolfgang Engelmann schrieb:
>
>
> Am 19.06.23 um 15:29 schrieb Herbert Voss:
>>
>>
>> Am 19.06.23 um 15:11 schrieb Wolfgang Engelmann:
 do you have a file texlive.sh in /etc/profile.d/. ?
 If yes, what's its contents.
>>>
>>> export PATH=/usr/local/texlive/2022/bin/x86_64-linux:$PATH
>>> export MANPATH=/usr/local/texlive/2022/texmf/doc/man:$MANPATH
>>> export INFOPATH=/usr/local/texlive/2022/texmf/doc/info:$INFOPATH
>>> unset TEXINPUTS
>>> unset TEXMFCONFIG
>>
>> as root change it to 2023
>>
>>
>>>

 If no, what is the output of

 which -a tex
>>>
>>> /usr/local/texlive/2022/bin/x86_64-linux/tex
>>> /usr/local/texlive/2022/bin/x86_64-linux/tex
>>> /usr/bin/tex
>>
>> it looks like an old instance from Debian's own texlive. Delete all
>> files
>> depending to tex in /usr/bin/, e.g. tex, latex, luatex, ...
>
> There A LOT of files in /usr/bin ..
> I have sudo rm the tex latex lua
> but what else should I remove?

With a correct path setting it shouldn‘t matter. Leave it as it is.


> So far after a restart
> which -a tex
> still gives 2022 >
> /usr/local/texlive/2022/bin/x86_64-linux/tex
>  >> /usr/local/texlive/2022/bin/x86_64-linux/tex

Search for 2022 in your .bashes, .profile, …
There must be entries with 2022. and of course,
control /etc/profile.d again

Herbert

>> After a restart try
>>
>> which -a latex
>>
>> Is it now 2023?
>>
>> Herbert
> --
> lyx-users mailing list
> lyx-users@lists.lyx.org
> http://lists.lyx.org/mailman/listinfo/lyx-users
>




-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: pdflatex build error: Mismatched LaTeX support files detected

[Rich Shepard]

On Mon, 19 Jun 2023, Rich Shepard wrote:


The problem seems to be a biblatex/utf8 issue. The whole error log is
attached and the error starts at line 500.


Er, not so. This just popped up again in a different doc without a
bibliography. But, a second ctrl-h to copy the whole error log produced the
.pdf.

With the first doc, a new ctrl-h also resulted in the .pdf being produced.

I'd still like to understand the error, but since I can send these docs to
my client there's no rush.

Regards,

Rich
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: pdflatex build error: Mismatched LaTeX support files detected

[Herbert Voss]

Am 19.06.23 um 19:52 schrieb Rich Shepard:

The problem seems to be a biblatex/utf8 issue. The whole error log is
attached and the error starts at line 500.

Please teach me how to fix this and avoid future occurrences.



it is a problem with your different latex (expl3) files, they don't match
with its versions. Run an update

(sudo)  tlmgr --self --all update

and run the document again.

However, if you have _local_ versions of latex3 files, then it maybe more
diffucult to fix it.

Herbert
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Time stamp is off

[Richard Kimberly Heck]

On 6/19/23 09:36, R. H. van der Gaag wrote:


Thanks for checking. Insert date gives the correct (Dutch) time here, too. But 
the time stamps added to the LaTeX preview are always exactly two hours behind. 
A riddle.


Two hours behind sounds like UCT (GMT). European time is one hour ahead 
but then another hour for daylight savings. I suspect that your system 
clock is set for UCT, which is what LaTeX is picking up.


I've had similar problems on a Windows system.

Riki


--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Display font shrunk

[Rich Shepard]

On Mon, 19 Jun 2023, Rich Shepard wrote:


In Documents -> Settings -> Display -> Preferences the font settings
haven't changed; the point size is still 12.


Also, reinstalling lyx-2.3.6.1 and yesterday's version of the document makes
no difference. All documents display on screen in the smallest font (5pt?).
I find nothing in any menu to change this.

Rich
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Display font shrunk [FIXED]

[Rich Shepard]

On Mon, 19 Jun 2023, Rich Shepard wrote:

Fixed! I found the solution on a StackOverflow thread from 4yrs/10mos ago:
Ctrl+trackball scroll wheel. Boy howdy! That's something I've not before
encountered in 30+ years using a trackball as the pointy device.

I must have inadvertently been pressing the Ctrl key while scrolling up.

Whew!

Rich
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

pdflatex build error: Mismatched LaTeX support files detected

[Rich Shepard]

The problem seems to be a biblatex/utf8 issue. The whole error log is
attached and the error starts at line 500.

Please teach me how to fix this and avoid future occurrences.

TIA,

RichThis is pdfTeX, Version 3.141592653-2.6-1.40.25 (TeX Live 2023) (preloaded 
format=pdflatex 2023.5.23)  19 JUN 2023 10:45
entering extended mode
 restricted \write18 enabled.
 %&-line parsing enabled.
**BE-lee.tex
(./BE-lee.tex
LaTeX2e <2022-11-01> patch level 1
L3 programming layer <2023-05-15>
(/usr/local/texlive/2023/texmf-dist/tex/latex/koma-script/scrreprt.cls
Document Class: scrreprt 2023/04/24 v3.40 KOMA-Script document class (report)
(/usr/local/texlive/2023/texmf-dist/tex/latex/koma-script/scrkbase.sty
Package: scrkbase 2023/04/24 v3.40 KOMA-Script package (KOMA-Script-dependent b
asics and keyval usage)
(/usr/local/texlive/2023/texmf-dist/tex/latex/koma-script/scrbase.sty
Package: scrbase 2023/04/24 v3.40 KOMA-Script package (KOMA-Script-independent 
basics and keyval usage)
(/usr/local/texlive/2023/texmf-dist/tex/latex/koma-script/scrlfile.sty
Package: scrlfile 2023/04/24 v3.40 KOMA-Script package (file load hooks)
(/usr/local/texlive/2023/texmf-dist/tex/latex/koma-script/scrlfile-hook.sty
Package: scrlfile-hook 2023/04/24 v3.40 KOMA-Script package (using LaTeX hooks)

(/usr/local/texlive/2023/texmf-dist/tex/latex/koma-script/scrlogo.sty
Package: scrlogo 2023/04/24 v3.40 KOMA-Script package (logo)
))) (/usr/local/texlive/2023/texmf-dist/tex/latex/graphics/keyval.sty
Package: keyval 2022/05/29 v1.15 key=value parser (DPC)
\KV@toks@=\toks16
)
Applying: [2021/05/01] Usage of raw or classic option list on input line 252.
Already applied: [/00/00] Usage of raw or classic option list on input line
 368.
)) (/usr/local/texlive/2023/texmf-dist/tex/latex/koma-script/tocbasic.sty
Package: tocbasic 2023/04/24 v3.40 KOMA-Script package (handling toc-files)
\scr@dte@tocline@numberwidth=\skip48
\scr@dte@tocline@numbox=\box51
)
Package tocbasic Info: omitting babel extension for `toc'
(tocbasic) because of feature `nobabel' available
(tocbasic) for `toc' on input line 135.
Class scrreprt Info: File `scrsize11pt.clo' used instead of
(scrreprt)   file `scrsize11.clo' to setup font sizes on input line 266
8.
(/usr/local/texlive/2023/texmf-dist/tex/latex/koma-script/scrsize11pt.clo
File: scrsize11pt.clo 2023/04/24 v3.40 KOMA-Script font size class option (11pt
)
) (/usr/local/texlive/2023/texmf-dist/tex/latex/koma-script/typearea.sty
Package: typearea 2023/04/24 v3.40 KOMA-Script package (type area)
\ta@bcor=\skip49
\ta@div=\count185
\ta@hblk=\skip50
\ta@vblk=\skip51
\ta@temp=\skip52
\footheight=\skip53
Package typearea Info: These are the values describing the layout:
(typearea) DIV  = 10
(typearea) BCOR = 0.0pt
(typearea) \paperwidth  = 597.50793pt
(typearea)  \textwidth  = 418.2pt
(typearea)  DIV departure   = -6%
(typearea)  \evensidemargin = 47.2316pt
(typearea)  \oddsidemargin  = -12.5192pt
(typearea) \paperheight = 845.04694pt
(typearea)  \textheight = 514.20023pt
(typearea)  \topmargin  = 12.2347pt
(typearea)  \headheight = 17.0pt
(typearea)  \headsep= 20.40001pt
(typearea)  \topskip= 11.0pt
(typearea)  \footskip   = 47.6pt
(typearea)  \baselineskip   = 13.6pt
(typearea)  on input line 1798.
)
\c@part=\count186
\c@chapter=\count187
\c@section=\count188
\c@subsection=\count189
\c@subsubsection=\count190
\c@paragraph=\count191
\c@subparagraph=\count192
\scr@dte@chapter@maxnumwidth=\skip54
Class scrreprt Info: using compatibility default `afterindent=bysign'
(scrreprt)   for `\chapter on input line 5961.
\scr@dte@section@maxnumwidth=\skip55
Class scrreprt Info: using compatibility default `runin=bysign'
(scrreprt)   for `\section on input line 5972.
Class scrreprt Info: using compatibility default `afterindent=bysign'
(scrreprt)   for `\section on input line 5972.
\scr@dte@part@maxnumwidth=\skip56
Class scrreprt Info: using compatibility default `afterindent=true'
(scrreprt)   for `\part on input line 5981.
\scr@dte@subsection@maxnumwidth=\skip57
Class scrreprt Info: using compatibility default `runin=bysign'
(scrreprt)   for `\subsection on input line 5991.
Class scrreprt Info: using compatibility default `afterindent=bysign'
(scrreprt)   for `\subsection on input line 5991.
\scr@dte@subsubsection@maxnumwidth=\skip58
Class scrreprt Info: using compatibility default `runin=bysign'
(scrreprt)   for `\subsubsection on input line 6001.
Class scrreprt Info: using compatibility default `afterindent=bysign'
(scrreprt)   for `\subsubsection on input line 6001.
\scr@dte@paragraph@maxnumwidth=\skip59
Class scrreprt Info: using compatibility default `runin=bysign'
(scrreprt)   for `\paragraph 

Re: pdflatex build error: Mismatched LaTeX support files detected

[Paul A. Rubin]

On 6/19/23 13:52, Rich Shepard wrote:

The problem seems to be a biblatex/utf8 issue. The whole error log is
attached and the error starts at line 500.

Please teach me how to fix this and avoid future occurrences.

TIA,

Rich

I think the stuff about UTF-8 right above the error message has nothing 
to do with the error. The error just got discovered after that log line.


Taking the error message at face value, it looks like you somehow ended 
up with a very recent (June 2023) version of TeXLive with a not quite so 
recent (May '23) version of one of the files (expl3.sty). So maybe an 
installation or update of TeXLive got bollixed up? At any rate, it's 
unrelated to LyX. Somebody reported this 
 
with an earlier version of TeXLive and posted what looks like a fix.


Paul
-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: Time stamp is off

[R. H. van der Gaag]

On 19 Jun 2023, at 18:46, Richard Kimberly Heck  wrote:
> 
> On 6/19/23 09:36, R. H. van der Gaag wrote:
>> 
>> Thanks for checking. Insert date gives the correct (Dutch) time here, too. 
>> But the time stamps added to the LaTeX preview are always exactly two hours 
>> behind. A riddle.
> 
> Two hours behind sounds like UCT (GMT). European time is one hour ahead but 
> then another hour for daylight savings. I suspect that your system clock is 
> set for UCT, which is what LaTeX is picking up.
> 
> I've had similar problems on a Windows system.

My macOS preferences say "Central European Summer Time" and in the terminal I 
get

 rh@iMac ~ % date
 Mon Jun 19 21:27:10 CEST 2023

It remains a mystery, then, where LyX or LaTeX gets its UCT/GMT time from. 
Should I worry about this possibly messing up sync?

-- 
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

SOLVED > texlive 2023 > WHAT DO I HAVE TO DO TO GET 2023 WORKING??

[Wolfgang Engelmann]

Am 19.06.23 um 19:00 schrieb Wolfgang Engelmann:



Am 19.06.23 um 17:11 schrieb Wolfgang Engelmann:



Am 19.06.23 um 16:55 schrieb Tobias Hilbricht:

Am Montag, dem 19.06.2023 um 15:57 +0200 schrieb Wolfgang Engelmann:



Am 19.06.23 um 15:29 schrieb Herbert Voss:



Am 19.06.23 um 15:11 schrieb Wolfgang Engelmann:

do you have a file texlive.sh in /etc/profile.d/. ?
If yes, what's its contents.


export PATH=/usr/local/texlive/2022/bin/x86_64-linux:$PATH
export MANPATH=/usr/local/texlive/2022/texmf/doc/man:$MANPATH
export INFOPATH=/usr/local/texlive/2022/texmf/doc/info:$INFOPATH
unset TEXINPUTS
unset TEXMFCONFIG


as root change it to 2023


/usr/local/texlive/2022/bin/x86_64-linux/tex
/usr/local/texlive/2022/bin/x86_64-linux/tex
/usr/bin/tex


it looks like an old instance from Debian's own texlive. Delete all
files
depending to tex in /usr/bin/, e.g. tex, latex, luatex, ...


There A LOT of files in /usr/bin ..
I have sudo rm the tex latex lua
but what else should I remove?


Did you remove Debians "own" TeXLive install completely? Try to find
out if there are packages left from an old install with
apt list --installed | grep texlive
and then remove those packages.
Tobias


Tobias and Herbert,

thanks for the suggestions.
I am upgrading my Debian bullseye to bookworm.
Unfortunately it contains again texlive 2022 instaed of 2023.
It takes quite some time to finish the upgrade. If done, I will try to 
use the proposals for getting finally the desired 2023.




Done. The Version is after changing 2022 to 2223 in
file texlive.sh in /etc/profile.d/ AND in
bashrc
now shown as
latex -v
pdfTeX 3.141592653-2.6-1.40.25 (TeX Live 2023)

Thanks to your help TL it is now working

Wolfgang
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: pdflatex build error: Mismatched LaTeX support files detected

[Rich Shepard]

On Mon, 19 Jun 2023, Paul A. Rubin wrote:


I think the stuff about UTF-8 right above the error message has nothing to
do with the error. The error just got discovered after that log line.


Paul,

Makes sense to me.


Taking the error message at face value, it looks like you somehow ended up
with a very recent (June 2023) version of TeXLive with a not quite so
recent (May '23) version of one of the files (expl3.sty). So maybe an
installation or update of TeXLive got bollixed up? At any rate, it's
unrelated to LyX. Somebody reported this

with an earlier version of TeXLive and posted what looks like a fix.


Yes, I did a tl update earlier this month. Just did another one (34 updates
packages.) Perhaps I need to make this a weekly cron task for root.

Thanks for the URL. Reading that thread I just ran `fmtutil-sys --all' and
now have a different issue:
##
fmtutil: Error! Not all formats have been built successfully.
Visit the log files in directory
  /usr/share/texmf-var/web2c
for details.
###

This is a summary of all `failed' messages and warnings:
`pdfetex -ini  -jobname=amstex -progname=amstex -translate-file=cp227.tcx 
*amstex.ini' failed
`pdfetex -ini  -jobname=bamstex -progname=bamstex -translate-file=cp227.tcx 
bamstex.ini' failed

There are 14 .log files in web2c. Guess that's where my afternoon will be
spent.

Thanks,

Rich


--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users

Re: pdflatex build error: Mismatched LaTeX support files detected

[Rich Shepard]

On Mon, 19 Jun 2023, Herbert Voss wrote:

Herbert,

I'm the only user of this host.


fmtutil-sys --all

$ fmtutil-sys --all
fmtutil: fmtutil is using the following fmtutil.cnf files (in precedence order):
fmtutil:   /usr/local/texlive/2023/texmf-dist/web2c/fmtutil.cnf
fmtutil: fmtutil is using the following fmtutil.cnf file for writing changes:
fmtutil:   /usr/local/texlive/2023/texmf-config/web2c/fmtutil.cnf
fmtutil [ERROR]: format directory not writable: 
/usr/local/texlive/2023/texmf-var/web2c

Huh. Looks okay to me:
$ ll /usr/local/texlive/2023/texmf-var/
total 28
drwxr-xr-x  6 root root 4096 May 23 15:52 fonts/
-rw-r--r--  1 root root 3689 Jun 14 06:03 ls-R
drwxr-xr-x  3 root root 4096 May 23 15:50 luametatex-cache/
drwxr-xr-x  3 root root 4096 May 23 15:50 luatex-cache/
drwxr-xr-x  4 root root 4096 May 23 14:35 tex/
drwxr-xr-x 14 root root 4096 May 23 15:50 web2c/
drwxr-xr-x  2 root root 4096 May 23 14:35 xdvi/


and
sudo fmtutil-sys --all

 ...
###
fmtutil: Error! Not all formats have been built successfully.
Visit the log files in directory
  /usr/share/texmf-var/web2c
for details.
###

This is a summary of all `failed' messages and warnings:
`pdfetex -ini  -jobname=amstex -progname=amstex -translate-file=cp227.tcx 
*amstex.ini' failed
`pdfetex -ini  -jobname=bamstex -progname=bamstex -translate-file=cp227.tcx 
bamstex.ini' failed

What do I read to learn how to properly build amstex and bamstex?


In this case you get local format or system format files.


Different errors when run by user and root.

Thanks,

Rich
--
lyx-users mailing list
lyx-users@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-users