When the weeder asks the repository to perform its
portion of weeding, the repository performs a sort-and-
merge of the derived shortid files to keep and the source
shortid files to keep. It uses an external program
(sidsort) to do this. That program can fail in cases of
low disk space. (sidsort is just a shell script that
invokes the sort(1) command, which uses temporary files
as it works.) If it does, the repository returns an error
to the weeder indicating that it failed to do its part of
weeding. When this happens, the weeder prints a
message like this:
03:35:06.152 10/28/2004 -- Fatal repository error
Derived weed error = 22
However, when this happens the weeder still exits with
successful status. This really should cause the weeder
to exit with a non-zero status to indicate to the caller
that something has gone wrong.
Logged In: YES
user_id=291223
The number "22" in the example is really an errno and there
should be a text error message.