The bug is still there using version 1.28.2 now ... in fact there are forum discussions and bug reports all over the internet about this problem for years now. Could we at least get a statement from the maintainers whether this will ever get fixed or is there some policy we could implement to allow this. SOME information would really help to figure out where this is going.

Reply via email to