Bug 449416 - FTBFS gpgme-1.1.6-3.fc9
Summary: FTBFS gpgme-1.1.6-3.fc9
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: gpgme
Version: rawhide
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Rex Dieter
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-06-02 16:38 UTC by FTBFS
Modified: 2008-07-22 13:52 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2008-07-22 13:52:51 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
root.log.bz2 (2.30 KB, application/x-bzip2)
2008-06-02 16:38 UTC, FTBFS 		no flags Details
build.log.bz2 (7.63 KB, application/x-bzip2)
2008-06-02 16:39 UTC, FTBFS 		no flags Details
root.log.bz2 (6.19 KB, application/x-bzip2)
2008-06-02 16:39 UTC, FTBFS 		no flags Details
build.log.bz2 (7.71 KB, application/x-bzip2)
2008-06-02 16:39 UTC, FTBFS 		no flags Details
View All

Description FTBFS 2008-06-02 16:38:31 UTC 
gpgme-1.1.6-3.fc9.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:38:51 UTC 
Created attachment 307427 [details]
root.log.bz2

root.log for i386
Comment 2 FTBFS 2008-06-02 16:39:03 UTC 
Created attachment 307428 [details]
build.log.bz2

build.log for i386
Comment 3 FTBFS 2008-06-02 16:39:09 UTC 
Created attachment 307429 [details]
root.log.bz2

root.log for x86_64
Comment 4 FTBFS 2008-06-02 16:39:16 UTC 
Created attachment 307430 [details]
build.log.bz2

build.log for x86_64
Comment 5 Kevin Kofler 2008-07-19 23:16:45 UTC 
/var/tmp/rpm-tmp.79655: line 26: syntax error near unexpected token `||'

Bad scriptlet, maybe caused by the new RPM?
Comment 6 Rex Dieter 2008-07-22 13:52:51 UTC 
fixed in rawhide.

fwiw, new rpm chokes on this:
%check || :
which was only there to provide compatibility with *old* versions of rpm that
didn't support %check sections.
Note You need to log in before you can comment on or make changes to this bug.