Bug 1307884 - puzzle-master: FTBFS in rawhide
Summary: puzzle-master: FTBFS in rawhide
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: puzzle-master
Version: 24
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Timur Kristóf
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F24FTBFS
TreeView+ depends on / blocked
 
Reported: 2016-02-13 22:03 UTC by Fedora Release Engineering
Modified: 2017-05-15 19:35 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-05-15 19:35:24 UTC
Type: ---

Attachments (Terms of Use)
build.log (13.57 KB, text/plain)
2016-02-13 22:03 UTC, Fedora Release Engineering 		no flags Details
root.log (93.63 KB, text/plain)
2016-02-13 22:03 UTC, Fedora Release Engineering 		no flags Details
state.log (649 bytes, text/plain)
2016-02-13 22:04 UTC, Fedora Release Engineering 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Fedora Release Engineering 2016-02-13 22:03:56 UTC 
Your package puzzle-master failed to build from source in current rawhide.

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

For details on mass rebuild see https://fedoraproject.org/wiki/Fedora_24_Mass_Rebuild
Comment 1 Fedora Release Engineering 2016-02-13 22:03:58 UTC 
Created attachment 1125713 [details]
build.log
Comment 2 Fedora Release Engineering 2016-02-13 22:03:59 UTC 
Created attachment 1125714 [details]
root.log
Comment 3 Fedora Release Engineering 2016-02-13 22:04:00 UTC 
Created attachment 1125715 [details]
state.log
Comment 4 Jan Kurik 2016-02-24 15:00:32 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 24 development cycle.
Changing version to '24'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora24#Rawhide_Rebase
Comment 5 Timur Kristóf 2017-05-15 19:34:51 UTC 
This issue has been fixed by the release engineering team by using the %{qmake_qt4} macro instead of simply qmake-qt4.
Note You need to log in before you can comment on or make changes to this bug.