For the benefit other readers with similar issues: when Stata's user-created packages start misbehaving, there are various options. Sometimes, the approach suggested by Suhail Doi in the post immediately above works; that is, to force an install of the latest package, over-writing any conflicting files. The downside is that you cannot be sure exactly which files were conflicting, which were over-written, and which are now in use by Stata.
Therefore, a more comprehensive approach would be to identify all the relevant (user-created!!) packages which are causing issues, uninstall them all (creating a backup if necessary, e.g. if the packages are no longer available for download!), and re-install one by one. Tools for helping here include:
Code:
. ado dir // list all installed packages, with internal Stata ID numbers in square brackets; optionally restrict to a particular pkgname . ado dir pkgname // same but restricted to a particular pkgname . which pkgname, all // list all file locations and versions for a particular pkgname . ado uninstall [x] // uninstall the package with internal Stata ID number [x] (including the square brackets, and where x is an integer)
I hope that helps!
David.
Leave a comment: