Bug 963613

Summary: Ninja 1.2.0 released
Product: [Fedora] Fedora Reporter: Haïkel Guémar <karlthered>
Component: ninja-buildAssignee: Ben Boeckel <fedora>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: fedora
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-06-10 03:39:57 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:
Attachments:
Description Flags
updated spec for ninja 1.2.0 none

Description Haïkel Guémar 2013-05-16 08:59:13 UTC
Created attachment 748671 [details]
updated spec for ninja 1.2.0

Ninja 1.2.0 has been released in April, 5 2013

An updated spec has been attached, it has been tested on F18/F19 and rawhide.
At the very least, it should be shipped with F19.
You can use spectool -g to retrieve the source from github.

Comment 1 Ben Boeckel 2013-06-10 03:39:57 UTC
Version 1.3.4 building for Rawhide now; will follow up with F18 and F19 builds and updates.

Comment 2 Fedora Update System 2013-06-10 03:46:42 UTC
ninja-build-1.3.4-1.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/ninja-build-1.3.4-1.fc19

Comment 3 Fedora Update System 2013-06-10 03:46:51 UTC
ninja-build-1.3.4-1.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/ninja-build-1.3.4-1.fc18

Comment 4 Fedora Update System 2013-06-18 06:23:27 UTC
ninja-build-1.3.4-1.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 5 Fedora Update System 2013-06-21 02:06:47 UTC
ninja-build-1.3.4-1.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.