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 433963 - ksshaskpass failed massrebuild attempt for GCC 4.3
Summary: ksshaskpass failed massrebuild attempt for GCC 4.3
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: ksshaskpass
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Aurelien Bompard
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: gcc43rebuildfail
TreeView+ depends on / blocked
 
Reported: 2008-02-22 12:50 UTC by Jesse Keating
Modified: 2013-01-10 02:46 UTC (History)
2 users (show)

Fixed In Version: 0.3-5.fc9
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-03-11 21:21:15 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Jesse Keating 2008-02-22 12:50:29 UTC 
This is an automatically filed bug for a failed rebuild attempt for GCC 4.3.

http://fedoraproject.org/wiki/JesseKeating/gcc43MassRebuildProposal

Please verify why this build failed and fix it.
http://koji.fedoraproject.org/koji/taskinfo?taskID=435881
Exit code was 1, check the build.log for the failed buildArch task.
Comment 1 Jon Stanley 2008-02-22 14:11:57 UTC 
IMHO, a missing build requirement,

+ unset QTDIR
+ . /etc/profile.d/qt.sh
/var/tmp/rpm-tmp.24827: line 29: /etc/profile.d/qt.sh: No such file or directory
error: Bad exit status from /var/tmp/rpm-tmp.24827 (%build)
Comment 2 Kevin Kofler 2008-03-11 21:21:15 UTC 
The usual kdelibs-devel vs. kdelibs3-devel problem.
I made the 1-character fix in Rawhide (the CVS commit message wasn't sent due 
to FAS-related problems, you can find it on fedora-extras-commits: 
https://www.redhat.com/archives/fedora-extras-commits/2008-March/msg03533.html ) 
and it built successfully.
Note You need to log in before you can comment on or make changes to this bug.