Hey Philip thanks for the clarification,
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 :)
** Summary changed:
- having project_path_not_found show the path it failed to find would ease debug
+ project_path_not_found is raised when data_path_not_found should be
** Also affects: quickly
Importance: Undecided
Status: New
** Changed in: quickly
Status: New => Triaged
** Changed in: quickly (Ubuntu)
Status: Invalid => Triaged
** Changed in: quickly
Milestone: None => 0.4
--
project_path_not_found is raised when data_path_not_found should be
https://bugs.launchpad.net/bugs/497688
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
