the context directory is lost in nested requirements files
Bug #1766298 reported by
d t
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
PBR |
Confirmed
|
Medium
|
Unassigned |
Bug Description
I have a directory with requirements files, where one file reference the others, for example:
- requirements
- all.txt
- foo.txt
- bar.txt
where all.txt is:
-r foo.txt
-r bar.txt
When calling pbr.packaging.
To post a comment you must log in.
This may be tricky to fix. Currently pbr doesn't keep track of which file a given requirement line comes from, so there's no way to figure out the base directory for relative paths like this.