TonP Posted November 27, 2012 Report Share Posted November 27, 2012 I have a weird situation where VIPM isn't showing a package is installed. However when I install the package I get the following error: Stating that the package is allread installed. Trying to install an older version fails as well. Is there some way to update my database? Ton Link to comment Share on other sites More sharing options...
Ashish Posted November 27, 2012 Report Share Posted November 27, 2012 TonP, Can you try "Remove all versions from library..." and try to install the package again? If that does not work, can you share the package so that I can give it a try on my PC? For some reason, I am not able to download the package from LAVA website. http://lavag.org/files/file/206-mercurial-provider/ Link to comment Share on other sites More sharing options...
JLMommy Posted December 7, 2012 Report Share Posted December 7, 2012 I've seen the exact same thing on my computer relating to packages on an internal repository. Steps to recreate: 1. Build a package locally (test_1.0.0.1.vip) - do not publish package at end of build when prompted 2. Install local package (test_1.0.0.1.vip) 3. Update and rebuild package (test_1.0.0.2.vip) - publish package at end of build when prompted 4. VIPM will now show that the package is not installed and will give the exact error Ton mentions The original package still shows up on the palettes. If I manually remove the files installed with the original package, VIPM returns the same error. "Remove this version" and "Remove all versions" are disabled and not an option. The workaround I found is to manually browse to our repository file server and open the *.vip file and install from there. The main VIPM window will update to reflect that the package is now installed. - Becky Link to comment Share on other sites More sharing options...
Ashish Posted December 10, 2012 Report Share Posted December 10, 2012 Becky, Using VIPM 2012.0.1 (build 1818), I was not able to recreate the behavior described by you. Here is how I tested it: 1. Build package. Do not publish. 2. Install the package 3. Update and build package. Publish the package. 4. Refresh repository to check for new packages. This shows that the new version of the installed package (in step 2) is available 5. Install the upgrade Any more details to recreate the behavior will be helpful. Link to comment Share on other sites More sharing options...
yuchia Posted January 29, 2013 Report Share Posted January 29, 2013 I'm having exactly the same problem. Normally it should show an upgrade option, but only install is there. But it won't let me to install over the old version. Is there anything I can update the package? Thanks, Joseph Becky, Using VIPM 2012.0.1 (build 1818), I was not able to recreate the behavior described by you. Here is how I tested it: 1. Build package. Do not publish. 2. Install the package 3. Update and build package. Publish the package. 4. Refresh repository to check for new packages. This shows that the new version of the installed package (in step 2) is available 5. Install the upgrade Any more details to recreate the behavior will be helpful. Link to comment Share on other sites More sharing options...
Michael Aivaliotis Posted February 6, 2013 Report Share Posted February 6, 2013 I'm having exactly the same problem. Normally it should show an upgrade option, but only install is there. But it won't let me to install over the old version. Is there anything I can update the package? Thanks, Joseph Please indicate which package you are trying to upgrade, which LV version you are trying to install to and what version of VIPM you are using. Link to comment Share on other sites More sharing options...
yuchia Posted February 6, 2013 Report Share Posted February 6, 2013 I'm using Labview 2011 SP1. The package I'm trying to install is an internal library I wrote. The VIPM version is 2012.0.1 (build 1818). After I built the package and opened in VIPM, it used to show "Upgrade" instead of "Install". But it didn't for this package. When I clicked install button, it didn't allow me to install. (see the screenshot). I tried to open the package file by double clicking it, but the result is still the same. Thanks, Joseph Link to comment Share on other sites More sharing options...
Michael Aivaliotis Posted February 7, 2013 Report Share Posted February 7, 2013 Please try re-downloading VIPM and re-installing it. Link to comment Share on other sites More sharing options...
yuchia Posted February 7, 2013 Report Share Posted February 7, 2013 It is working now after re-installed VIPM. Thank you very much, Joseph Please try re-downloading VIPM and re-installing it. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.