Control: reopen -1
Control: tags -1 patch
On Thu, 3 Jul 2025 17:23:12 +0200 Chris =?utf-8?Q?Hofst=C3=A4dtler?=
<[email protected]> wrote:
Source: fonts-atarist
Version: 0+git20230822+ds-2
Severity: normal
User: [email protected]
Usertags: timestamps
Hi,
apparently the build process for the .otf files captures the current
time, not honoring SOURCE_DATE_EPOCH.
The automated rebuilds on reproduce.debian.net show diffs like this:
│ │ ├── ./usr/share/fonts/opentype/fonts-atarist/atarist-normal.otf
│ │ │ │ Created by FontForge 16:46 30-June-2024
│ │ │ │ - Font created: Thu Jul 18 05:46:45 2024
│ │ │ │ + Font created: Tue Jun 17 21:17:58 2025
...
│ │ │ │ - File created: Thu Jul 18 05:46:45 2024
│ │ │ │ + create[1]=e4778c06
│ │ │ │ + File created: Tue Jun 17 21:17:58 2025
...
Please fix this by honoring SOURCE_DATE_EPOCH at build time. If this is a
problem in FontForge, please help fixing FontForge.
This issue is due to the fact that bdf2sfd embeds the creation timestamp
in the SFD file (<https://bugs.debian.org/1126820>) and FontForge copies
it into the generated OTF file (this is the correct behavior).
Regards,
--
Gioele Barabucci
