New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Expected committer but didn't get one" #14
Comments
great, thanks for the bug report, i'll check this out |
I had the same issue when I was using the bzr that came with Ubuntu M (2.2.1) When I uninstalled and installed using pip install, I wasn't able to install 2.2 (not found), but I was able to just "pip install bzr". I got bzr 2.3.1. It got me past the "expected committer but didn't get one". I am having trouble pushing but haven't diagnosed that yet. (I thought I already posted this; apologies if this is duplicated) |
pip install bzr==2.2 failed? :( grr, it looks like they pushed 2.3.0 (instead of the beta versions) but i suspect they maintained the bug that affects pushing |
It definitely "fails for me": $ sudo pip install bzr==2.2 Is the pushing a known bug? Should I be installing bzr from 2.2 source manually then? |
Yeha, it's a known bug: https://bugs.launchpad.net/bzr/+bug/541626 this is disappointing :/ I'd suggest installing 2.2 from source, there is a simple patch to fix the issue but it seems more trouble than installing 2.2 from source. |
I believe I have resolved the push issue that I was experiencing - I wasn't getting the "BTreeBuilder" message, I was getting a message about an extra argument. I traced that down to bzr-fastimport trunk. See issue #19 for a "works for me" resolution :-) |
this appears to be fixed once upgrading to bzr 2.3.0 |
I did the following:
I don't know enough about bzr to know where the problem lies or how to fix it. :-/
The text was updated successfully, but these errors were encountered: