Bug 539051 - FTBFS monodevelop-debugger-mdb-2.1.0-1.fc12
Summary: FTBFS monodevelop-debugger-mdb-2.1.0-1.fc12
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: monodevelop-debugger-mdb
Version: 13
Hardware: i386
OS: Linux
high
high
Target Milestone: ---
Assignee: Mauricio Henriquez
QA Contact: Fedora Extras Quality Assurance
URL: http://linux.dell.com/files/fedora/Fi...
Whiteboard:
Depends On:
Blocks: F13FTBFS
TreeView+ depends on / blocked
 
Reported: 2009-11-19 16:35 UTC by FTBFS
Modified: 2010-06-03 15:47 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-06-03 15:47:59 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
root.log (18.87 KB, text/plain)
2009-11-19 16:36 UTC, FTBFS 		no flags Details
build.log (651 bytes, text/plain)
2009-11-19 16:36 UTC, FTBFS 		no flags Details
mock.log (948 bytes, text/plain)
2009-11-19 16:36 UTC, FTBFS 		no flags Details
View All

Description FTBFS 2009-11-19 16:35:58 UTC 
monodevelop-debugger-mdb-2.1.0-1.fc12.src.rpm Failed To Build From Source against the rawhide tree.  See http://fedoraproject.org/wiki/FTBFS for more information.
Comment 1 FTBFS 2009-11-19 16:36:01 UTC 
Setting to ASSIGNED per Fedora Bug Triage workflow.  https://fedoraproject.org/wiki/BugZappers/BugStatusWorkFlow
Comment 2 FTBFS 2009-11-19 16:36:04 UTC 
Created attachment 371351 [details]
root.log

root.log for i386
Comment 3 FTBFS 2009-11-19 16:36:05 UTC 
Created attachment 371352 [details]
build.log

build.log for i386
Comment 4 FTBFS 2009-11-19 16:36:07 UTC 
Created attachment 371353 [details]
mock.log

mock.log for i386
Comment 5 Bug Zapper 2010-03-15 13:11:49 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 13 development cycle.
Changing version to '13'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Comment 6 Matt Domsch 2010-06-03 15:47:59 UTC 
monodevelop-debugger-mdb-2.3.1-1.fc14.src.rpm
builds in rawhide.
Note You need to log in before you can comment on or make changes to this bug.