push from lightweight checkout to location with bzrdir creates BranchReference
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Confirmed
|
High
|
Unassigned | ||
Breezy |
Triaged
|
Medium
|
Jelmer Vernooij |
Bug Description
I don't have a reliable way of reproducing this problem, but thought I'd report it anyway in case anyone else has an insight.
As part of Launchpad development, I'll often push branches to our development server, roughly following this workflow:
1. create a lightweight checkout of the local copy of the branch
2. make my changes in the lightweight checkout and commit
3. run "bzr push" in the lightweight checkout, which will create a new branch and push it via bzr+ssh to the development server.
The destination directory on the development server is part of a shared repository.
Usually this works fine, but once or twice I ended up with a BranchReference object on the server containing the path to the local copy of the branch (which of course does not exist remotely).
It only happens occasionally, but it has also happened to other members of the team so I don't think it is purely related to my local environment.
Changed in bzr: | |
status: | Triaged → Confirmed |
tags: | added: check-for-breezy |
tags: | removed: check-for-breezy |
Changed in brz: | |
status: | New → Triaged |
importance: | Undecided → Medium |
assignee: | nobody → Jelmer Vernooij (jelmer) |
This happens to me consistently. Here are some details:
kiko@whatever:~$ bzr --version
Bazaar (bzr) 0.90.0
I use a script to create my branches:
# Create the branch in the repository archives/ launchpad $1
cd ~/repo/
bzr branch ~/devel/
# Make a lightweight checkout of the new branch
cd ~/devel
bzr checkout --lightweight ~/repo/$1 $1
bzr push --remember \ ssh://devpad. canonical. com/code/ kiko/launchpad/ $1 &
bzr+
I then use the checkout, commit, commit and then push, and it says no new revisions. I can reproduce this pretty reliably using whatever. async.com. br and devpad. canonical. com.