I am also running in YESIAMSTUPID mode! ( I think Ton got a bit nervous that time…) Actually I find it is perfectly usable already, just when you happen to open a 64bit-saved file in a 32bit blender, you get a couple of fancy things, but until now I could fix them all easily (save the file again under a new name, etc…)
From time to time they have, in some ways: he-mesh, Nurbana, Pytextures… The only thing that that prooves is their humanity, something to remember when comes the time for praise, comments or, (eeek!..) addictive requests.
That wasn’t my point: they still may fail and they still may meet greater success that ever expected. There’s likely many thing to come out of the blue that will surprise us and others that we fully expect that won’t happen. A project like Blender is a human adventure to a level like no regular business can be. That is my point.
I’m on 64 bit Feisty Fawn, and I just “apt-get install blender” to get 2.43. 2.42a is in Dapper. They’re in the universe repostories.
However, these are the “YESIAMSTUPID” versions, because 64 bit versions aren’t “safe” yet. They really should make this warning clear in the package description, because many users won’t notice the warning message if they don’t launch it from a console.
Also, IIRC, library linking was never safe between 64 and 32 bits files (this wasn’t an issue at the time since the work environment at NeoGeo was, I assume much more homogeneous than the current mix of platform and architecture).