Silent failure if no bzrdefaults file
Bug #1831915 reported by
Robert Ladyman
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
EasyBreezy |
Fix Released
|
High
|
HBCoders |
Bug Description
If the bzrdefaults file does not exist, then operations depending upon it that cannot use existing settings (checkout, new project) silently fail.
The action should probably report that the settings file is either missing or has no values set.
tags: | added: error-reporting |
tags: | added: ui |
Changed in easybreezy: | |
status: | New → Triaged |
status: | Triaged → New |
status: | New → Triaged |
importance: | Undecided → High |
tags: | added: feature-request installation |
Changed in easybreezy: | |
assignee: | nobody → HBCoders (hbcoders) |
description: | updated |
To post a comment you must log in.
[Notes re: installer]
We have some choices here: the actions requiring the presence of the bzrdefaults file could be disabled if it does not exist (simplest) or the chooser / setup could be run if the file does not exist (and the options always be available).
Alternatively, there could be a setup option (where bzrdefaults does not exist) and then a chooser option once it does exist ('add a repository' or somesuch).