Remembering an URL different from the one the user entered is surprising
Bug #569361 reported by
Jasper St. Pierre
This bug affects 4 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Confirmed
|
Wishlist
|
Unassigned |
Bug Description
I was trying to pull from a repository that Launchpad had said had been last updated "9 days ago", but "bzr log" said it had been last updated in February. It was then that I realized that the branch linked to "lp:project" had been changed, but bazaar was still trying to pull from the old path. I found this a little strange, I originally branched from "lp:project" and what I had to do to solve it was "bzr pull lp:project". Shouldn't bzr try to keep the unresolved path around, so it can track any changes to what it links to?
tags: | added: check-for-breezy |
To post a comment you must log in.
Note that bzr should still have the *old* url in branch.conf, you can check that with 'bzr info'.
You can update it with 'bzr pull --remember <new_url>'.
As for whether bzr should remember 'lp:project' or how it is translated into when first used (bzr+ssh: //bazaar. launchpad. net/~<project_ devs>/< project> /<development_ focus>/ , the debate is still open, both are valid use cases so we may want an option to decide.
IMHO, we should remember what the user entered on the command line and I think there is a bug open about that. Doing so will allow the user to specify the bzr+ssh form instead of the lp form.