Single-user operations getting locked in a shared repository

Vincent Vertigo vincent.vertigo at gmail.com
Thu Oct 18 13:32:14 BST 2007


Hi,

Using the official 0.91 release, I reopened bug #83503 (state new):
https://bugs.launchpad.net/bzr/+bug/83503

The bug was opened for a lock problem when pushing to a branch in the same
repository.
I could not reproduce that same bug, but managed to reproduce the same
problem with a commit on a checkout (still within the same shared repo).
The bug is also presented in bug #95004 (in state 'confirmed' since
2007-03-26),
with hints as how to fix it.

I thought the problem might be important enough to be raised on the mailing
list, as it affects (what i think is) a common operation with the latest
official release.
Are there any plans to fix this? (There may be other bugs around dealing
with that issue of shared repository referenced by different objects, my
investigation was rather shallow).

Regards,
Vincent.

Side note:
I reopened the bug in state "new". I am not sure if this was the right thing
to do, but I could not find any specific guideline about how Bazaar bugs are
tracked (except through the generic Launchpad documentation). Unless I
missed it, I was wondering if such documentation [ exists / is planned / is
necessary ].
I am thinking of guidelines such as the ones written for Django web
framework project:
http://www.djangoproject.com/documentation/contributing/#reporting-bugs
http://www.djangoproject.com/documentation/contributing/#ticket-triage
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ubuntu.com/archives/bazaar/attachments/20071018/fc964eb6/attachment.htm 


More information about the bazaar mailing list