Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
C
ceders-lyskom-server
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Per Cederqvist
ceders-lyskom-server
Commits
b5b2a6e1
Commit
b5b2a6e1
authored
25 years ago
by
Per Cederqvist
Browse files
Options
Downloads
Patches
Plain Diff
Recommend running dbck when upgrading from 2.0.0.
parent
c6fd5044
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
README
+7
-0
7 additions, 0 deletions
README
with
7 additions
and
0 deletions
README
+
7
−
0
View file @
b5b2a6e1
...
...
@@ -143,6 +143,13 @@ AUTHORS List of authors.
4. Database Versions -- you may have to convert the database
============================================================
The database format has not changed in the 2.0.1 release. However,
there was a bug in the 2.0.0 release that may have caused the database
to contain errors. They can be fixed by dbck; please run this command
if you are upgrading from the 2.0.0 release:
dbck -i
lyskomd version 2.0.0 uses a new file format for the database. If you
have been running earlier versions of lyskomd you must convert the
database by issuing the following command:
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment