Bug 1239459 - erlang-emmap: FTBFS in rawhide
Summary: erlang-emmap: FTBFS in rawhide
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: erlang-emmap
Version: 23
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Peter Lemenkov
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F23FTBFS
TreeView+ depends on / blocked
 
Reported: 2015-07-05 20:54 UTC by Dennis Gilmore
Modified: 2016-02-10 14:13 UTC (History)
2 users (show)

Fixed In Version: erlang-emmap-0-0.14.git05ae1bb.fc24
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-02-10 14:13:16 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
build.log (9.00 KB, text/plain)
2015-07-05 20:54 UTC, Dennis Gilmore
no flags Details
root.log (95.21 KB, text/plain)
2015-07-05 20:54 UTC, Dennis Gilmore
no flags Details
state.log (681 bytes, text/plain)
2015-07-05 20:54 UTC, Dennis Gilmore
no flags Details

Description Dennis Gilmore 2015-07-05 20:54:20 UTC
Your package erlang-emmap failed to build from source in current rawhide.

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

For details on mass rebuild see https://fedoraproject.org/wiki/Fedora_23_Mass_Rebuild

Comment 1 Dennis Gilmore 2015-07-05 20:54:21 UTC
Created attachment 1046695 [details]
build.log

Comment 2 Dennis Gilmore 2015-07-05 20:54:22 UTC
Created attachment 1046696 [details]
root.log

Comment 3 Dennis Gilmore 2015-07-05 20:54:22 UTC
Created attachment 1046697 [details]
state.log

Comment 4 Jan Kurik 2015-07-15 13:45:53 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.