https://bugzilla.redhat.com/show_bug.cgi?id=1458840 David Kaspar [Dee'Kej] <dkaspar@xxxxxxxxxx> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(dkaspar@xxxxxxxxx |needinfo?(zdohnal@xxxxxxxxx |m) |m) --- Comment #27 from David Kaspar [Dee'Kej] <dkaspar@xxxxxxxxxx> --- The latest version: >> https://dkaspar.fedorapeople.org/share/reviews/urw-base35-fonts/v4/ * Added requirement for 'fontpackages-filesystem', to deal with ownership of /usr/share/fonts (this package, however, should be installed on Fedora by default) * Split the %description line to avoid warnings about description being longer than 80 characters. >From version 3: * 'font.dir' and 'font.scale' files have been marked as %ghost files * the upgrading process has been fixed (proper Obsoletes/Provides/Conflicts) Known issues: * error message during installation if the user does not have X11 running: > xset: unable to open display "" ... This has been already reported in BZ #1466254. I expect to reroute the output of that command into /dev/null before F27 Beta, if this is not fixed in X11 by then. * 2 errors regarding 'unknown Type 1 Weight' of the fonts. This is produced by the 'mkfontscale' command, and this is a bug in the fonts source itself. ... I have already reported this to both upstream and URW++, and I'm waiting for their reply. In case they don't fix it, I will add a patch myself that I've created for it. But I don't want to hide the error messages from those commands, because this helps us identify if the fonts became somehow corrupt during rebase. In that case, we can apply patches/report it to upstream, and not just silently hide it. NOTE: I will still be adding fontconfig & appstream files, but these are not mandatory, and I will ask for a review of them in Fedora's fontconfig mailing list. In other words, this is not a blocker for finishing the review. Best regards, Dee'Kej -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list -- package-review@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to package-review-leave@xxxxxxxxxxxxxxxxxxxxxxx
