From: Eli Zaretskii <eliz@gnu.org>
To: David Reitter <david.reitter@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: 23 branch - can't push - lock
Date: Thu, 16 Jun 2011 20:27:41 +0300 [thread overview]
Message-ID: <83boxxy9de.fsf@gnu.org> (raw)
In-Reply-To: <1C745F22-51D9-4FE6-A8EF-5D621109E656@gmail.com>
> From: David Reitter <david.reitter@gmail.com>
> Date: Thu, 16 Jun 2011 11:49:05 -0400
>
> Can't push to the 23 branch - there's a lock. Any suggestions?
Yes, the obvious: "bzr break-lock".
But someone already did, because it isn't locked. Maybe it's a local
lock on your machine, in which case "bzr break-lock" will fix that.
> The usual bzr comment: This is not the only weird problem I had with Bazaar, and I was just trying to push a change to make the 23 branch compile again. It's been slow, I've seen unclear error messages, and now I can't push. Oh man.
What is your network bandwidth? It's quite fast for me (I have 3.5Mbps).
To say something positive at least, "bzr resolve" trumps git's manual "add" operations in terms of convenience.
> dr@elin:~/Projects/emacs/emacs-23 $ bzr push
> Using saved push location: bzr://bzr.savannah.gnu.org/emacs/emacs-23
> bzr: ERROR: Cannot lock LockDir(filtered-160255308:///emacs/emacs-23/.bzr/branch/lock): Permission denied: "/srv/bzr/emacs/emacs-23/.bzr/branch/lock/lufitpwgqo.tmp": [Errno 13] Permission denied: '/srv/bzr/emacs/emacs-23/.bzr/branch/lock/lufitpwgqo.tmp'
That _is_ a local lock on your machine. Did you Ctrl-C in the middle
of a commit or something?
next prev parent reply other threads:[~2011-06-16 17:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-16 15:49 23 branch - can't push - lock David Reitter
2011-06-16 16:28 ` David Reitter
2011-06-16 21:44 ` Glenn Morris
2011-06-16 17:27 ` Eli Zaretskii [this message]
2011-06-16 17:44 ` David Reitter
2011-06-16 20:09 ` Eli Zaretskii
2011-06-17 13:57 ` David Reitter
2011-06-17 15:39 ` Eli Zaretskii
2011-06-17 19:19 ` UI / reaction time - was: " David Reitter
2011-06-17 21:59 ` chad
2011-06-19 13:42 ` Stephen J. Turnbull
2011-06-17 16:30 ` Stefan Monnier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83boxxy9de.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=david.reitter@gmail.com \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.