[master] Write hardcoded salt version before building when running "setup.py --with-salt-version=xxxx"#65238
Conversation
|
Be advised that we want to move away from |
Thanks for the note! 👍 |
…c#1215489) (saltstack#604) BACKPORT-UPSTREAM=saltstack#65238
2cc6113 to
ca5b37b
Compare
ca5b37b to
8cc3c0e
Compare
|
@meaksh You can set the salt version by creating |
Hey @dwoz, manually creating |
What does this PR do?
This PR fixes an issue we detected when building Salt with
setup.pyscript and making use of--with-salt-versionparameter to hardcode an specific Salt version:After running the above commands, the generated "egg-info" metadata for the built package is not reflecting the specified version but instead it is calculating it without respecting what it was provided via
--with-salt-versionparameter:Previous Behavior
As mentioned, I got a different version than the specified:
New Behavior
After this PR, I get the expected version in the generated egg-info:
Merge requirements satisfied?
[NOTICE] Bug fixes or features added to Salt require tests.
Commits signed with GPG?
Yes