kbluetooth-0.4.2-1.fc14.src.rpm Failed To Build From Source against the rawhide tree. See http://fedoraproject.org/wiki/FTBFS for more information.
If you believe this is actually a bug in another package, do NOT change the component in this bug or close this bug. Instead, add the appropriate bug number from the other package to the "Depends on" line in this bug. If the other package does not yet have a bug created that you think matches, please create one. Doing so helps us properly track bugs and their dependencies, just as we track package dependencies. (If you close this bug, and the other package is not fixed before the next FTBFS run, a new bug will get created. Please follow the above advice to avoid such duplication.)
Created attachment 420489 [details]
root.log for i386
Created attachment 420490 [details]
build.log for i386
Created attachment 420491 [details]
mock.log for i386
Created attachment 420492 [details]
root.log for x86_64
Created attachment 420493 [details]
build.log for x86_64
Created attachment 420494 [details]
mock.log for x86_64
This bug appears to have been reported against 'rawhide' during the Fedora 14 development cycle.
Changing version to '14'.
More information and reason for this action is here:
0.4.2-1.fc14 is correctly built - http://koji.fedoraproject.org/koji/buildinfo?buildID=157921. Closing.
That was on February 22. It didn't build anymore as of June 3. This must be fixed.
Kevin, thanks for catch, I'm fixing it right now.
kbluetooth-0.4.2-2.fc14 has been submitted as an update for Fedora 14.
kbluetooth-0.4.2-2.fc14 has been pushed to the Fedora 14 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update kbluetooth'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/kbluetooth-0.4.2-2.fc14
kbluetooth-0.4.2-2.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.