Bug 440765 - FTBFS crystal-stacker-1.5-6.fc9
Summary: FTBFS crystal-stacker-1.5-6.fc9
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: crystal-stacker
Version: rawhide
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Hans de Goede
QA Contact: Fedora Extras Quality Assurance
URL: http://linux.dell.com/files/fedora/Fi...
Whiteboard:
Depends On: 440136
Blocks: FTBFS
TreeView+ depends on / blocked
 
Reported: 2008-04-04 15:55 UTC by FTBFS
Modified: 2008-04-28 15:22 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-04-28 15:22:57 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
root.log.bz2 (3.81 KB, application/x-bzip2)
2008-04-04 15:55 UTC, FTBFS 		no flags Details
build.log.bz2 (2.26 KB, application/x-bzip2)
2008-04-04 15:55 UTC, FTBFS 		no flags Details
root.log.bz2 (3.27 KB, application/x-bzip2)
2008-04-04 15:55 UTC, FTBFS 		no flags Details
build.log.bz2 (2.19 KB, application/x-bzip2)
2008-04-04 15:55 UTC, FTBFS 		no flags Details
View All

Description FTBFS 2008-04-04 15:55:43 UTC 
crystal-stacker-1.5-6.fc9.src.rpm Failed To Build From Source
Comment 1 FTBFS 2008-04-04 15:55:47 UTC 
Created attachment 300655 [details]
root.log.bz2

root.log for i386
Comment 2 FTBFS 2008-04-04 15:55:49 UTC 
Created attachment 300656 [details]
build.log.bz2

build.log for i386
Comment 3 FTBFS 2008-04-04 15:55:50 UTC 
Created attachment 300657 [details]
root.log.bz2

root.log for x86_64
Comment 4 FTBFS 2008-04-04 15:55:52 UTC 
Created attachment 300658 [details]
build.log.bz2

build.log for x86_64
Comment 5 Hans de Goede 2008-04-05 07:28:04 UTC 
This FTBFS is caused by a bug in ImageMagick, for which I've written a patch,
but the ImageMagick maintainer on average is anything but fast to respond to bugs :(

See bug 440136.
Comment 6 Hans de Goede 2008-04-28 15:22:57 UTC 
This is fixed by ImageMagick-6.3.8.1-4.fc9 which has been tagged for F-9 final
inclusion and thus should show up in rawhide soon.
Note You need to log in before you can comment on or make changes to this bug.