should not have ~user/project/.bzr/control.conf in vfss used by puller

Bug #288655 reported by Michael Hudson-Doyle
2
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
High
Jonathan Lange

Bug Description

It turns out that having the $project/.bzr/control.conf directory in the lp-mirror:/// filesystem is a bad idea -- the branch we create ends up being initially stacked on the default stack-on branch, which isn't as bad as it might sound because we immediately stack it on a more appropriate branch, but it's pretty bad because if opening the default stack-on branch fails, it all explodes (with a ridiculous message).

Jonathan Lange (jml)
Changed in launchpad-bazaar:
importance: Undecided → High
milestone: none → 2.1.12
status: New → Triaged
Jonathan Lange (jml)
Changed in launchpad-bazaar:
assignee: nobody → jml
milestone: 2.1.12 → 2.1.11
Jonathan Lange (jml)
Changed in launchpad-bazaar:
status: Triaged → In Progress
Jonathan Lange (jml)
Changed in launchpad-bazaar:
status: In Progress → Fix Committed
Tim Penhey (thumper)
Changed in launchpad-bazaar:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.