Bug 1307588 - gource: FTBFS in rawhide
Summary: gource: FTBFS in rawhide
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: gource
Version: 24
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Gwyn Ciesla
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F24FTBFS
TreeView+ depends on / blocked
 
Reported: 2016-02-13 21:31 UTC by Fedora Release Engineering
Modified: 2016-02-25 16:01 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-02-25 16:01:02 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
build.log (62.76 KB, text/plain)
2016-02-13 21:31 UTC, Fedora Release Engineering
no flags Details
root.log (101.91 KB, text/plain)
2016-02-13 21:31 UTC, Fedora Release Engineering
no flags Details
state.log (613 bytes, text/plain)
2016-02-13 21:31 UTC, Fedora Release Engineering
no flags Details

Description Fedora Release Engineering 2016-02-13 21:31:45 UTC
Your package gource failed to build from source in current rawhide.

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

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

Comment 1 Fedora Release Engineering 2016-02-13 21:31:47 UTC
Created attachment 1124828 [details]
build.log

Comment 2 Fedora Release Engineering 2016-02-13 21:31:48 UTC
Created attachment 1124829 [details]
root.log

Comment 3 Fedora Release Engineering 2016-02-13 21:31:49 UTC
Created attachment 1124830 [details]
state.log

Comment 4 Jan Kurik 2016-02-24 14:45:23 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 Upstream Release Monitoring 2016-02-25 15:53:48 UTC
limb's gource-0.43-9.fc25 completed http://koji.fedoraproject.org/koji/buildinfo?buildID=738917


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