Comment 6 for bug 549696

(Oh, and the whole not-fix-things-mid-cycle is only policy. This guy clearly reported the bug before the final version was out and about. Be humble enough to recognize that where a grave mistake was made, an exception which can retroactively fix this mistake should be made. Other than sticking to whats always been done, what logical reason is there for *not* fixing this extreme case of dependency failure? I think its time to break out of the mold for a minute.)