Comment 17 for bug 160683

Revision history for this message
Cliff Cunnington (cc-ububug) wrote :

> what if vmware server 1.0.3-2 actually does get released?

The Nov6 VMWare package release that triggered this bug should have been called 1.0.3-2, so we are really just giving it its proper version number.

If there is another 1.0.3 release (to close this bug!), hopefully the VMWare Build Team will be considerate enough to call it 1.0.3-3 so it will trigger a proper update for users with and without this workaround.