Empty branches.db breaks revisioner-cli

[Sean Hodges]

On first installation, running any commands other than "add" creates an empty branches.db, which in turn breaks the front-end.

The example below describes running "revisioner-cli help" twice:

sean@metis:~/Documents/Revisioner/src$ rm -r /home/sean/.revisioner/branches.db
sean@metis:~/Documents/Revisioner/src$ revisioner-cli help
Revisioner CLI version 0.1
Usage: revisioner <command>
List of available commands:
 help - Display this help message
 add - Add a new branch
 remove <branch name> - Remove an existing branch
 push <branch name> - Push new revisions of the specified branch
 push-all - Push new revisions of all managed branches
 pull <branch name> - Pull new revisions of the specified branch
 pull-all - Pull new revisions of all managed branches
 info <branch name> - Display info about the specified branch
 list - List all managed branches
sean@metis:~/Documents/Revisioner/src$ revisioner-cli help
Traceback (most recent call last):
  File "/usr/bin/revisioner-cli", line 82, in <module>
    cli = CLI()
  File "/usr/bin/revisioner-cli", line 24, in __init__
    self.load()
  File "/usr/bin/revisioner-cli", line 33, in load
    self.branches = pickle.load(db)
  File "/usr/lib/python2.5/pickle.py", line 1370, in load
    return Unpickler(file).load()
  File "/usr/lib/python2.5/pickle.py", line 858, in load
    dispatch[key](self)
  File "/usr/lib/python2.5/pickle.py", line 880, in load_eof
    raise EOFError
EOFError

Work-around:

Delete the broken ~/.revisioner/branches.db and ensure your first command is "revisioner-cli add"

[Hendrik Kaju (hkaju)]

Fixed in revision 12