From: David Gibson <david@gibson.dropbear.id.au>
To: Tom Rini <trini@kernel.crashing.org>
Cc: acurtis@directvinternet.com,
"David M?ller (ELSOFT AG)" <d.mueller@elsoft.ch>,
linuxppc-dev@lists.linuxppc.org, lm@bitmover.com
Subject: Re: Problem with bk repository?
Date: Wed, 7 Aug 2002 10:12:52 +1000 [thread overview]
Message-ID: <20020807001252.GF5012@zax> (raw)
In-Reply-To: <20020806161339.GB714@opus.bloom.county>
On Tue, Aug 06, 2002 at 09:13:39AM -0700, Tom Rini wrote:
> On Tue, Aug 06, 2002 at 08:46:50AM -0700, acurtis@directvinternet.com wrote:
> >
> > >
> > > david@devil:/repository/linuxppc_2_4_devel>bk parent
> > > Parent repository is bk://ppc.bkbits.net/linuxppc_2_4_devel
> > > david@devil:/repository/linuxppc_2_4_devel>bk pull -ll
> > > ERROR-Can't get read lock on the repository.
> > > pull: remote locked, trying again...
> > > ERROR-Can't get read lock on the repository.
> > > pull: remote locked, trying again...
> > > ERROR-Can't get read lock on the repository.
> > > pull: remote locked, trying again...
> > > ERROR-Can't get read lock on the repository.
> > > pull: remote locked, trying again...
> >
> > I was it for the first time today too.
>
> Are either of you still getting this? What seems to be happening is
> that when David Gibson pushes something to the tree, it never quite
> finishes and Bk ends up in a slightly wierd state. David, are you
> behind some sort of wierd network setup or anything?
Ah, crap. I did run into this the other day - I did a push which got
interrupted (connection closed by foreign host - probably due to
SOCKS). After that my pulls (and attempts to push again) complained
that there was a lock. But paulus had a look at the parent repository
where 'll' denied that there was any lock - at least it did the second
time it was invoked. My pulls were still failing and I was going to
send out a mail, but the next day it seemed to be working again, so I
figured it was a once off breakage.
I guess I was wrong.
I'm not sure if my last push was interrupted, or whether there was
some residual breakage from the earlier push in the repository which
got triggered again by the later push.
Pulls are working again for me now, so I'm not sure what to do next to
investigate this.
--
David Gibson | For every complex problem there is a
david@gibson.dropbear.id.au | solution which is simple, neat and
| wrong.
http://www.ozlabs.org/people/dgibson
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-08-07 0:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-06 15:24 Problem with bk repository? "David Müller (ELSOFT AG)"
2002-08-06 15:46 ` acurtis
2002-08-06 16:13 ` Tom Rini
2002-08-07 0:12 ` David Gibson [this message]
2002-08-07 0:29 ` Larry McVoy
2002-08-07 15:12 ` Larry McVoy
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=20020807001252.GF5012@zax \
--to=david@gibson.dropbear.id.au \
--cc=acurtis@directvinternet.com \
--cc=d.mueller@elsoft.ch \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=lm@bitmover.com \
--cc=trini@kernel.crashing.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.
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 NNTP newsgroup(s).