fix(scanner): parsing apt cache policy for nvidia-container-toolkit - #1786
Merged
kotakanbe merged 2 commits intoNov 13, 2023
Merged
Conversation
kotakanbe
approved these changes
Nov 13, 2023
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What did you implement:
The repository for NVIDIA Container Toolkit has a different format for
apt-cache policy.All other packages have 5 fields separated by whitespace.
But the
nvidia-container-toolkithas 4 fields, including a blank repo (maybe)If the
nvidia-container-toolkitis installed and updatable for a new version, when you scan with fast-root mode, the following will happen:Type of change
How Has This Been Tested?
nvidia-container-toolkitwith an older versionnvidia-container-tookitis updatableChecklist:
You don't have to satisfy all of the following.
make fmtmake testIs this ready for review?: YES
Reference