No, it's not that working on a plane sucks ;)
project_path_not_found should only be called in the case I previously described (in get_root_project_path). Not when no data path is found!
Consequently, you are totally correct about providing wrong data path is needed (even though data path is now collected with trunk version by apport when you use "ubuntu-bug quickly"): the thing is to raise the right exception (which has to be created: "data_path_no_found").
So, I'm changing wrong raise/except catchup when project_path_not_found was instantiated instead of data_path_not_found based on your patch. I rename the bug too. Thanks for your contribution and your feedback :)
Hey Philip thanks for the clarification,
No, it's not that working on a plane sucks ;) path_not_ found should only be called in the case I previously described (in get_root_ project_ path). Not when no data path is found!
project_
Consequently, you are totally correct about providing wrong data path is needed (even though data path is now collected with trunk version by apport when you use "ubuntu-bug quickly"): the thing is to raise the right exception (which has to be created: "data_path_ no_found" ).
So, I'm changing wrong raise/except catchup when project_ path_not_ found was instantiated instead of data_path_not_found based on your patch. I rename the bug too. Thanks for your contribution and your feedback :)