BK-CHECK(1)

🌸 NAME 🌸

okay so this page is bk check, and the header up top literally reads bk check(none) from the BitKeeper User’s Manual — cute, iconic, no notes. what it does, in one line: check repository for consistency. that's the whole assignment bestie 💅

---

✨ SYNOPSIS ✨

bk −r check [−acdefgpRvw]

---

🦋 DESCRIPTION 🦋

so check exists to make sure your repository is in a consistent state, and honestly it's giving vibe check for your entire repo. here's the lore: a repository contains files, and each file may have multiple versions. groups of versions are called changesets (csets, for the girlies in a hurry). every cset gets recorded in the ChangeSet file. the ChangeSet file points at the set of deltas in the set of files. there are no back pointers, but the files do record the point at which each cset occurs — and yeah, there can be multiple deltas in a file that all belong to one cset, and the marker records the cset boundary. iykyk 🔥

since csets propagate between repositories, it is important that the ChangeSet file is correct — like, main character energy levels of important. bk check is used to make sure nothing has gone wrong (and if it has, it gives you a rough idea of how to fix it). 🫶

currently, the following are checked:

• for each file specified, make sure that deltas marked as recorded in the ChangeSet file are recorded in the ChangeSet file.
• for each file specified and for each delta of that file which is recorded in the ChangeSet file, make sure that the delta exists in the file.
• for each file specified, make sure that the file has no unresolved branches.
• make sure that every delta recorded in ChangeSet file is in the repository (only with -a).

okay so yes, you can specify a list of files instead of using bk -r to get all of them — but this is not recommended. ngl, just don't. 🙈

---

🎀 OPTIONS 🎀

• -a — ensures that the ChangeSet file and the repository agree on what files are in the repository; also ensures that the ChangeSet and other files agree on where they are in the repository history timeline. lowkey the big one ⭐
• -c — check file and the per delta checksums. heads up though: only the most recent delta’s checksum is checked, so if you wanna check all of the checksums, see bk checksum. 💅
• -d — provide more details about what is wrong. mainly for debugging. not me reading the extra lore 🍓
• -e — check for end of line (eoln) inconsistencies in text files. typically used with the -a option. this will check to make sure that:
  • the state of the EOLN_NATIVE flag in each sfile is consistent with what is set in the BitKeeper/etc/config file (see bk admin).
  • a bk file on a win32 operating system that has the EOLN_NATIVE flag set has the expected line termination: \r\n
  • a file on a UNIX operating system has the expected line termination: \n
  • a file that does not have the EOLN_NATIVE flag has the expected line termination: \n
• -f — fix any fixable errors. this option will renumber incorrectly numbered revisions, put incorrectly located files where they belong, reconstruct corrupted xflags metadata, and add missing changeset backpointers. and bestie, this option is on by default if the auto_fix config option is set. 👑
• -ff — fix any fixable errors which have destructive fixes. this option will remove any old line‑of‑development (LOD) information except the 1.x LOD. > ⚠️ destructive means destructive, babe — it's deleting stuff on purpose. proceed with your whole chest but maybe read twice 💀
• -g — list each missing file as the file’s identifier (root key), but do not produce any other output. typically used as input to the bk gone command. ✨
• -gg — list each missing delta key, but do not produce any other output. typically used as input to the bk gone command. ✨✨
• -ggg — list both missing files and missing deltas. typically used as input to the bk gone command. ✨✨✨ the trilogy, ate
• -p — list deltas which are in more than one changeset. 🦋
• -R — only do checks which make sense in the RESYNC dir. 💜
• -v — be more verbose. each -v adds additional verbosity. with just one, bk check will display a progress bar (slay, a progress bar 🎀). with two, bk check will list each file which is OK. more than two is for debugging only. without the -v option, there is no output if the repository is OK; there is only output if things are broken. silence = good news, fr fr 🤫
• -w — list files which are writable but not locked. 🔥

---

🌈 SEE ALSO 🌈

bk‐admin, bk‐checksum, bk‐config‐etc, bk‐gone, bk‐log, bk‐xflags

---

⭐ CATEGORY ⭐

Repository

---

and that's the whole page, bestie 🫶 this gem was brought to you by BitKeeper Inc, version 1E1, and the page itself goes by bk check(none) — go forth and have a consistent repository, you've got this 💖✨🎀