bzr+ssh says "has no revision", sftp doesn't complain
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Bazaar |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
When doing info on a branch on Launchpad (server running Bazaar 1.10 at the time), client running 1.11dev, I get an error if I query the branch via bzr+ssh, but no error if I query it via sftp.
Observe!
$ bzr info -v lp://staging/
Repository branch (format: unnamed)
Location:
shared repository: bzr+ssh:
repository branch: bzr+ssh:
Related branches:
parent branch: /home/jml/
stacked on: /~jml/rc-fix/trunk
Format:
control: bzr remote bzrdir
branch: Remote BZR Branch
repository: bzr remote repository
Branch history:
12 revisions
bzr: ERROR: Server sent an unexpected error: ('error', "KnitPackReposi
HPSS calls: 34 <bzrlib.
$ bzr info -v sftp://
Repository branch (format: 1.9)
Location:
shared repository: sftp://
repository branch: sftp://
Related branches:
parent branch: /home/jml/
stacked on: /~jml/rc-fix/trunk
Format:
control: Meta directory format 1
branch: Branch format 7
repository: Packs 6 (uses btree indexes, requires bzr 1.9)
Branch history:
12 revisions
2 committers
198 days old
first revision: Sun 2008-06-01 15:27:58 +1000
latest revision: Sat 2008-10-04 13:59:24 +1000
Repository:
26 revisions
| John A Meinel (jameinel) wrote | #1 |
| Changed in bzr: | |
| status: | New → Fix Released |
I'm pretty sure this is a duplicate of the 'stacking' bug, so for now I'm going to mark it as such. (Basically, sftp is resolved locally, thus the VersionedFile object has the fallback set and can grab the data from there, bzr+ssh tries to resolve everything on the server *without* the fallback. So the fix was to push more data into every branch so it can resolve the information without fallbacks.)
I don't remember the bug, but we've generally fixed this.