Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 131513 - Sylpheed-Claws 2.2.0 released
Summary: Sylpheed-Claws 2.2.0 released
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All All
: Normal enhancement (vote)
Assignee: Marius Mauch (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-04-27 14:22 UTC by timbrain
Modified: 2006-05-22 11:07 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description timbrain 2006-04-27 14:22:03 UTC
SC 2.2.0 announced to be released on Monday May 8th.
Release candidate available at http://claws.sylpheed.org/cvs.php.
Comment 1 Jakub Moc (RETIRED) gentoo-dev 2006-04-27 14:30:08 UTC
So, reopen once there's some release at least... 
Comment 2 timbrain 2006-04-28 07:43:18 UTC
Sorry...
There were times RC were in portage too....
Comment 3 timbrain 2006-05-08 09:59:31 UTC
It's out:
http://sourceforge.net/project/showfiles.php?group_id=25528
Comment 4 ronmon 2006-05-10 12:57:38 UTC
Yes, it's out and it builds and works fine. However, there is a little catch.

Something in the 2.1.1 ebuild was broken. Claws would open, mail would be received, and then it would hang with the receive dialogue window open. CPU usage would max out and memory use would slowly increase until it was maxed out too.

First, I thought it was 2.1.1, so I waited for 2.2.0 to upgrade from 2.0.0. I renamed the 2.1.1 ebuild and found the same problem. So I used the 2.0.0 ebuild, added the startup-notification stuff, and voila! It works fine.
Comment 5 timbrain 2006-05-11 00:47:43 UTC
Report it to developers ;)
http://www.thewildbeast.co.uk/sylpheed-claws/bugzilla/
Comment 6 Marius Mauch (RETIRED) gentoo-dev 2006-05-11 07:16:30 UTC
in CVS
Comment 7 ronmon 2006-05-22 11:07:36 UTC
The problem did, in fact, persist. It took me a while to pinpoint the problem, and I sent a report to the mailing list this morning along with links to plenty of debugging info. Amazingly, Colin Leroy (the main developer), contacted me directly less than an hour later. He wanted to see my matcherrc file, which I provided, and within another 30 minutes or so he sent me a patch to test. 

It turns out that he had rewritten some of the filter stuff, which broke some of my filter rules that had multiple actions. Anyway, the patch, applied to 2.3.0-rc3, fixed it.