It isn't fixed in rc2. You only posted that analysis 2 days before the rc2 release, and the tarball had already been cut at the time you posted the message. (It takes a day or two between release cutoff and the release showing up, since it needs to be tested before the announcement.)
Furthermore, you only posted the notice here in the users group where it could easily be missed by the SA devs. The proper thing to do is open a bug in Bugzilla on this subject, and include the info that you posted here. FWIW, the change that is causing the problems was a deliberate change to work around another problem in another tool. So the fix isn't likely to be as simple as backing out that change, since that would just bring the previous bug back. Loren