Skip to content
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

Dependency mismatch corrections #118

Conversation

tgonzalezorlandoarm
Copy link
Member

When transferring the changes to Parsec as indicated in #116 , some issues were spotted. Correct those issues.

The symmetric difference between versions of parsec and parsec-tool
is computed using sets. The exception list has a specific order, so
when checking whether the version differences between parsec and
parsec-tool are allowed (are in the same as the ones in the
exception list), this may appear to not be allowed.

 * Sort the exception lists and the list obtained from calculating
   the symmetric difference so that the comparison between them can
   be performed without ordering issues.

Signed-off-by: Tomás González <[email protected]>
Dependencies that have more than one version should be checked for
the case where only parsec-tool repo itself is being analyzed.
For comparing between two repositories, we should be checking any
mismatch between the two.

Signed-off-by: Tomás González <[email protected]>
 * Correct an obvious mistake on the parsec flags for cargo tree.
 * Change the exception list accordingly

Signed-off-by: Tomás González <[email protected]>
@tgonzalezorlandoarm tgonzalezorlandoarm added the bug Something isn't working label Nov 28, 2023
@tgonzalezorlandoarm tgonzalezorlandoarm self-assigned this Nov 28, 2023
@tgonzalezorlandoarm
Copy link
Member Author

tgonzalezorlandoarm commented Nov 28, 2023

@tgonzalezorlandoarm tgonzalezorlandoarm deleted the tg/dependency-mismatch-corrections branch November 28, 2023 14:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant