Bug 1240005 - sil-padauk-fonts: FTBFS in rawhide
Summary: sil-padauk-fonts: FTBFS in rawhide
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: sil-padauk-fonts
Version: 23
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Parag Nemade
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F23FTBFS
TreeView+ depends on / blocked
 
Reported: 2015-07-05 21:23 UTC by Dennis Gilmore
Modified: 2015-07-21 06:12 UTC (History)
3 users (show)

Fixed In Version: sil-padauk-fonts-2.8-9.fc23
Clone Of:
Environment:
Last Closed: 2015-07-21 06:12:33 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
build.log (8.22 KB, text/plain)
2015-07-05 21:23 UTC, Dennis Gilmore 		no flags Details
root.log (72.73 KB, text/plain)
2015-07-05 21:23 UTC, Dennis Gilmore 		no flags Details
state.log (649 bytes, text/plain)
2015-07-05 21:23 UTC, Dennis Gilmore 		no flags Details
View All

Description Dennis Gilmore 2015-07-05 21:23:55 UTC 
Your package sil-padauk-fonts failed to build from source in current rawhide.

http://koji.fedoraproject.org/koji/taskinfo?taskID=10153454

For details on mass rebuild see https://fedoraproject.org/wiki/Fedora_23_Mass_Rebuild
Comment 1 Dennis Gilmore 2015-07-05 21:23:56 UTC 
Created attachment 1048330 [details]
build.log
Comment 2 Dennis Gilmore 2015-07-05 21:23:57 UTC 
Created attachment 1048331 [details]
root.log
Comment 3 Dennis Gilmore 2015-07-05 21:23:57 UTC 
Created attachment 1048332 [details]
state.log
Comment 4 Jan Kurik 2015-07-15 13:24:44 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 23 development cycle.
Changing version to '23'.

(As we did not run this process for some time, it could affect also pre-Fedora 23 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 23 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora23
Note You need to log in before you can comment on or make changes to this bug.