Jump to content
Sign in to follow this  
RocketHacker

fails to recognize incompatible packages

Recommended Posts

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.

 

post-9114-0-51148200-1464721420_thumb.png

Edited by RocketHacker

Share this post


Link to post
Share on other sites

I have a very similar but slightly different issue, though it's likely related. Although I am installing to LV 2012, VIPM 2106 is allowing the installation of packages that are restricted to higher versions of LabVIEW. For example, VIPM shows an upgrade available to JKI State Machine Toolkit 3.0 even though that is restricted to LV>=2013. It installs, but then is broken because the VIs cannot be opened.

 

post-336-0-02244100-1466723862_thumb.png

Share this post


Link to post
Share on other sites

I am also noticing the same issue reported by Greg sands. It appears to be a general issue that the Compatible LabVIEW Version is being ignored. I'm seeing this in 2016.0.0 (build 1986). Is this a known issue at this point?

 

-Matt

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×

Important Information

By using this site, you agree to our Terms of Use.