Jump to content

Issue with VIPM and System Packages


Recommended Posts

I am using the newest version (2020.1) of VIPM, but I had this same issue with the release of 2020.

For two of the packages that I have created for internal repos, VIPM has decided that I need a System Package.   The posts I have seem from JKI indicate that this is a sub-package that is used internally to the main package, and should be automatically included.

However, after I am seeing issues on any PC other than the PC where the package was built.

Is there a setting I am missing?

 

Showing the (System) package as a dependency:

image.png.c0fcf17e4067f65a12e06e85465338cb.png

 

Package Configuration in the VI Package Configuration Editor

 

image.png.8a25bf9fb49f2d7337ade13159ecf523.png

 

Package installed, on the PC where the package was initially created (no issues, no exclamation mark)

 

image.png.49483023edfd895c11ad0fbf52721f84.png

 

image.png.b649d164360dd0daab52e86b345e6fcd.png

 

Package when installed on another PC (NOTICE: the System Package name has changed and there is a red exclamation mark, but there are no errors shown on install of the package).

image.png.a360dc8d4a84e10fb4132e13ed44c4f2.png

 

image.png.89831b7ef1d2a72d7c32b162659f647b.png

image.png

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

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