Next time you're out in the stable putting the baby in the manger, please remember to stable net-im/bitlbee-1.0.1 for the night as well. Thank you, please drive your horse and buggy through.
I've been using the bee-1.0.1 for my daily icq/aim/messenger business ever since it came out. Should be fine on ppc.
alpha stable. A note on testing for those who don't have a lot of experience with bitlbee... when you add a jabber account, you need to use the full user name (username@example.org, not just username). Example "account add jabber username@example.org password example.org"
amd64 stable (keywording amd64 with permission from KingTaco, I'm be officially joining amd64 soon).
Having run this on an ~x86 for three months, and a few hours in an x86 chroot (using all supported protocols), and I'm pretty confident that it's ok to mark it stable on x86. The only thing I haven't been able to test is the ssl/tls stuff - all I can really say about that is that having it enabled doesn't break anything else.
x86 looks good X_X zzz sleepy tsunam
ppc stable
i just had a talk with the bitlebee devs. it seems like a lot of ppl miss the msn (gnutls | openssl) dependency warning (me including). Could this be checked and error'd if not complete ? I added this too the stable ticket since it seems like a minor check. Hope its ok! thx!
All stable, closing bug
Not sure why someone felt this needed closing when there is still something to be done.
Removing ia64 as we're already stable and closing bug.
