Bug#682736: unblock: vmware-manager/0.2.0-2

["Adam D. Barratt" <adam@adam-barratt.org.uk>]

On Mon, 2012-08-13 at 15:38 +1000, Alexander Zangerl wrote:
> sorry for the late response: after digging through this a few more times
> i've got an explanation for the debdiff output.
[...]
> the problem is that the debian diff doesn't represent file deletions,
> and that i rather should have left the vmm filename intact and just 
> installed it with its new name via debian/rules (hindsight and all that).
> 
> net effect: a newly unpacked 0.2.0-2 includes the correct vwm file,
> but also a superfluous and unused vmm file from the orig tarball, 
> which of course reflects only the state before the -1 changes were made.

Okay.  Assuming an upload could be made fairly quickly, I think I'd
prefer a -3 which made the POD changes to the original binary and
installed it under the new name.  Thanks for working on this.

Regards,

Adam