Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 511493 - FTBFS asterisk-sounds-core-1.4.15-1.fc11
Summary: FTBFS asterisk-sounds-core-1.4.15-1.fc11
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: asterisk-sounds-core
Version: rawhide
Hardware: i386
OS: Linux
high
high
Target Milestone: ---
Assignee: Jeffrey C. Ollie
QA Contact: Fedora Extras Quality Assurance
URL: http://linux.dell.com/files/fedora/Fi...
Whiteboard:
Depends On:
Blocks: F12FTBFS
TreeView+ depends on / blocked
 
Reported: 2009-07-15 03:06 UTC by FTBFS
Modified: 2009-07-17 16:22 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-07-17 16:22:32 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
root.log (17.38 KB, text/plain)
2009-07-15 03:06 UTC, FTBFS 		no flags Details
build.log (4.13 MB, text/plain)
2009-07-15 03:06 UTC, FTBFS 		no flags Details
mock.log (1010 bytes, text/plain)
2009-07-15 03:06 UTC, FTBFS 		no flags Details
View All

Description FTBFS 2009-07-15 03:06:22 UTC 
asterisk-sounds-core-1.4.15-1.fc11.src.rpm Failed To Build From Source against the rawhide tree.  See http://fedoraproject.org/wiki/FTBFS for more information.
Comment 1 FTBFS 2009-07-15 03:06:25 UTC 
Setting to ASSIGNED per Fedora Bug Triage workflow.  https://fedoraproject.org/wiki/BugZappers/BugStatusWorkFlow
Comment 2 FTBFS 2009-07-15 03:06:27 UTC 
Created attachment 352124 [details]
root.log

root.log for i386
Comment 3 FTBFS 2009-07-15 03:06:33 UTC 
Created attachment 352125 [details]
build.log

build.log for i386
Comment 4 FTBFS 2009-07-15 03:06:35 UTC 
Created attachment 352126 [details]
mock.log

mock.log for i386
Comment 5 Matt Domsch 2009-07-17 16:22:32 UTC 
lsThis was a build system failure, not a package bug.  I apologize.
Note You need to log in before you can comment on or make changes to this bug.