Bug 440790 - FTBFS pyzor-0.4.0-11.fc7
Summary: FTBFS pyzor-0.4.0-11.fc7
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: pyzor
Version: 9
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Andreas Thienemann
QA Contact: Fedora Extras Quality Assurance
URL: http://linux.dell.com/files/fedora/Fi...
Whiteboard:
Depends On:
Blocks: FTBFS
TreeView+ depends on / blocked
 
Reported: 2008-04-04 15:59 UTC by FTBFS
Modified: 2008-08-14 16:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-08-14 16:37:23 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
root.log.bz2 (1.56 KB, application/x-bzip2)
2008-04-04 15:59 UTC, FTBFS 		no flags Details
build.log.bz2 (719 bytes, application/x-bzip2)
2008-04-04 15:59 UTC, FTBFS 		no flags Details
root.log.bz2 (1.57 KB, application/x-bzip2)
2008-04-04 15:59 UTC, FTBFS 		no flags Details
build.log.bz2 (721 bytes, application/x-bzip2)
2008-04-04 15:59 UTC, FTBFS 		no flags Details
View All

Description FTBFS 2008-04-04 15:59:50 UTC 
pyzor-0.4.0-11.fc7.src.rpm Failed To Build From Source
Comment 1 FTBFS 2008-04-04 15:59:54 UTC 
Created attachment 300750 [details]
root.log.bz2

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

build.log for i386
Comment 3 FTBFS 2008-04-04 15:59:57 UTC 
Created attachment 300752 [details]
root.log.bz2

root.log for x86_64
Comment 4 FTBFS 2008-04-04 15:59:58 UTC 
Created attachment 300753 [details]
build.log.bz2

build.log for x86_64
Comment 5 Bug Zapper 2008-05-14 08:45:07 UTC 
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Comment 6 Jason Tibbitts 2008-08-14 16:37:23 UTC 
I'm not the maintainer, but I was fixing up the bogus license tag and went ahead and fixed the failing build as well.  Should be built for rawhide as soon as koji is back up.
Note You need to log in before you can comment on or make changes to this bug.