I saw this earlier today too the first time I ran collection status after upgrading from 0.5.18 to 0.6.01 on Python 2.5 and FreeBSD.
For some reason I am unable to reproduce it again, even after nuking ~/.cache. Possibly because I have tacked on a couple of 0.6.01 produced backup increments onto the backups.
I saw this earlier today too the first time I ran collection status after upgrading from 0.5.18 to 0.6.01 on Python 2.5 and FreeBSD.
For some reason I am unable to reproduce it again, even after nuking ~/.cache. Possibly because I have tacked on a couple of 0.6.01 produced backup increments onto the backups.