should not immediately abort of .bzr/format can't be opened
Bug #216614 reported by
Jelmer Vernooij
This bug report is a duplicate of:
Bug #256612: should prompt for usernames during HTTP Basic/Digest auth.
Edit
Remove
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Bazaar |
Incomplete
|
Undecided
|
Unassigned | ||
Bug Description
It should be possible to probe for multiple formats even if the first ones tried fail horribly. E.g. even if opening .bzr/branch/
Revision history for this message
| John A Meinel (jameinel) wrote | #1 |
| Changed in bzr: | |
| status: | New → Incomplete |
To post a comment you must log in.
Well, if we get a 401, shouldn't we be trying to prompt the user to authenticate? Certainly we shouldn't be stopping completely at that point. We should certainly be retrying the 401 with some amount of authentication (I don't know that this could be passed to bzr-svn). Otherwise you wouldn't be able to download from a password protected bzr branch.
If the auth fails completely.. it seems reasonable to have it fail rather than have it prompt for authentication over and over trying for different ones that we won't use.
Could you describe how we are failing in a way that we don't recover, and maybe provide a bit more information about what you want to see?