Refine get_purldb_entries to compare on plain PURL #307 #308
Conversation
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
Including the qualifiers and subpaths in the comparison is too restrictive. Signed-off-by: tdruez <[email protected]>
Signed-off-by: tdruez <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The recent changes included in #304 were a bit too restrictive in the PURL comparison.
This PR exclude the PURL
qualifiersandsubpathsfor the PURL comparison when matching data returned by the PURLDB.For example, if the provided PURL is
pkg:pypi/[email protected], the following PURL returned by the PURLDB are kept as relevant packages:pkg:pypi/[email protected]?file_name=boto3-1.37.26-py3-none-any.whlpkg:pypi/[email protected]?file_name=boto3-1.37.26.tar.gz