Can't re-install module when new path detected #1185
isc-bsherman
started this conversation in
General
Replies: 2 comments
-
|
You can delete the repo and recreate it or force update the cache using zpm "repo -n -p4 -force" (HS internal command when using the p4 extension) |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I was able to do a minimally invasive (but unsupported) tweak with SQL, like so: update %IPM_Repo_Filesystem.Cache |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I have a module which has been relocated to a new folder due to having been created with an irregular path, which has been corrected. IPM remembers the original location, which no longer exists, and encounters the new path.
I have un-installed the module, but if I attempt to re-install with -dev and -p specified, I still get this:
WARNING: healthshare.hp.utils.pastransformation 1.0.0+snapshot previously found in //projects/healthshare/appmodules/CMS-0057-WIP/HealthShare.HP.Utils.PASTransformation/; also found in //projects/healthshare/appmodules/CMS-0057-WIP/HealthShare.HP.Utils.PASTransformation/latest/. The version in //projects/healthshare/appmodules/CMS-0057-WIP/HealthShare.HP.Utils.PASTransformation/ will be used.
The prompt/p flag's help text says "Prompts user which version to install, if more then (sic) one found." Apparently that applies to new versions but not locations. How can I tell it to use the new path? Do I have to manually locate the cached path information in the globals and delete?
Beta Was this translation helpful? Give feedback.
All reactions