Bug 1423097 - GMT: FTBFS in rawhide
Summary: GMT: FTBFS in rawhide
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: GMT
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ralf Corsepius
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 1417385
Blocks: F26FTBFS
TreeView+ depends on / blocked
 
Reported: 2017-02-17 02:47 UTC by Fedora Release Engineering
Modified: 2017-02-22 08:10 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-02-22 08:05:38 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
build.log (1.11 KB, text/plain)
2017-02-17 02:47 UTC, Fedora Release Engineering 		no flags Details
root.log (70.68 KB, text/plain)
2017-02-17 02:47 UTC, Fedora Release Engineering 		no flags Details
state.log (461 bytes, text/plain)
2017-02-17 02:47 UTC, Fedora Release Engineering 		no flags Details
View All

Description Fedora Release Engineering 2017-02-17 02:47:00 UTC 
Your package GMT failed to build from source in current rawhide.

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

For details on mass rebuild see https://fedoraproject.org/wiki/Fedora_26_Mass_Rebuild
Comment 1 Fedora Release Engineering 2017-02-17 02:47:04 UTC 
Created attachment 1251060 [details]
build.log
Comment 2 Fedora Release Engineering 2017-02-17 02:47:07 UTC 
Created attachment 1251061 [details]
root.log
Comment 3 Fedora Release Engineering 2017-02-17 02:47:09 UTC 
Created attachment 1251062 [details]
state.log
Comment 4 Ralf Corsepius 2017-02-22 07:49:21 UTC 
Taking. The cause for the FTBFS seems to have been the GCC ppc64le issues, which meanwhile appear to have been resolved.

A scratch-build has just succeed, so I am going to launch a real build.
Comment 5 Upstream Release Monitoring 2017-02-22 08:03:55 UTC 
corsepiu's GMT-5.3.1-2.fc26 completed http://koji.fedoraproject.org/koji/buildinfo?buildID=840051
Note You need to log in before you can comment on or make changes to this bug.