Could not acquire lock "(remote lock)"

[Tom Eugelink]

I'm getting the follow log in TortoiseBZR

Connected (version 2.0, client OpenSSH_5.5p1)
Authentication (password) successful!
Secsh channel 1 opened.
bzr: ERROR: Could not acquire lock "(remote lock)": bzr+ssh://.../home/bzr/reinders/

Executing "bzr break-lock bzr+ssh://.../home/bzr/reinders/" either locally and report does not report anything, but does not break the lock.

Rebooting the machine did not help.

This is now completely blocking the use of the repo. I'm running BZR 2.5.1 on the client and the latest available version on the server (Ubuntu).

[Tom Eugelink (tbee)]

Ubuntu runs BZR 2.1.2

[John A Meinel (jameinel)]

Can you give more background information? Such as "bzr info bzr+ssh://.../home/bzr/reinders" says?

[Tom Eugelink (tbee)]

"bzr info reinders"

Shared repository with trees (format: 2a)
Location:
  shared repository: reinders

[John A Meinel (jameinel)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2013-01-30 10:48, Tom Eugelink wrote:
> "bzr info reinders"
>
> Shared repository with trees (format: 2a) Location: shared
> repository: reinders
>

I'm guessing you would be trying to push to a branch, rather than a
repository. So I realize the message might be talking about the repo
being locked, you probably need to check the branches that are in the
repository.

John
=:->

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (Cygwin)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlEI2YEACgkQJdeBCYSNAAN7gACgl37OyFfa/Cg2buCoq8PBGmel
JFUAoL/kRycb3C4oEgsxiM/JEI+jkZ6o
=XRbJ
-----END PGP SIGNATURE-----

[Tom Eugelink (tbee)]

I'm using BZR in a very simple mode; replacement for CVS / SVN. I am the only developer and only have one branch (trunk) and that is what I have been committing against for the past year.

[Tom Eugelink (tbee)]

What I did was a bzr commit, cancelled that because it was committing a directory with jars inside, and since then the lock is in place. How do I remove that lock?

[John A Meinel (jameinel)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2013-01-31 1:46, Tom Eugelink wrote:
> What I did was a bzr commit, cancelled that because it was
> committing a directory with jars inside, and since then the lock is
> in place. How do I remove that lock?
>

It should be "bzr break-lock PATH-TO-BRANCH".

If you are just doing "bzr commit" then you probably have a checkout,
and you should be able to just do "bzr break-lock" with no parameters,
and it should check all the branches/trees/repositories associated
with that checkout.

John
=:->

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (Cygwin)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlEKTGUACgkQJdeBCYSNAAPZTACfaj0rrYaTQEequakuDaNSdjF+
GEsAn19SUEUDyy7BMPu/Oe+42qlGL0aN
=9PuU
-----END PGP SIGNATURE-----

[Tom Eugelink (tbee)]

Ah! Indeed, break-lock on the trunk reported that it broke a lock.

Thanks

On 2013-01-31 11:50, John A Meinel wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 2013-01-31 1:46, Tom Eugelink wrote:
>> What I did was a bzr commit, cancelled that because it was
>> committing a directory with jars inside, and since then the lock is
>> in place. How do I remove that lock?
>>
> It should be "bzr break-lock PATH-TO-BRANCH".
>
> If you are just doing "bzr commit" then you probably have a checkout,
> and you should be able to just do "bzr break-lock" with no parameters,
> and it should check all the branches/trees/repositories associated
> with that checkout.
>
> John
> =:->
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.12 (Cygwin)
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iEYEARECAAYFAlEKTGUACgkQJdeBCYSNAAPZTACfaj0rrYaTQEequakuDaNSdjF+
> GEsAn19SUEUDyy7BMPu/Oe+42qlGL0aN
> =9PuU
> -----END PGP SIGNATURE-----
>