-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to solve "Referenced pack 'XXX' was found in multiple locations"? #16082
Comments
You don't necessarily have to remove the old directory, but you do need to ensure that the environment variables and configurations point to the correct locations for the new version. you just need to make sure that all environment variables related to CodeQL (such as PATH) are pointing to the directory of the new version (v2.16.6). |
@Malikrehman00107 I just made a trick to solve this problem by changing the priority of my old CodeQL's folder, then running
Once I want to switch to my old CodeQL, run the following commands let me run codeql-v2.15.3.
|
Great ! 👍 |
If I recall correctly CodeQL looks for query packs in its "sibling" folders. I think organizing your folders like the following should work
You can also download CodeQL CLI versions without bundled queries. They can be downloaded directly from https://github.com/github/codeql-cli-binaries/releases , but I'd recommend the |
I was using codeql-v2.15.3, and I hope to test the latest version (v2.16.6). After downloading the latest bundle and decompressing it, I moved the new version to a new directory. The folder looks like
Then I changed the
PATH
from using the directory of v2.15.3 to v2.16.6, and runningcodeql --version
looks good (see below).Next, I tried to use the new
codeql
with new queries and got the following errors.Changing the folder of
codeql-v2.15.3
to other folders likeabcd
does not help. Does it mean I have to remove the old directory?Is there any way to switch the used version without removing the old one?
Thank you in advance.
The text was updated successfully, but these errors were encountered: