Discussion:
Fixed compilation date in the .log file
(too old to reply)
Daniel Flipo
2018-04-05 10:17:55 UTC
Permalink
Raw Message
Hi all,

I have just installed TeXLive 2018 pretest (2018/04/05).

With all formats the compilation date and time written at the beginning
of the .log file is replaced by a fixed one (20 MAY 2016) f.i. I get:

This is LuaTeX, Version 1.07.0 (TeX Live 2018) (format=luatex 2018.4.5)
20 MAY 2016 11:00

This is XeTeX, Version 3.14159265-2.6-0.99999 (TeX Live 2018) (preloaded
format=xelatex 2018.4.5) 20 MAY 2016 09:00

This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2018)
(preloaded format=pdflatex 2018.4.5) 20 MAY 2016 09:00

Not a big deal ;-) thanks for your hard work!
--
Daniel Flipo
Akira Kakuto
2018-04-05 10:40:45 UTC
Permalink
Raw Message
Post by Daniel Flipo
This is XeTeX, Version 3.14159265-2.6-0.99999 (TeX Live 2018) (preloaded
format=xelatex 2018.4.5) 20 MAY 2016 09:00
Maybe you are setting variables
export FORCE_SOURCE_DATE=1
export SOURCE_DATE_EPOCH=...

Best,
Akira
Daniel Flipo
2018-04-05 13:51:18 UTC
Permalink
Raw Message
Post by Akira Kakuto
Post by Daniel Flipo
This is XeTeX, Version 3.14159265-2.6-0.99999 (TeX Live 2018) (preloaded
format=xelatex 2018.4.5)  20 MAY 2016 09:00
Maybe you are setting variables
export FORCE_SOURCE_DATE=1
export SOURCE_DATE_EPOCH=...
No these variables are not set on my system (Linux Debian) and while
compiling with TL2017, the current date and time are printed as expected
in the .log file.

Best,
--
Daniel Flipo
Norbert Preining
2018-04-05 14:40:58 UTC
Permalink
Raw Message
HI
Post by Daniel Flipo
I have just installed TeXLive 2018 pretest (2018/04/05).
With all formats the compilation date and time written at the beginning
Not reproducible by me, just run trivial Hello World through pdflatex
and got this in the log file:
This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2018) (preloaded format=pdflatex 2018.4.4) 5 APR 2018 23:37


Full run:
[~] pdflatex
This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2018) (preloaded format=pdflatex)
restricted \write18 enabled.
**\relax
entering extended mode
LaTeX2e <2017-04-15>
Babel <3.18> and hyphenation patterns for 84 language(s) loaded.

*\documentclass{article}

*\begin{document}
(/home/norbert/tl/2018/texmf-dist/tex/latex/base/article.cls
Document Class: article 2014/09/29 v1.4h Standard LaTeX document class
(/home/norbert/tl/2018/texmf-dist/tex/latex/base/size10.clo))
No file texput.aux.

*Hello World

*\end{document}
[1{/home/norbert/tl/2018/texmf-var/fonts/map/pdftex/updmap/pdftex.map}]
(./texput.aux)</home/norbert/tl/2018/texmf-dist/fonts/type1/public/amsfonts/cm/
cmr10.pfb>
Output written on texput.pdf (1 page, 11534 bytes).
Transcript written on texput.log.


I also tried with TL2018/Debian from experimental, same result.

So I am quite sure that you have some env vars as described by Akira set
somehow. Maybe when *BUILDING* the formats.

Best

Norbert

--
PREINING Norbert http://www.preining.info
Accelia Inc. + JAIST + TeX Live + Debian Developer
GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
Daniel Flipo
2018-04-05 15:24:02 UTC
Permalink
Raw Message
Post by Norbert Preining
So I am quite sure that you have some env vars as described by Akira set
somehow. Maybe when *BUILDING* the formats.
Thanks Norbert! I rebuilt the formats (fmtutil-sys --all) and the
date/time is now correct in the .log files.

I still do not understand what happened during the first build of the
formats by the genuine TL2018-pretest installation. It was done as an
unprivileged user (me, not "root") and I /didn't/ change any ENV
variables in between…

Best,
--
Daniel Flipo
Daniel Flipo
2018-04-05 19:56:57 UTC
Permalink
Raw Message
Post by Daniel Flipo
I still do not understand what happened during the first build of the
formats by the genuine TL2018-pretest installation. It was done as an
unprivileged user (me, not "root") and I /didn't/ change any ENV
variables in between…
I have investigated a bit further: actually the fixed compilation time
only occurs when I run test files through the l3build system (both with
TL2017 or TL2018), not with normal files.

I guess this is done on purpose by the l3build system to avoid
differences when checking regression files. I had never noticed this
before :-(

Sorry for the noise!
--
Daniel Flipo
Akira Kakuto
2018-04-05 20:23:05 UTC
Permalink
Raw Message
Post by Daniel Flipo
I guess this is done on purpose by the l3build system to avoid
differences when checking regression files. I had never noticed this
before :-(
Many thanks. I didn't know that. I can find in
l3build-aux.lua:

function setepoch()
return
os_setenv .. " SOURCE_DATE_EPOCH=" .. epoch
.. os_concat ..
os_setenv .. " SOURCE_DATE_EPOCH_TEX_PRIMITIVES=1"
.. os_concat ..
os_setenv .. " FORCE_SOURCE_DATE=1"
.. os_concat
end

Best,
Akira
Joseph Wright
2018-04-05 20:28:57 UTC
Permalink
Raw Message
Post by Akira Kakuto
Post by Daniel Flipo
I guess this is done on purpose by the l3build system to avoid
differences when checking regression files.  I had never noticed this
before :-(
Many thanks. I didn't know that. I can find in
function setepoch()
 return
   os_setenv .. " SOURCE_DATE_EPOCH=" .. epoch
     .. os_concat ..
   os_setenv .. " SOURCE_DATE_EPOCH_TEX_PRIMITIVES=1"
     .. os_concat ..
   os_setenv .. " FORCE_SOURCE_DATE=1"
     .. os_concat
end
Best,
Akira
We've recently adjusted the defaults so the above doesn't apply
as-standard to documentation typesetting.

Joseph
Norbert Preining
2018-04-05 23:52:02 UTC
Permalink
Raw Message
Post by Daniel Flipo
I guess this is done on purpose by the l3build system to avoid
Yes, it is, and one of the reasons why S_D_E is there ;-)

Norbert

--
PREINING Norbert http://www.preining.info
Accelia Inc. + JAIST + TeX Live + Debian Developer
GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
Loading...