Bug 1606577 - trytond-calendar: FTBFS in Fedora rawhide
Summary: trytond-calendar: FTBFS in Fedora rawhide
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: trytond-calendar
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Dan Horák
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F29FTBFS
TreeView+ depends on / blocked
 
Reported: 2018-07-20 20:41 UTC by Mohan Boddu
Modified: 2018-07-23 09:05 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-07-23 09:05:51 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
build.log (3.61 KB, text/plain)
2018-07-20 20:41 UTC, Mohan Boddu 		no flags Details
root.log (32.00 KB, text/plain)
2018-07-20 20:42 UTC, Mohan Boddu 		no flags Details
state.log (655 bytes, text/plain)
2018-07-20 20:42 UTC, Mohan Boddu 		no flags Details
View All

Description Mohan Boddu 2018-07-20 20:41:48 UTC 
trytond-calendar failed to build from source in Fedora rawhide

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


For details on the mass rebuild see:

https://fedoraproject.org/wiki/Fedora_29_Mass_Rebuild
Please fix trytond-calendar 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,
trytond-calendar will be orphaned. Before branching of Fedora 30,
trytond-calendar 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-20 20:41:57 UTC 
Created attachment 1468673 [details]
build.log
Comment 2 Mohan Boddu 2018-07-20 20:42:03 UTC 
Created attachment 1468674 [details]
root.log

file root.log too big, will only attach last 32768 bytes
Comment 3 Mohan Boddu 2018-07-20 20:42:07 UTC 
Created attachment 1468675 [details]
state.log
Comment 4 Dan Horák 2018-07-23 09:05:51 UTC 
package has been retired
Note You need to log in before you can comment on or make changes to this bug.