Bazaar

Why does bzr try (and fail) to write to a remote repo on commit?

Asked by Malte S. Stretz

I just checked out lp:mailman/2.1, patched some stuff and pushed it to an own branch. Everything went fine.

Then I tried to forward-port (easy, patch still applies) my changes to 2.2. So checked out lp:mailman/2.2, applied my patch and tried to commit. And bzr asked me to unlock my SSH key. And failed with the complaint that I can't obtain a remote lock. Of course I can't, but why did it try to do this on commit time anyway?!?

mss@TreeHouse:~/Work/mailman$ bzr lp-login mss
mss@TreeHouse:~/Work/mailman$ bzr checkout lp:mailman/2.2
Enter passphrase for key '/home/mss/.ssh/id_rsa':
mss@TreeHouse:~/Work/mailman$ cd 2.2
mss@TreeHouse:~/Work/mailman/2.2$ patch -p0 < /tmp/1243.patch
patching file Mailman/Defaults.py.in
Hunk #1 succeeded at 1045 (offset 5 lines).
patching file Mailman/Gui/General.py
patching file Mailman/Handlers/SMTPDirect.py
patching file Mailman/MailList.py
Hunk #1 succeeded at 366 (offset 3 lines).
patching file Mailman/versions.py
Hunk #1 succeeded at 364 (offset 11 lines).
mss@TreeHouse:~/Work/mailman/2.2$ bzr commit -v
Enter passphrase for key '/home/mss/.ssh/id_rsa':
bzr: ERROR: Cannot lock LockDir(lp-69744016:///~mailman-coders/mailman/2.2/.bzr/branchlock): Transport operation not possible: readonly transport

Question information

Language:
English Edit question
Status:
Solved
For:
Bazaar Edit question
Assignee:
No assignee Edit question
Solved by:
Gordon Tyler
Solved:
Last query:
Last reply:
Revision history for this message
Best Gordon Tyler (doxxx) said : 		#1

'bzr checkout' creates a bound branch, which will automatically commit to the remote branch before committing locally. If you want to be able to make local commits use 'bzr branch' and then 'bzr push' and 'bzr pull' to send and receive new commits to/from the remote branch.

Revision history for this message
Malte S. Stretz (mss) said : 		#2

Thanks Gordon Tyler, that solved my question.