This bug appears to have been reported against 'rawhide' during the Fedora 29 development cycle.
Changing version to '29'.
As of last month, unifont is now at release 11.0.02.
Can someone retitle/retarget this bug (especially since rawhide is already at 10.0.07, currently), or should I open a new one?
The update to 10.0.* went out long ago. Let's close this.