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-----
>
Ah! Indeed, break-lock on the trunk reported that it broke a lock.
Thanks
On 2013-01-31 11:50, John A Meinel wrote: trees/repositor ies associated www.enigmail. net/ KTGUACgkQJdeBCY SNAAPZTACfaj0rr YaTQEequakuDaNS djF+ BMPu/Oe+ 42qlGL0aN
> -----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/
> with that checkout.
>
> John
> =:->
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.12 (Cygwin)
> Comment: Using GnuPG with Thunderbird - http://
>
> iEYEARECAAYFAlE
> GEsAn19SUEUDyy7
> =9PuU
> -----END PGP SIGNATURE-----
>