Jump to content


fails to recognize incompatible packages

incompatible conflict conflicts

  • Please log in to reply
2 replies to this topic

#1 RocketHacker

  • Members
  • 19 posts
  • Gender:Male

Posted 31 May 2016 - 07:00 PM

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.

  • 0

#2 Greg sands

Greg sands
  • Members
  • 9 posts

Posted 23 June 2016 - 11:18 PM

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.



  • 0

#3 Matthew Harrison

Matthew Harrison
  • Members
  • 10 posts
  • Gender:Male
  • Location:Layton, UT
  • Interests:Triathlon

Posted 25 August 2016 - 04:35 PM

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?



  • 0