verify command should print session *names* and list should accept "N" (session number) as an argument

[GoogleCodeExporter]

When running the verify command on my repo boar indicated a file was missing 
when scanning session 2. To the best of my knowledge there is no way to obtain 
any information about what session "session 2" without knowing the session name.

So either verify should output the session name along with the session number, 
or list should accept a N argument and return information about the 
session/session name that it corresponds to. I think both enhancements would 
improve usability

The idea being when you see an error along the lines of session 2: {hex-digest} 
missing, you can do a "boar list 2", to see information the session the 
session/2 folder corresponds to, and then you can do a "boar find {hex-digest}" 
command to get a hint about what file seems to have gone missing or become 
corrupt.

Also, along these lines, if for some reason a file becomes corrupt in the repo, 
there should be a way to *force* a reimport of a file explicitly. The idea 
being if you know that example.jpg became corrupt, and thru the list and find 
commands you determine the file in question is still sitting on your drive at 
/path/to/example.jpg. You should be able to force boar to reimport that file 
specifically even if it appears in the bloblist as being in the repo already. 
Alternately, there should be a way to strip a file from the bloblist (with many 
warning and bells) if the verify command detects that it is corrupt or missing.

The bloblists and the blob directory should always be in sync. There should be 
some mechanism exposed by boar to resolve these kinds of issues when boar 
discovers them.

Thanks :)

Original issue reported on code.google.com by cryptob...@gmail.com on 29 Feb 2012 at 10:56

[GoogleCodeExporter]

Btw, I realize you can browse to the sessions folder in the boar repo manually 
and view the session.json file that way. I meant there is no way to obtain that 
information from boar itself. 

Original comment by cryptob...@gmail.com on 29 Feb 2012 at 10:58

[GoogleCodeExporter]

About "verify" printing session names, yes that sounds like a good idea... But 
since this issue seems to be about several things, I'll just address these 
issues and close this one and open a new issue just for the session names thing.

Lots of ideas here... First of all, attempting reparation of repos is usually 
not a good idea, better to have a fresh clone available for drop in 
replacement. Although it is possible to manually repair a repo with a simple 
missing file, it is not what boar is designed for. The workflow with boar is 
something like "Create a repo. Maintain clones. When a repo fails, delete it 
and restore a clone". But sometimes things do not go according to plan. I'll 
email you privately about your corrupted repo.

Original comment by ekb...@gmail.com on 29 Feb 2012 at 12:37

• Changed state: Invalid