| 1 |
% bup-validate-object-links(1) Bup %BUP_VERSION% |
| 2 |
% Rob Browning <[email protected]> |
| 3 |
% %BUP_DATE% |
| 4 |
|
| 5 |
# NAME |
| 6 |
|
| 7 |
bup-validate-object-links - scan the repository for broken object links |
| 8 |
|
| 9 |
# SYNOPSIS |
| 10 |
|
| 11 |
bup validate-object-links |
| 12 |
|
| 13 |
# DESCRIPTION |
| 14 |
|
| 15 |
`bup validate-object-links` scans the objects in the repository for |
| 16 |
and reports any "broken links" it finds, i.e. any links from a tree or |
| 17 |
commit in the repository to an object that doesn't exist. Currently, |
| 18 |
it doesn't include "loose objects" (those not in packfiles -- which |
| 19 |
git may create, but bup doesn't), and it can't handle tag objects |
| 20 |
(which bup also doesn't create). |
| 21 |
|
| 22 |
Whenever a broken link (missing reference) is found, an ASCII encoded |
| 23 |
line formatted like this will be printed to standard output: |
| 24 |
|
| 25 |
no MISSING_HASH for PARENT_HASH |
| 26 |
|
| 27 |
# EXIT STATUS |
| 28 |
|
| 29 |
The exit status will be 1 if any broken links are found, 0 if none are |
| 30 |
found, and some other positive integer for other failures. |
| 31 |
|
| 32 |
# SEE ALSO |
| 33 |
|
| 34 |
`bup-fsck`(1) |
| 35 |
|
| 36 |
# BUP |
| 37 |
|
| 38 |
Part of the `bup`(1) suite. |