unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Karl Fogel <kfogel@red-bean.com>
To: bob@gnu.org (Robert J. Chassell)
Cc: emacs-devel@gnu.org
Subject: Re: bazaar: "unable to obtain lock"
Date: Tue, 29 Dec 2009 22:39:43 -0500	[thread overview]
Message-ID: <87my11gmf4.fsf@red-bean.com> (raw)
In-Reply-To: <E1NPls9-0000TH-8I@fencepost.gnu.org> (Robert J. Chassell's message of "Tue, 29 Dec 2009 18:53:05 -0500")

bob@gnu.org (Robert J. Chassell) writes:
>    >Unable to obtain lock
>    >sftp://bzr.savannah.gnu.org/srv/bzr/emacs/trunk/.bzr/branch/lock
>    >held by bob@gnu.org on host benthic [process #13025]
>    >locked 6 hours, 10 minutes ago
>
>That was me.  (I don't connect to the Internet very often.)  I was
>trying to download for about four hours this morning, but not for 6
>hours.  It was clearly something wrong.
>
>This afternoon, I moved my /usr/local/src/emacs/ directory to
>/usr/local/src/emacs-09dec29 and restarted, following the
>http://www.emacswiki.org/emacs/BzrForEmacsDevs document exactly.  I
>gave up after a few hours, after getting 181780 kilobytes according to
>`du -s'.  According to the progress meter, the download was less than
>half done.  I have an old laptop with a half gigabyte of RAM.  The
>wireless connection I use might be broken (I cannot fix it -- it is
>not mine, but is the only way I can connect.  It works for other
>connections, as you can see:  I am SSH'd to fp.gnu.org to mail this
>message, but am writing conveniently on a different Emacs on my home
>machine.)
>
>In any case, I thought I had downloaded a bzr version that worked
>yesterday (I used it successfully today for other things) but it
>turned out to fail with sending mail so I have started an older Emacs
>and am using that to write this message.  Also, because of a change in
>Debian testing, I am no longer coming into X as `bob' but doing the
>same as `root' with `sudo -i -u bob rxvt' in my root Enlightenment
>.xinitrc file.
>
>I have tried to download the latest CVS version every morning and build
>it with the following, and then use it:
>
>   (progn
>     (cd "/usr/local/src/emacs/")
>     (cvs-update "/usr/local/src/emacs/" '("-dPA")))
>
>   ;; usually takes less than half a minute and 18k
>   (progn
>      (cd "/usr/local/src/emacs/")
>      (compile
>       "time make -k -C lisp autoloads EMACS=/usr/local/src/emacs/src/emacs && \
>        cd lisp && \
>       time make cvs-update EMACS=/usr/local/src/emacs/src/emacs && \
>       cd /usr/local/src/emacs/ && \
>       time make info html"))
>
>   ;; make may take 20 minutes; usually takes a minute or so
>   (progn
>     (cd "/usr/local/src/emacs/")
>     (compile "time make -k"))
>
>So far, so good!  Only occasionally has there been trouble and it has
>been fixed within 24 hours.  But I may not be able to download the bzr
>version.
>
>What should I do?  Please remember, I am dumber than I was.

Wow.  I don't know why Bzr ballooned that much when trying to branch; as
far as I know it "worked fine for me", but then maybe my machine just
has enough memory that I didn't notice.

If you want, just grab this file:

  http://www.red-bean.com/kfogel/emacs-bzr-repository.tar.gz

and unpack it as your emacs/ development directory.  That carries you to
the end of "Initialize Your quickfixes Branch" section in the
instructions (you'll have to edit emacs/trunk/.bzr/branch/branch.conf to
say "bob" instead of "kfogel", of course).

-Karl




  reply	other threads:[~2009-12-30  3:39 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-29 23:53 bazaar: "unable to obtain lock" Robert J. Chassell
2009-12-30  3:39 ` Karl Fogel [this message]
2009-12-30 15:15   ` Robert J. Chassell
2009-12-31 19:14     ` Karl Fogel
2010-01-01  0:19       ` Robert J. Chassell
2009-12-31 19:15     ` Karl Fogel
2009-12-30 16:43   ` Robert J. Chassell
2009-12-30 17:25     ` Andreas Schwab
2009-12-30 21:46       ` Robert J. Chassell
2009-12-30 22:18         ` Andreas Schwab
2009-12-31  1:48           ` Robert J. Chassell
2009-12-31  4:29             ` Óscar Fuentes
2009-12-31  6:59               ` Óscar Fuentes
2009-12-31 11:32               ` Robert J. Chassell
2009-12-31 14:57                 ` James Cloos
2009-12-30 23:34   ` Kevin Ryde
2009-12-31  0:30     ` Óscar Fuentes
2009-12-31  0:44       ` Lennart Borgman
2009-12-31  1:07         ` Óscar Fuentes
2009-12-31  1:24           ` Lennart Borgman
2010-01-03 22:38       ` Kevin Ryde
2010-01-04  7:05         ` Eli Zaretskii
2010-01-05 21:20           ` Kevin Ryde
2010-01-01  9:59     ` Stephen J. Turnbull
2010-01-01 10:16       ` Óscar Fuentes
2010-01-01 16:42       ` Jason Earl
2009-12-30  9:19 ` David Kastrup
  -- strict thread matches above, loose matches on Subject: below --
2009-12-29 17:14 Juanma Barranquero
2009-12-29 17:40 ` Karl Fogel
2009-12-29 17:44   ` Juanma Barranquero
2009-12-29 18:42     ` Karl Fogel
2009-12-29 20:39       ` Juanma Barranquero

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87my11gmf4.fsf@red-bean.com \
    --to=kfogel@red-bean.com \
    --cc=bob@gnu.org \
    --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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).