Closed ronaldtse closed 2 years ago
https://github.com/metanorma/metanorma-ogc/issues/357
As reported by @gbuehler the google/stix_two_math fonts have mismatched checksums.
@alexeymorozov can you please help update the formula to reflect this? Also, is there a way to avoid these issues in the future? (e.g. relax font hash matching but only display a warning).
I have attempted to run Metanorma via the .gitlab-ci.yml file on the Gitlab pipeline and also locally
docker run -v "$(pwd)":/metanorma metanorma/mn metanorma compile -t ogc -x xml,html,doc,pdf --agree-to-terms document.adoc
on several different repositories (one of which build successfully yesterday with no changes)
Here is the snippet of the log:
`....
- /config/fonts/trebucbi.ttf
- /config/fonts/Verdanaz.ttf Downloading font "google/stix_two_math" from https://fonts.google.com/download?family=STIX%20Two%20Math /usr/local/bundle/gems/fontist-1.13.0/lib/fontist/utils/downloader.rb:39:in
raise_if_tampered': The downloaded file from https://fonts.google.com/download?family=STIX%20Two%20Math doesn't match with the expected sha256 checksum (429bd510636b72ac19d9dbcdaa5d4e3992bd9719bcb5e175be468110c971877c)! (Fontist::Errors::TamperedFileError) Beginning of content: PK\x03\x04\x14\0\b\b\b\0\0\0�R\0\0\0\0\0\0\0\0\0\0\0\0\a\0\0\0OFL.txt�Wێ��\x11}'�\c?(�C�\x0183\x1Eg�\0~�%�C�Di)��~�Ȗ�1�f�I���/ɧ�Kr����8�e��5dwթSU��#����l;�����݇�\x1F\x1E)� Zf��4QM ....
I understand that the issue is with the font package, but is there a way to bypass such problems?
@alexeymorozov I think the Google STIX two font package is too unstable. Let's change to use the official release from GitHub.
https://github.com/stipub/stixfonts/releases
Latest is 2.13b171: https://github.com/stipub/stixfonts/archive/refs/tags/v2.13b171.zip