diff options
| author | Chandan Singh <csingh43@bloomberg.net> | 2018-08-22 18:41:09 +0100 |
|---|---|---|
| committer | Chandan Singh <csingh43@bloomberg.net> | 2018-08-22 21:11:19 +0100 |
| commit | e1d5bfa5ed752adb8a8a8ed81592fd4147e83de7 (patch) | |
| tree | f2b2889affeadf70d9de106f063fec492d7c8b32 | |
| parent | baee80b4700312ef603fe2ec0eb9d9ee77424cab (diff) | |
| download | buildstream-chandan/fix-mainfest-dev-requirements-1.2.tar.gz | |
MANIFEST.in: Fix include for dev-requirements.txtchandan/fix-mainfest-dev-requirements-1.2
Currently, running any setuptools commands using `setup.py` generates a
warning like so:
warning: manifest_maker: MANIFEST.in, line 21: unknown action 'dev-requirements.txt'
The syntax is invalid and got accidentally introduced in !637 but it's a
shame that this is not a warning and no obvious way to make it an error
if there are invalid things in MANIFEST.in file.
---
This is a backport of
https://gitlab.com/BuildStream/buildstream/merge_requests/704.
| -rw-r--r-- | MANIFEST.in | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/MANIFEST.in b/MANIFEST.in index 80c815e55..f9e506027 100644 --- a/MANIFEST.in +++ b/MANIFEST.in @@ -23,4 +23,4 @@ recursive-include tests *.expected recursive-include buildstream/_protos *.proto # Requirements files -dev-requirements.txt +include dev-requirements.txt |