"Not a branch" errors could be better when branch is missing.
Bug #52865 reported by
Andrew Bennetts
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Bazaar |
Confirmed
|
Wishlist
|
Unassigned | ||
Bug Description
Consider this:
andrew@steerpike:~$ bzr branch /tmp/fjsdfjkldf
bzr: ERROR: Not a branch: /tmp/fjsdfjkldf
To me, "Not a branch" implies that there is something there, and that it isn't a branch. However, the situation is actually that path specified doesn't exist at all. I'd expect the error message to be clearer about this.
It's more of an issue with http and sftp urls, I think, because then it's not as easy to interactively browse to the location and realise that the problem is it's absent.
Revision history for this message
| John A Meinel (jameinel) wrote | #1 |
| Changed in bzr: | |
| importance: | Undecided → Wishlist |
| status: | Unconfirmed → Confirmed |
| tags: | added: check-for-breezy |
To post a comment you must log in.
Part of the problem is that we cannot reliably detect whether or not a remote directory exists (especially over http).
So it would be possible to have code catch NotBranchError, and then do an inspection to see if it should be PathDoesNotExist, or something like that, it may be fragile.
For now, I'm marking this as a Wishlist item.