waf assumes that python2.X-config is a python script
Bug #1108983 reported by
Robie Basak
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
talloc (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
tdb (Ubuntu) |
Fix Released
|
High
|
Unassigned |
Related branches
Changed in talloc (Ubuntu): | |
status: | Confirmed → Fix Committed |
Changed in tdb (Ubuntu): | |
status: | Confirmed → Fix Committed |
To post a comment you must log in.
Raring (and Debian experimental) now use a shell script for python2.7-config instead of the original upstream Python script. We should call python2.7-config as an executable directly instead of assuming that it is a Python script.
Both talloc and tdb are affected by the same issue and can be fixed with the same patch which just calls python2.7-config directly instead of via Python. It turns out that the fix was already committed upstream by Jelmer, so we can drop it when the fix filters through.
Debdiffs for talloc and tdb attached above.