>
> Notice the build date?  If his report was made *after* June the 3rd,
> then it is obvious why it's not fixed in this package.
>

Still, you could refrain from public release of a build that is *known* to
be broken. -3mdk appeared on mirrors just yesterday and not June the 4th. It
is different from -2mdk problem where first reports happened after it was
released.

-andrej


Reply via email to