pull does not understand lp: URLs in branch.conf
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Fix Released
|
Medium
|
Gordon Tyler | ||
QBzr |
Invalid
|
Undecided
|
Unassigned |
Bug Description
My branch.conf for a local branch looks like this:
parent_location = lp:bzr-mac-installers/2.1
And my system location.conf contains the following:
[C:/dev/
submit_branch = lp:bzr-mac-installers
pull_location = lp:bzr-mac-installers
pull_location:
push_location = lp:bzr-mac-installers
push_location:
public_branch = lp:bzr-mac-installers
public_
When I use 'bzr push' in C:/dev/
Using saved parent location: C:/dev/
bzr: ERROR: Not a branch: "C:/dev/
Related branches
- Andrew Bennetts: Needs Fixing
- Martin Pool: Approve
-
Diff: 77 lines (+23/-5)4 files modifiedNEWS (+3/-0)
bzrlib/tests/test_urlutils.py (+14/-0)
bzrlib/transport/__init__.py (+1/-5)
bzrlib/urlutils.py (+5/-0)
description: | updated |
Changed in bzr: | |
assignee: | nobody → Gordon Tyler (doxxx) |
Changed in bzr: | |
status: | Confirmed → In Progress |
Changed in bzr: | |
milestone: | none → 2.2b4 |
status: | In Progress → Fix Released |
I've just put lp:qbzr/0.18 into the branch.conf of my qbzr development branch.
Trying standard bzr commands:
C:\work\ Bazaar\ plugins\ qbzr>bzr info
Lightweight checkout (format: 2a)
Location:
light checkout root: .
checkout of branch: .bzr/branches/0.18
shared repository: .bzr/branches
Related branches:
parent branch: .bzr/branches/0.18/lp:qbzr/0.18
C:\work\ Bazaar\ plugins\ qbzr>bzr pull Bazaar/ plugins/ qbzr/.bzr/ branches/ 0.18/lp:qbzr/0.18 Bazaar/ plugins/ qbzr/.bzr/ branches/ 0.18/lp:qbzr/0.18/".
Using saved parent location: C:/work/
bzr: ERROR: Not a branch: "C:/work/
So as I can see the standard bzr behavior is the same as qbzr one: bzr don't understand directory services in branch.conf. And because qbzr just uses bzr API we get the same problems as bzr core has.
Based on your bug report I don't understand how it actually works for you with plain `bzr pull`.
I'm inclined to mark this bug as Invalid for QBzr or re-assign it to bzr core.