Bugzilla Bug 223703

net-wireless/kdebluetooth-1.0_beta1-r2 fails to emerge

Reproducible: Always

Steps to Reproduce:
1.emerge net-wireless/kdebluetooth-1.0_beta1-r2

Actual Results:  
sdprecord.h:56: error: expected ‘;’ before ‘*’ token
sdprecord.cpp: In constructor ‘Bluetooth::SdpRecord::SdpRecord()’:
sdprecord.cpp:39: error: ‘m_sdpSession’ was not declared in this scope
sdprecord.cpp: In member function ‘void Bluetooth::SdpRecord::clear()’:
sdprecord.cpp:83: error: ‘m_sdpSession’ was not declared in this scope
sdprecord.cpp: In member function ‘bool
Bluetooth::SdpRecord::sdpRegister()’:
sdprecord.cpp:352: error: ‘m_sdpSession’ was not declared in this scope
sdprecord.cpp: In member function ‘void
Bluetooth::SdpRecord::sdpUnregister()’:
sdprecord.cpp:382: error: ‘m_sdpSession’ was not declared in this scope
sdprecord.cpp:387: error: ‘m_sdpSession’ was not declared in this scope
make[5]: *** [sdprecord.o] Error 1
make[5]: *** Waiting for unfinished jobs....
sdprecord.h:56: error: ISO C++ forbids declaration of ‘sdp_session_t’ with
no type
sdprecord.h:56: error: expected ‘;’ before ‘*’ token
make[5]: *** [rfcommportlistener.o] Error 1
make[5]: Leaving directory
`/var/tmp/portage/net-wireless/kdebluetooth-1.0_beta1-r2/work/kdebluetooth-1.0_beta1/kdebluetooth/kbluetoothd/kbluetoothd'
make[4]: *** [all-recursive] Error 1
make[4]: Leaving directory
`/var/tmp/portage/net-wireless/kdebluetooth-1.0_beta1-r2/work/kdebluetooth-1.0_beta1/kdebluetooth/kbluetoothd/kbluetoothd'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory
`/var/tmp/portage/net-wireless/kdebluetooth-1.0_beta1-r2/work/kdebluetooth-1.0_beta1/kdebluetooth/kbluetoothd'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory
`/var/tmp/portage/net-wireless/kdebluetooth-1.0_beta1-r2/work/kdebluetooth-1.0_beta1/kdebluetooth'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory
`/var/tmp/portage/net-wireless/kdebluetooth-1.0_beta1-r2/work/kdebluetooth-1.0_beta1'
make: *** [all] Error 2
 *
 * ERROR: net-wireless/kdebluetooth-1.0_beta1-r2 failed.
 * Call stack:
 *               ebuild.sh, line   49:  Called src_compile
 *             environment, line 4123:  Called kde_src_compile
 *             environment, line 2945:  Called kde_src_compile 'src_compile'
 *             environment, line 3065:  Called kde_src_compile 'src_compile'
'all' 'myconf'
 *             environment, line 3061:  Called die
 * The specific snippet of code:
 *                   emake || die "died running emake, $FUNCNAME:make"
 *  The die message:
 *   died running emake, kde_src_compile:make
 *
 * If you need support, post the topmost build error, and the call stack if
relevant.
 * A complete build log is located at
'/var/tmp/portage/net-wireless/kdebluetooth-1.0_beta1-r2/temp/build.log'.
 * The ebuild environment file is located at
'/var/tmp/portage/net-wireless/kdebluetooth-1.0_beta1-r2/temp/environment'.
 *

Please, be so kind to attach your `emerge --info`.

Created an attachment (id=154395) [details]
emerge --info

I did now :)

Hope it can help :)

Can you reproduce the bug with net-wireless/kdebluetooth-1.0_beta8 ?

No 

net-wireless/kdebluetooth-1.0_beta8  works fine :)

Then let's simply stabilize it.

And remove the broken one from the portage ;)

Problem still exists. 

emerge --oneshot =net-wireless/kdebluetooth-1.0_beta8 works fine,
net-wireless/kdebluetooth-1.0_beta1-r2 don't works.

It should be removed, or fixed.

Thanks

I came over the problem today, too. Please remove the broken one.

(In reply to comment #8)
> I came over the problem today, too. Please remove the broken one.
> 

Guys, what is it that you do not understand? Blame the x86 arch team if you
want. Unless they stabilize a newer version, I am not dropping the broken one.

(In reply to comment #9)
> Guys, what is it that you do not understand? Blame the x86 arch team if you
> want. Unless they stabilize a newer version, I am not dropping the broken one.
Sorry, but I didn't understand that from reading the previous comments. Thanks
for the clarification.

I dropped the ebuild anyway. It makes no sense to have a broken ebuild in the
tree. I also pushed the herds to stabilize the latest ebuilds at once.