As far as i know this problem occurs when the file being deployed is not been included in package or soincides with the orgiginal file being deployed with VB setup.
So one way to avoid would be first determine whether it is included in Package or not?
Whatevre the ans comes then take reverse action i.e either remove it from package or add it to package?
Cheers.
Naresh Rohra.