From: zimoun <zimon.toutoune@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 28173@debbugs.gnu.org
Subject: bug#28173: texlive-texmf-minimal not reproducible
Date: Tue, 12 Oct 2021 23:50:44 +0200 [thread overview]
Message-ID: <86o87tkj4b.fsf@gmail.com> (raw)
In-Reply-To: <8735q4pxr2.fsf@elephly.net> (Ricardo Wurmus's message of "Thu, 16 Sep 2021 13:26:25 +0200")
Hi Ricardo,
On Thu, 16 Sep 2021 at 13:26, Ricardo Wurmus <rekado@elephly.net> wrote:
> Many of the modular texlive packages have reproducibility issues.
>
> Take texlive-cm for example. METAFONT writes a timestamp into
> every generated font file
> (e.g. /gnu/store/lkmiyfzi1bq571yn4gypbcs5vn4fpma7-texlive-cm-51265/share/texmf-dist/fonts/tfm/public/cm/cmvtt10.600gf).
> It also generates log files that contain timestamped lines like
> these:
>
> │ │ │ │ │ │ ├── +++
> /gnu/store/lkmiyfzi1bq571yn4gypbcs5vn4fpma7-texlive-cm-51265/share/texmf-dist/fonts/tfm/public/cm/cmu10.log
[..]
> Perhaps we could just delete this log file.
Yeah, maybe this file could be removed -- if this log file follows a
pattern for the various TeXlive packages.
For instance, these…
> /gnu/store/2x6jddfgfg5rp342wsrsl5gssz2lkd06-texlive-union-51265/share/texmf-dist/fonts/map/dvips/updmap/:
> │ │ │ │ - 15890 2021-09-16 11:24:07 builtin35.map
> │ │ │ │ - 21363 2021-09-16 11:24:07 download35.map
> │ │ │ │ - 21470 2021-09-16 11:24:07 psfonts_pk.map
> │ │ │ │ - 21674 2021-09-16 11:24:07 psfonts_t1.map
> │ │ │ │ - 21669 2021-09-16 11:24:07 ps2pk.map
> │ │ │ │ - 14 2021-09-16 11:24:07 psfonts.map ->
> psfonts_t1.map
> │ │ │ │ + 15890 2021-09-16 11:24:06 builtin35.map
> │ │ │ │ + 21363 2021-09-16 11:24:06 download35.map
> │ │ │ │ + 21470 2021-09-16 11:24:06 psfonts_pk.map
> │ │ │ │ + 21674 2021-09-16 11:24:06 psfonts_t1.map
> │ │ │ │ + 21669 2021-09-16 11:24:06 ps2pk.map
> │ │ │ │ + 14 2021-09-16 11:24:06 psfonts.map ->
> psfonts_t1.map
> │ │ │ │
> /gnu/store/2x6jddfgfg5rp342wsrsl5gssz2lkd06-texlive-union-51265/share/texmf-dist/fonts/map/pdftex/updmap/:
> │ │ │ │ - 21676 2021-09-16 11:24:07 pdftex_dl14.map
> │ │ │ │ - 20011 2021-09-16 11:24:07 pdftex_ndl14.map
> │ │ │ │ - 15 2021-09-16 11:24:07 pdftex.map ->
> pdftex_dl14.map
> │ │ │ │ + 21676 2021-09-16 11:24:06 pdftex_dl14.map
> │ │ │ │ + 20011 2021-09-16 11:24:06 pdftex_ndl14.map
> │ │ │ │ + 15 2021-09-16 11:24:06 pdftex.map ->
> pdftex_dl14.map
> │ │ │ │
> /gnu/store/2x6jddfgfg5rp342wsrsl5gssz2lkd06-texlive-union-51265/share/texmf-dist/fonts/map/dvipdfmx/updmap/:
> │ │ │ │ - 413 2021-09-16 11:24:07 kanjix.map
> │ │ │ │ + 413 2021-09-16 11:24:06 kanjix.map
…seem annoying. Is it possible to set the date at Big Bang, i.e.,
1970-01-01 00:00:00 UTC?
Cheers,
simon
prev parent reply other threads:[~2021-10-12 21:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-21 14:23 bug#28173: texlive-texmf-minimal not reproducible Danny Milosavljevic
2017-08-21 14:43 ` Ricardo Wurmus
2017-10-09 21:39 ` Ricardo Wurmus
2021-09-16 6:43 ` zimoun
2021-09-16 11:26 ` Ricardo Wurmus
2021-10-12 21:50 ` zimoun [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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86o87tkj4b.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=28173@debbugs.gnu.org \
--cc=rekado@elephly.net \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).