bzrlib.errors.ReadingCompleted Internal error
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Confirmed
|
Undecided
|
Unassigned | ||
bzr (Debian) |
Fix Released
|
Unknown
|
Bug Description
bzr pull/branch is failing. I tried from different machines with working configurations for other users.
Only I am hitting the issue. Creating new repository and fresh checkout is also failing with same problem--
so the problem is not specific to parent workspace.
These are the traces:
~/mysql/
Using saved location: bzr+ssh:
bzr: ERROR: bzrlib.
Traceback (most recent call last):
File "/usr/lib/
return run_bzr(argv)
File "/usr/lib/
ret = run(*run_argv)
File "/usr/lib/
return self.run(
File "/usr/lib/
possible_
File "/usr/lib/
possible_
File "/usr/lib/
return BzrDir.
File "/usr/lib/
redirected)
File "/usr/lib/
File "/usr/lib/
return transport, BzrDirFormat.
File "/usr/lib/
return format.
File "/usr/lib/
format_string = transport.
File "/usr/lib/
return StringIO(
File "/usr/lib/
return smart_protocol.
File "/usr/lib/
bytes = self._request.
File "/usr/lib/
raise errors.
ReadingCompleted: The MediumRequest '<bzrlib.
bzr 1.5 on python 2.4.3 (linux2)
arguments: ['/usr/bin/bzr', 'pull']
encoding: 'UTF-8', fsenc: 'UTF-8', lang: 'en_US.UTF-8'
plugins:
bzrtools /usr/lib/
difftools /usr/lib/
extmerge /usr/lib/
gtk /usr/lib/
launchpad /usr/lib/
*** Bazaar has encountered an internal error.
Please report a bug at https:/
including this traceback, and a description of what you
were doing when the error occurred.
Changed in bzr: | |
status: | New → Confirmed |
Changed in bzr: | |
status: | Unknown → New |
Changed in bzr (Debian): | |
status: | New → Fix Released |
tags: | added: check-for-breezy |
It turned out to be the source of the problem is ssh communication. I had .ssh keys setup to avoid prompting of passwords for ssh. I could have not suspected ssh first, because ssh over my destination machine was just working fine. However I noticed the problem when scp was not working (but ssh was ok!). After I removed my .ssh directory, the problem disappeared.
However, this bug needs to be fixed to give proper error message when ssh communication does not work properly.