Fixed libbe.storage.util.upgrade
authorW. Trevor King <wking@drexel.edu>
Sun, 27 Dec 2009 20:58:29 +0000 (15:58 -0500)
committerW. Trevor King <wking@drexel.edu>
Sun, 27 Dec 2009 20:58:29 +0000 (15:58 -0500)
commit214c4317bb90684dcfdab4d2402daa66fbad2e77
tree8935072ad4ce8ddee2a7056412a7a89c96acf359
parent89b7a1411e4658e831f5d635534b24355dbb941d
Fixed libbe.storage.util.upgrade

Note that it only upgrades on-disk versions, so you can't use a
non-VCS storage backend whose version isn't your command's current
storage version.  See #bea/110/bd1# for reasoning.  To see the on-disk
storage version, look at
  .be/version
To see your command's supported storage version, look at
  be --full-version

I added test_upgrade.sh to exercise the upgrade mechanism on BE's own
repository.
.be/bea86499-824e-4e77-b085-2d581fa9ccab/bugs/1100c966-9671-4bc6-8b68-6d408a910da1/comments/bd1207ef-f97e-4078-8c5d-046072012082/body [new file with mode: 0644]
.be/bea86499-824e-4e77-b085-2d581fa9ccab/bugs/1100c966-9671-4bc6-8b68-6d408a910da1/comments/bd1207ef-f97e-4078-8c5d-046072012082/values [new file with mode: 0644]
.be/version
libbe/bug.py
libbe/storage/util/upgrade.py
libbe/storage/vcs/base.py
libbe/util/id.py
libbe/version.py
test_upgrade.py [new file with mode: 0755]