Bug 1239441 - eclipse-m2e-sourcelookup: FTBFS in rawhide
Summary: eclipse-m2e-sourcelookup: FTBFS in rawhide
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: eclipse-m2e-sourcelookup
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Mikolaj Izdebski
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F23FTBFS
TreeView+ depends on / blocked
 
Reported: 2015-07-05 20:53 UTC by Dennis Gilmore
Modified: 2015-07-13 06:17 UTC (History)
5 users (show)

Fixed In Version: 1.1.0.201406131218-3.git192e51f
Clone Of:
Environment:
Last Closed: 2015-07-13 06:17:57 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
build.log (27.85 KB, text/plain)
2015-07-05 20:53 UTC, Dennis Gilmore 		no flags Details
root.log (160.02 KB, text/plain)
2015-07-05 20:53 UTC, Dennis Gilmore 		no flags Details
state.log (785 bytes, text/plain)
2015-07-05 20:53 UTC, Dennis Gilmore 		no flags Details
View All

Description Dennis Gilmore 2015-07-05 20:53:26 UTC 
Your package eclipse-m2e-sourcelookup failed to build from source in current rawhide.

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

For details on mass rebuild see https://fedoraproject.org/wiki/Fedora_23_Mass_Rebuild
Comment 1 Dennis Gilmore 2015-07-05 20:53:28 UTC 
Created attachment 1046641 [details]
build.log
Comment 2 Dennis Gilmore 2015-07-05 20:53:28 UTC 
Created attachment 1046642 [details]
root.log
Comment 3 Dennis Gilmore 2015-07-05 20:53:29 UTC 
Created attachment 1046643 [details]
state.log
Comment 4 Mikolaj Izdebski 2015-07-13 06:17:52 UTC 
Fixed in eclipse-m2e-sourcelookup-1.1.0.201406131218-3.git192e51f
Comment 5 Mikolaj Izdebski 2015-07-13 06:17:57 UTC 
I believe that this bug is fixed in eclipse-m2e-sourcelookup-1.1.0.201406131218-3.git192e51f,
which is available in Fedora Rawhide, so I am closing this bug now.

The build containing the fix can be found at Koji:
http://koji.fedoraproject.org/koji/buildinfo?buildID=668371
Note You need to log in before you can comment on or make changes to this bug.