Bug 1186656
| Summary: | Build fontforge fontforge-20141230-1.fc22.x86_64 for Fedora 21 | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Pravin Satpute <psatpute> |
| Component: | fontforge | Assignee: | Kevin Fenzi <kevin> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 21 | CC: | fonts-bugs, kevin, paul, pnemade |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | fontforge-20141230-1.fc21 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-02-08 08:56:25 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Pravin Satpute
2015-01-28 09:15:22 UTC
So, normally we don't like updating fontforge in a stable release. This is because then the fonts in fedora wouldn't have been built with it, and if they wished to update for some reason they could be broken. However, this time we don't have a mass rebuild for f22, so we dont know if that will break existing fonts either. ;) So, I am ok with pushing this to f21, but will wait a bit to hear from my co-maintainers as to what they think. I have already done testing for all fonts packages in Nov. 2014 using initial fontforge2 build fontforge-20140813-3.fc22.x86_64. See https://copr.fedoraproject.org/coprs/pnemade/ff2-rebuild/ One failure was this -> https://copr.fedoraproject.org/coprs/pnemade/ff2-rebuild/build/58193/ which is already fixed in http://pkgs.fedoraproject.org/cgit/oflb-prociono-fonts.git/commit/?id=ae365492c58eb80ed2f406800ca43ed8be700b8d and another is reported in bug 1147421 which is already reported in upstream https://github.com/fontforge/fontforge/issues/1756 but still not fixed. I am also personally using this build fontforge-20140813-3.fc21.x86_64 from my own copr repo and it looks working fine though I have not used it heavily for any font issues recently. I will be fine to have this new fontforge built in Fedora 21. I spoke too soon for oxygen-fonts issue. It looks like its fixed in recent fontforge release fontforge-20141230-1.fc22. See the build https://copr.fedoraproject.org/coprs/pnemade/ff2-rebuild/build/69689/ succeeded after removing disable fontforge patch from oxygen-fonts.spec file. (In reply to Kevin Fenzi from comment #1) > > So, I am ok with pushing this to f21, but will wait a bit to hear from my > co-maintainers as to what they think. As Parag has done the groundwork in retesting our fonts, I think it makes sense to move forward. It would pay to check versions of the sister projects libuninameslist and libspiro at the same time. (Parag may have done this; I haven't had a look recently.) I don't see any specific version requirement of any of the build dependencies in configure script. Currently we have same build available for libuninameslist and libspiro in F22 and F21. so this should not be a problem. fontforge-20141230-1.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/fontforge-20141230-1.fc21 Package fontforge-20141230-1.fc21: * should fix your issue, * was pushed to the Fedora 21 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing fontforge-20141230-1.fc21' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-1429/fontforge-20141230-1.fc21 then log in and leave karma (feedback). fontforge-20141230-1.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report. |