I've built a custom package and set it as incompatible with a 3rd party package. VIPM doesn't recognize the conflict on installation of my package, but acknowledges the conflict via icon after the install. clicking the icon and selecting "Install missing dependencies" just gives a dialog saying "There is nothing to do. All the packages are already installed". If I were not he original author of my package i would be very confused what was going on here...
running VIPM 2016.0.0.1986
Of course the manual workaround is to manual uninstall the conflicting package, but i'm trying to get a solution that automatically does this. just looking to file this as a bug report.
Edited by RocketHacker, 31 May 2016 - 07:38 PM.