You are not logged in.
In general I appreciate the "being up-to-date" of Arch.
Gaim-1.5.0-5 worked for me without any limitation and I had no reason to upgrade.
Some day gaim 2.0xxbeta went to current and
I said to myself: "Ok they will have some strong reason to put beta in current" and synced.
Since then I have a problem with the reached maximum of users in the contact list.
It is even a known bug in the bug tracker of gaim.sourceforge.net: [ 1675294 ] Unable To Add for an unknown reason
After a downgrade to version 1.5.0-5 the problem disappered.
This leads me to a general question:
Should Beta Software be put to current without any strong reason?
Especially if it breaks basic funktionality, just to be up-to-date?
For me being up-to-date, means "Having the last STABLE version" unless there is a really good reason to upgrade with beta.
greets
ferkulat
Last edited by ferkulat (2007-03-14 21:54:12)
Offline
I have to agree with you, I've never understand why the betas are in current. It definitely isn't "stable", which is the whole reason why packages like fvwm-devel are in unstable.
I am a gated community.
Offline
I have the same problem here.
Interestingly it worked a while. But after I logged in to my ICQ account from a slackware machine with gaim 1.5 and authorised a buddy, I now get the same error as ferkulat.
I would also like to see the gaim-beta in unstable. Then everyone can decide, if he wants to use latest stable or latest dev.
Offline