From: "Allen Curtis" <acurtis@onz.com>
To: <linuxppc-dev@lists.linuxppc.org>
Subject: BK... a little help please
Date: Mon, 27 May 2002 20:34:58 -0700 [thread overview]
Message-ID: <NCBBIINEHIPFGJPLBEIFMEKLDHAA.acurtis@onz.com> (raw)
I recently cloned the linuxppc_2_4_devel tree and started working with it
but now the repository is locked and the messages say to contact BitKeeper.
Could someone take a look at the below messages and tell me what needs to be
done.
What was done:
1. make htmldocs - this failed because I am missing "fig2dev"
2. bk pull - results in the messages below
3. bk -r check -acf
Unfortunately, this did not auto-matically correct my problem.
4. bk pull - says that the repository is locked by RESYNC directory
All help and pointers on using BK welcome.
TIA
========================================================================
Applying 1 revisions to ChangeSet
Applying 1 revisions to BitKeeper/deleted/.del-ocp-dma.h~39362d3f62392136
Applying 1 revisions to include/asm-ppc/ocp.h
takepatch: 3 new revisions, 0 conflicts in 3 files
624 bytes uncompressed to 2116, 3.39X expansion
Running resolve to apply new work ...
Using :0 as graphical display
Verifying consistency of the RESYNC tree...
resolve: found 2 renames in pass 1
resolve: resolved 2 renames in pass 2
resolve: applied 4 files in pass 4
resolve: running consistency check, please wait...
=========================================================================
check: ``scripts/docgen'' writable but not checked out.
This means that a file has been modified without first doing a "bk edit".
bk -R edit -g scripts/docgen
will fix the problem by changing the file to checked out status.
Running "bk -r check -acf" will fix most problems automatically.
=========================================================================
=========================================================================
check: ``scripts/gen-all-syms'' writable but not checked out.
This means that a file has been modified without first doing a "bk edit".
bk -R edit -g scripts/gen-all-syms
will fix the problem by changing the file to checked out status.
Running "bk -r check -acf" will fix most problems automatically.
=========================================================================
=========================================================================
check: ``scripts/kernel-doc'' writable but not checked out.
This means that a file has been modified without first doing a "bk edit".
bk -R edit -g scripts/kernel-doc
will fix the problem by changing the file to checked out status.
Running "bk -r check -acf" will fix most problems automatically.
=========================================================================
Check failed. Resolve not completed.
SCCS/s.ChangeSet
include/asm-ppc/SCCS/s.ocp-dma.h
BitKeeper/etc/SCCS/s.gone
BitKeeper/deleted/SCCS/s..del-ocp.h~73a8dba61594f2
Your repository should be back to where it was before the resolve started.
We are running a consistency check to verify this.
=========================================================================
check: ``scripts/docgen'' writable but not checked out.
This means that a file has been modified without first doing a "bk edit".
bk -R edit -g scripts/docgen
will fix the problem by changing the file to checked out status.
Running "bk -r check -acf" will fix most problems automatically.
=========================================================================
=========================================================================
check: ``scripts/gen-all-syms'' writable but not checked out.
This means that a file has been modified without first doing a "bk edit".
bk -R edit -g scripts/gen-all-syms
will fix the problem by changing the file to checked out status.
Running "bk -r check -acf" will fix most problems automatically.
=========================================================================
=========================================================================
check: ``scripts/kernel-doc'' writable but not checked out.
This means that a file has been modified without first doing a "bk edit".
bk -R edit -g scripts/kernel-doc
will fix the problem by changing the file to checked out status.
Running "bk -r check -acf" will fix most problems automatically.
=========================================================================
Check FAILED, contact BitMover.
resolve: RESYNC directory left intact.
====================================================
[acurtis@ws01 linuxppc_2_4_devel]$ bk -r check -acf
[acurtis@ws01 linuxppc_2_4_devel]$ bk pull
Entire repository is locked by:
RESYNC directory.
ERROR-Unable to lock repository for update.
--
All things come to those who wait. Some of us just have to wait a little
longer...
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2002-05-28 3:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-28 3:34 Allen Curtis [this message]
2002-05-28 6:53 ` BK... a little help please Momchil Velikov
2002-05-28 13:39 ` Allen Curtis
2002-05-28 21:56 ` Val Henson
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=NCBBIINEHIPFGJPLBEIFMEKLDHAA.acurtis@onz.com \
--to=acurtis@onz.com \
--cc=linuxppc-dev@lists.linuxppc.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).