that bug is a well known nightmare which is/was pretty much unaddressable, as it depends on some lacking upstream features. Many other people had a look at it without success, and the fact I am the assignee doesn't prevent anyone from fixing or acting on it. Feel free to change the assignee if anybody is willing to take the burden, though.
Thanks for the info, so are we waiting for something from upstream or what?
P.S.: It is good practice to avoid name-calling on a public list, I'd appreciate if you could avoid this next time. Thanks
Really sorry about that, I respect and appreciate all the work all of you do for the rest of us, thank you.