Reinstall nuked my existing KBs!!!

gnebbia / kb

A minimalist command line knowledge base manager

GNU General Public License v3.0

3.17k stars 104 forks source link

Reinstall nuked my existing KBs!!! #107

Closed dnorthup-ums closed 8 months ago

dnorthup-ums commented 1 year ago

Expected Behavior

Re-install to cope with OS upgrade, be able to use my existing KBs

Actual Behavior

It DELETED THEM.

Steps to Reproduce the Problem

Upgrade OS, therefore upgrading the system python
Find that KB doesn't work anymore
Re-install KB via pip
Find that KB re-install removed completely the existing store of KBs

Specifications

(Note, this is kinda useless in this case, but whatever)

Version: NEW is latest, today (2023-05-16), from pip (pre-upgrade may have been 0.1.6, current seems to be 0.1.7; I don't trust it anymore)
Platform: Was F36, Now F37
Subsystem: ????

dnorthup-ums commented 1 year ago

Note, it is going to take me at least 8 hours to regenerate this information, at best, so I'm very angry right now.

dnorthup-ums commented 1 year ago

I found the answer, and I'm still not pleased. If a package is going to completely abandon the previous data storage location (in 0.1.6 and earlier: ~/.kb) then upon upgrade it must check the previous location for data and migrate it to the new location instead of creating a new data store from scratch. If I find the neurons to do the python-fu I'll let you know. More than anything else, I'm leaving this here in case somebody else has the same problem I did.

gnebbia commented 8 months ago

Sorry you are completely right! I should write a note somewhere with this! Tried to change this at an early stage but still it affected some users.