Bug 449563 - FTBFS taglib-sharp-2.0.3.0-4.fc10
FTBFS taglib-sharp-2.0.3.0-4.fc10
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: taglib-sharp (Show other bugs)
rawhide
All Linux
high Severity high
: ---
: ---
Assigned To: Tom "spot" Callaway
Fedora Extras Quality Assurance
http://linux.dell.com/files/fedora/Fi...
:
Depends On:
Blocks: FTBFS
  Show dependency treegraph
 
Reported: 2008-06-02 16:49 EDT by FTBFS
Modified: 2008-06-05 15:42 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-06-05 15:42:19 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
root.log.bz2 (1.64 KB, application/x-bzip2)
2008-06-02 16:50 EDT, FTBFS
no flags Details
build.log.bz2 (446 bytes, application/x-bzip2)
2008-06-02 16:50 EDT, FTBFS
no flags Details
root.log.bz2 (21.07 KB, application/x-bzip2)
2008-06-02 16:50 EDT, FTBFS
no flags Details
build.log.bz2 (450 bytes, application/x-bzip2)
2008-06-02 16:50 EDT, FTBFS
no flags Details

  None (edit)
Description FTBFS 2008-06-02 16:49:45 EDT
taglib-sharp-2.0.3.0-4.fc10.src.rpm Failed To Build From Source against the rawhide tree.  See http://fedoraproject.org/wiki/FTBFS for more information.
Comment 1 FTBFS 2008-06-02 16:50:09 EDT
Created attachment 307855 [details]
root.log.bz2

root.log for i386
Comment 2 FTBFS 2008-06-02 16:50:20 EDT
Created attachment 307856 [details]
build.log.bz2

build.log for i386
Comment 3 FTBFS 2008-06-02 16:50:29 EDT
Created attachment 307857 [details]
root.log.bz2

root.log for x86_64
Comment 4 FTBFS 2008-06-02 16:50:41 EDT
Created attachment 307858 [details]
build.log.bz2

build.log for x86_64
Comment 5 Tom "spot" Callaway 2008-06-05 15:42:19 EDT
Combination of mono dependencies in flux and new doc behavior. All fixed now in
rawhide.

http://koji.fedoraproject.org/koji/buildinfo?buildID=51798

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