Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Migration from dirty.db seems to have bitrotted #29

Closed
kentonv opened this issue Sep 12, 2016 · 1 comment
Closed

Migration from dirty.db seems to have bitrotted #29

kentonv opened this issue Sep 12, 2016 · 1 comment

Comments

@kentonv
Copy link
Owner

kentonv commented Sep 12, 2016

Very-old etherpads can't be opened with the latest version.
@kentonv kentonv mentioned this issue Sep 12, 2016
Closed
@kentonv
Copy link
Owner Author

kentonv commented Sep 13, 2016

Problem is that the npm module ueberDB was renamed to ueberdb2. The reasons are not clear. The only documentation of this change appears to be a vaguetweet:

https://twitter.com/johnmclear/status/683454253856337920

kentonv added a commit that referenced this issue Mar 7, 2017
@kentonv
Fix migration of very-old etherpads.
69cf1ec 
I don't know why ueberDB's name changed.

The commit message does not explain it:

ether/ueberDB@423e40f

There is this tweet, and the tweets chronologically after it, but they just complain vaguely of an "npm issue" without explaining the issue:

https://twitter.com/johnmclear/status/683454253856337920

Fixes #29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@kentonv