|
|
|
Error messages
-
What does this message mean?
 |
Running resolve to apply new work...
Check: found in ChangeSet but not found in repository:
|
This means you may have deleted an sfile after having committed it
to a changeset.
-
Sometimes
bk clean acts confused and responds with:
<filename> writable but not edited
What's going on?
Just do a bk edit -g <your file> (this changes
your file to edit status without overwriting your existing gfile)
and then run
bk citool again.
-
What would cause Entire Repository locked by RESYNC error:
|
Entire repository is locked by:
RESYNC directory.
Cannot do pull into locked repository.
|
The RESYNC directory exists because a previous bk pull failed due
to a conflict that hasn't yet been resolved.
At the end of that pull, there should have been a message stating
something like "pull failed due to unresolved conflict, run
resolve".
At this point, you have two options: if you want to resolve the
previous conflict and continue with a new pull, you should run 'bk
resolve' and then type 'e', fix the conflict, get out of the
editor, and then type 'C' to commit the fix.
Or, if you don't want to do the conflict resolution, you can do a
'bk abort' and that will get rid of the RESYNC directory, but you
will eventually have to resolve the conflict in order to pull.
-
What does this error message mean?
|
getRegBody: Can't open bk-names.1 for writing
get of SCCS/s.bk-names.1 failed, skipping it.
getRegBody: Can't open bk-unpark.1 for writing
get of SCCS/s.bk-unpark.1 failed, skipping it.
getRegBody: Can't open bk-level.1 for writing
|
It most likely means that your system has run out of inodes.
-
Is there some way to get better information when debugging the logging process?
|
bk _log -d
|
will tell you what is going on.
-
I am trying to push up to my repository and I get the following errors:
|
Running resolved to apply new work ....
============================
sane: bad host name: "red-hat". BitKeeper wants fully qualified
hostname.
===========================
{bk}{-r}{check}{-cR} failed. Resolve not even started.
|
Actually, the name of my computer IS red-hat. What can I do to get around this?
BitKeeper requires fully-qualified DNS names in order to ensure we
do not create BK keys that are not unique.
A key looks like this:
|
user@host.domain|src/foo.c|YYYYMMDDHHSS|12345
|
and we use the user@host.domain part to know that we are not
creating the same key twice to name two different things.
So, instead of red-hat, your machine should be named red-hat.com.
To verify the rename worked, use the
bk gethost
command.
And in general, you can make sure BitKeeper is happy about this
sort of thing by running the
bk sane
command.
| |
|
Home 
Documentation