Bug 1231398 - fontforge-20150612 is available
Summary: fontforge-20150612 is available
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: fontforge
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kevin Fenzi
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-06-13 00:34 UTC by Upstream Release Monitoring
Modified: 2015-06-15 05:10 UTC (History)
4 users (show)

Fixed In Version: fontforge-20150612-1.fc23
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-15 05:10:06 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
[patch] Update to 20150612 (#1231398) (922 bytes, text/x-diff)
2015-06-13 00:35 UTC, Upstream Release Monitoring
no flags Details

Description Upstream Release Monitoring 2015-06-13 00:34:38 UTC
Latest upstream release: 20150612
Current version/release in rawhide: 20150430-1.fc23
URL: https://github.com/fontforge/fontforge

Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy

More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring

Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.

Comment 1 Upstream Release Monitoring 2015-06-13 00:35:10 UTC
Created attachment 1038202 [details]
[patch] Update to 20150612 (#1231398)

Comment 2 Upstream Release Monitoring 2015-06-13 12:21:14 UTC
pnemade's fontforge-20150612-1.fc23 completed http://koji.fedoraproject.org/koji/buildinfo?buildID=645795

Comment 3 Parag Nemade 2015-06-15 05:10:06 UTC
fixed in fontforge-20150612-1.fc23


Note You need to log in before you can comment on or make changes to this bug.