Packaging: accept normalized Marvin archive names - #13793
Draft
Dogface2k wants to merge 1 commit into
Draft
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
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.
Summary
Setuptools 69.3.0 introduced PEP 625-compliant normalization of
source-distribution filenames.
Although the Python project is declared as
name="Marvin", currentSetuptools versions produce:
Older versions may still produce:
Update the Debian packaging consumers to match
[Mm]arvin-*.tar.gz,allowing both forms to remain supported.
This only changes archive discovery during packaging and installation.
It does not alter the Marvin archive contents or CloudStack runtime
behaviour.
still need review
packaging/el8/cloud.spec
packaging/suse15/cloud.spec
tools/marvin/pom.xml
will tighten patterns