FS#6347 - gaim 2.0.0b6 broken

Attached to Project: Arch Linux
Opened by david cheung (scruffidog) - Monday, 05 February 2007, 21:08 GMT
Last edited by Jan de Groot (JGC) - Wednesday, 02 May 2007, 18:07 GMT
Task Type Bug Report
Category Packages: Current
Status Closed
Assigned To arjan timmerman (blaasvis)
Architecture not specified
Severity Medium
Priority Normal
Reported Version 0.7.2 Gimmick
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

gaim is now highly broken:

with multiple services, a restart prevents the gui from coming up after logging in. this seems to be affecting icq and msn accounts in general. this only goes away once the ~/.gaim is removed.

also with icq, buddy list management is impacted as bogus errors about maximum users reached (14 buddies).
This task depends upon

Closed by  Jan de Groot (JGC)
Wednesday, 02 May 2007, 18:07 GMT
Reason for closing:  Fixed
Additional comments about closing:  Updated to pidgin 2.0.0b7, assuming these issues are fixed (and new ones will come up :()
Comment by Marcel (ferkulat) - Wednesday, 14 March 2007, 21:31 GMT
In general I appreciate the "being up-to-date" of Arch.

gaim 2.0xxbeta went to current, but gaim-1.5.0-5 worked for me without any limitaion and I had no reason to upgrade.
I said to myself: "Ok they will have some strong reason to put beta in current" and synced.

I can confirm the problem with the reached maximum users.
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, when it breaks basic funktionality?


Comment by Jan de Groot (JGC) - Wednesday, 14 March 2007, 22:21 GMT
The problem with GAIM is that their development is a big mess. Moving from 1.5 to 2.0beta was needed because of all the broken things in 1.5. Looking at Redhat when they did the same move: their CVS repo went from something like 50-75 patches to close to zero when they moved. As beta3 worked fine for me, I upgraded to that version and applied a minimal amount of patches.
After a while, beta4 (flaky) and beta5 came out. I got a bug report that beta3 was outdated and upgraded it to beta6 then. Beta6 worked fine for me, as I "only" use MSN, Jabber (2-3 accounts) and ICQ without any problems (though MSN pops up with authentication error, but shows my contact list fine nowadays)
Comment by Marcel (ferkulat) - Thursday, 15 March 2007, 13:50 GMT
@Jan
If i read your answer I could get the impression You are the maitainer of gaim.
Are you?
In case "YES":
For you and maybe for some others gaim 2.0b works.
For others not, but 1.5 worked.
Was the wild patching for building process the only reason to use Beta?

From my position as user, I dont care how much patches are neccessary to get it working the right way.
If it works, I am happy.

Now this bug report shows that it doesnt work like it should.
Could it be a solution to shift gaim Beta to unstable and put 1.5 back in current, and let the users decide which is the best for them?

greets

ferkulat
Comment by Jan de Groot (JGC) - Thursday, 15 March 2007, 13:57 GMT
Switching back to 1.5 and applying 100 patches from which I don't know what they do exactly is not an option. Switching back to 2.0 beta5 and applying a small bit of patches which fixes problems fixed in beta6 is an option though. Debian is taking this approach also, we could use their patches, which have a clear description about what they fix. Beta5 doesn't have the regressions we've seen with beta6.
Comment by Marcel (ferkulat) - Sunday, 18 March 2007, 21:28 GMT
ahhh I see.
Ok if switching back to beta5 would fix the bug with the contact list it would be nice.
Like i said : whatever you do, if it works like expected I am happy :)

greets

ferkulat

Loading...