Your message dated Sat, 14 Mar 2026 11:40:01 +0100
with message-id <[email protected]>
and subject line Re: fonts-xolonium: Please make font bit-for-bit identical to
upstream (enabled OFL+RFN license)
has caused the Debian Bug report #1129301,
regarding fonts-xolonium: Please make font bit-for-bit identical to upstream
(enabled OFL+RFN license)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1129301: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1129301
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: fonts-xolonium
Version: 4.2-2
Tags: patch
Severity: wishlist
Forwarded: https://gitlab.com/sev/xolonium/-/issues/4
Xonotic is dual-licensed under OFL+RFN and GPL2+. Currently Debian
distributes it as a GPL font because the Reserverd Font Name clause of
OFL requires a complete bit-for-bit reproduction of the font files,
something curently cannot be achieved for two reasons:
1) The main reason is that the files released in 4.2
(https://gitlab.com/sev/xolonium/-/releases/v4.2) have been produced
with a version of FontForge that contained some bugs related to the way
metadata is written in TTF/OTF files (in a nutshell: some fields contain
a stray final \0). Newly produced fonts will never match these old files
containing these errors.
2) Also, the files all contain slightly different build timestamps and
the reproducible build supports only one timestamps.
Once these issues are resolved upstream, a mechanism to ensure
bit-for-bit reproduction needs to be in place.
A proof-of-concept MR to do this can be found at
https://salsa.debian.org/fonts-team/fonts-xolonium/-/merge_requests/2
Regards,
--
Gioele Barabucci
--- End Message ---
--- Begin Message ---
Control: tag 1129301 wontfix
Upstream author removed the Reserved Font Name restriction from the
license, thanks!
80% of the problem as been solved:
- upstream files all contains the same timestamp
- upstream used a newer FontForge
- Debian distributes the OFL files starting with v4.3-1
We still can't build files bit-for-bit identical to the ones distributed
upstream, but it doesn't matter anymore.
Sébastien
--- End Message ---
