Ghost package in NI Package Manager

[Sergey_Kolbunov]

I have a package from our company feed visible in NI Package Manager and it can be installed right, but it can not be found anywhere.

This package was created some time ago, and then I decided to get rid of it. That was done by using NIPM Feed Manager utility (https://github.com/allenh-ni/nipm-feed-manager-gui-labview/blob/master/README.md), package was removed from the feed. That change was verified in NI Package Manager.

Then, the system consists of the development PC where this update was done and the build PC, with the data exchange via SVN. Feed files at build PC were not updated, and when conflict was reported after the build completion, I resolved it in favor of build PC. Dev PC was updated from SVN, and I assumed that now I have this package recovered in the feed, and I need to remove it again. But it is not in the list. All the packages and Packages,Packages.gz,Packages.stamps files are in sync at dev PC, build PC, and the feed server, no .nipkg file exists anywhere for the package in question, but it is visible in the feed and installable.

What can I check else? 

[WesW]

Here's a suggestion on how to find where it's coming from and remove it:

1. Open a Windows command-prompt, and run this command
   "c:\Program Files\National Instruments\NI Package Manager\nipkg.exe" list-source-feeds packageNameOfGhost
   
2. This shows you which feeds contain this package, for example:
   
   
3. Run the following command to remove the undesired feed and update the cache:
   "c:\Program Files\National Instruments\NI Package Manager\nipkg.exe" feed-remove badFeedName
   "c:\Program Files\National Instruments\NI Package Manager\nipkg.exe" update
   

[Sergey_Kolbunov]

No success so far. When I'm sending command to list source feed, I only get this error:

Error -125104: Unable to locate one or more packages with a compatible version and architecture in the registered feeds.

Same error comes for other (existing) custom packages, so something is wrong with that. Your example with ni-metauninstaller works fine.