After upgrading to Mac Os X 10.6, I've noticed that offlineimap was crashing with a tracetrap with python 2.6 on the new Mac Os X. Aparrently (according to: http://pogma.com/2009/09/09/snow-leopard-and-offlineimap/) this is related to _locale.so being loaded not in the main thread but in a spun-off thread and is easily fixed by patching offlineimap to 'import locale from *'. Maybe it'd be a good Idea to patch offlineimap in gentoo prefix until this issue is resolved upstream ? I'll append the patch for net-mail/offlineimap-6.2.0 Reproducible: Always
Created attachment 204045 [details, diff] PATCH for net-mail/offlineimap-6.2
what version of python are you using exactly?
python 2.6.2 (according to python --version ) dev-lang/python 2.6.2-r01.3(2.6)(12:22:25 09/14/2009)(aqua ipv6 ncurses readline ssl threads xml -berkdb -build -doc -elibc_uclibc -examples -gdbm -sqlite -tk -ucs2 -wininst) (according to eix ) sorry, forgot to include those in the report.
ok, I see, python 2.4, 2.5 and 2.6 are on my system all linked against CoreFoundation
I'm using the standard ones you've get pushed via the gentoo emerge... not sure if those are linked against CoreFoundation, but the problem rather seems to be with code initialisation (which needs to be done before threading) for CoreFoundation rather than a pure linker issue (everything builds fine and as long as the thing does not start threading it does not crash as well).
sorry to say, but that's one crappy patch; you didn't patch in the source tree it seems.
Yeah, sorry for that. I didn't exactly have the time nor possibility to get the sources and patch against them from here. Rather I just included the patch just for the Reason someone might be able to easier understand how to circumvent the problem. I can attach a 'real' patch for you in the evening, but got no access to the sources from work (bandwidth limitations).
If you can come up with a patch, I'm happy to apply it.
Created attachment 207612 [details, diff] patched offlineimap-6.2.0.ebuild including proposed patch by submitter
Added patched ebuild, including patch proposed by submitter. Can someone comment on the preferred way to apply only on osx 10.6 ?
(In reply to comment #10) > Added patched ebuild, including patch proposed by submitter. > Can someone comment on the preferred way to apply only on osx 10.6 ? > The preferred way is to not have conditional patches. If you have to, do a CHOST check for *darwin* or so. You can find examples of this by grepping the portage tree, or use qgrep from portage-utils.
it's python, but it looks to me that patch is going to hurt noone, so it can just be applied unconditionally.
hmmmm, I had this patch laying around in my tree but never committed it. Did that now.