Has the error in compiling the patch met with any progress? Or is it still coming back with 3.2gb, even now several weeks later? I'd imagine that progress with such an error would by now either be
A) Solved via some thorough re-checking of the submitted data.
B) Solved by a diagnostic systems and software check at the end of the platform holder.
C) Be stalled via inaction due to being busy with various projects (at either end), or the possibility of diminished priority.
It may be that there are other factors that aren't able to be, or are unwilling to be shared, I guess we can't at the consumer end know anything for sure.
From a consumer viewpoint, it's possible that just about anything could happen or anything could not happen. The patch could come out at any moment, it could come out months from now, it could just continue to be a "coming soon" assurance into the forseeable future.
Myself, I've taken the attitude that it's best to assume no progress (as there has been none to hear of) and other than the occasional check on here and Big Ant Forums, to get on with the other games around that deserve attention also.
There's been some news of the next DBC and that's great and probably best to turn my attention towards it. However, if in the future we receive the next DBC and there may be things that need patched, it might be best to learn from things and just make do with what we get and don't anticipate a patch.