Translate paths back to virtual paths when handling errors in vfs transports
Bug #270076 reported by
Jonathan Lange
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Confirmed
|
Wishlist
|
Unassigned | ||
Launchpad itself |
Triaged
|
Low
|
Unassigned |
Bug Description
At the moment, people get errors like this from bzr:
Format <RepositoryForm
starting upgrade of bzr+ssh://<email address hidden>
making backup of tree history
bzr: ERROR: File exists: '/srv/bazaar.
We shouldn't show them the internal address — it's confusing and they don't need to know it. We should translate the paths in all errors raised from the virtual transport.
tags: | added: check-for-breezy |
To post a comment you must log in.
This doesn't look too hard in fact, we can intercept PathError and translate that. We're not totally consistent about the way we invoke the methods on the underlying transport and I guess we'll be wanting to clean that up at the same time.
I'm not sure how to actual do the untranslation, how general to try to make it. Just hacking it wouldn't be hard, I think.