fix(build): fix version number when building with old Sapling #712
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.
fix(build): fix version number when building with old Sapling
Summary:
Fix a bug (#711) in Sapling that causes
sl --version
to not work whenbuilding Sapling with an old version of Sapling.
The way
setup.py
gets the version number is by first finding the path tothe vc exe (
findhg
) and then running thesl log ...
(orgit show ...
).findhg
interprets the
hint[old-version]
as an error and aborts.This commit fixes the bug by simply adding
hint[old-version]
tofilterhgerr
Test Plan:
It doesn't seem straightforward to write an automated test for this since we
don't have tests for
setup.py
. The manual steps to test would be:sl
$ sl go "bsearch(date('-50'),main)"
make oss
)./sl --version
Before this commit:
This commit:
Closes #711