Bug 1604480 - kdevelop: FTBFS in Fedora rawhide
Summary: kdevelop: FTBFS in Fedora rawhide
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: kdevelop
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F29FTBFS
TreeView+ depends on / blocked
 
Reported: 2018-07-19 22:55 UTC by Mohan Boddu
Modified: 2018-07-23 13:17 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-07-23 13:17:22 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
build.log (32.00 KB, text/plain)
2018-07-19 22:55 UTC, Mohan Boddu
no flags Details
root.log (32.00 KB, text/plain)
2018-07-19 22:55 UTC, Mohan Boddu
no flags Details
state.log (623 bytes, text/plain)
2018-07-19 22:55 UTC, Mohan Boddu
no flags Details

Description Mohan Boddu 2018-07-19 22:55:14 UTC
kdevelop failed to build from source in Fedora rawhide

https://koji.fedoraproject.org/koji/taskinfo?taskID=28193176


For details on the mass rebuild see:

https://fedoraproject.org/wiki/Fedora_29_Mass_Rebuild
Please fix kdevelop at your earliest convenience and set the bug's status to
ASSIGNED when you start fixing it. If the bug remains in NEW state for 8 weeks,
kdevelop will be orphaned. Before branching of Fedora 30,
kdevelop will be retired, if it still fails to build.

For more details on the FTBFS policy, please visit:
https://fedoraproject.org/wiki/Fails_to_build_from_source

Comment 1 Mohan Boddu 2018-07-19 22:55:24 UTC
Created attachment 1463321 [details]
build.log

file build.log too big, will only attach last 32768 bytes

Comment 2 Mohan Boddu 2018-07-19 22:55:29 UTC
Created attachment 1463322 [details]
root.log

file root.log too big, will only attach last 32768 bytes

Comment 3 Mohan Boddu 2018-07-19 22:55:33 UTC
Created attachment 1463323 [details]
state.log

Comment 4 Than Ngo 2018-07-23 13:17:22 UTC
it's fixed in kdevelop-5.2.3-3.fc29


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