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.

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

FIX(client): Data dir migration issues #5593

Merged
merged 2 commits into from
Mar 16, 2022

Conversation

Krzmbrzl
Copy link
Member

This PR contains fixes related to the migration of the data directory as performed
in #5531.

The following issues are fixed

  1. The database wouldn't be found on Windows, after the migration has been performed (after having restarted Mumble once)
  2. Plugin settings were lost due their explicit dependence on the plugin's path

Checks

When the DB is migrated, it won't be found anymore after a restart,
because the new DB location was not saved in the settings.

This commit makes sure that during the migration, the path stored in the
settings gets updated and then subsequently saved.

Because of this, the dedicated migration code block in the Database
class is no longer needed (at the point it runs, the DB setting has
already been migrated) and was therefore removed.
@Krzmbrzl Krzmbrzl added client bug A bug (error) in the software labels Mar 12, 2022
When migrating the data directory, the plugin settings have been let
untouched. However, since these contain the plugin's absolute path (both
as a immediate property and also in the hash identifying the plugin),
the settings wouldn't apply to the migrated plugins. Therefore, the
migration would lead to a loss of plugin settings.

This commit adds dedicated code that remedies this situation by
explicitly adapting the plugin settings to the migrated plugin paths.
@Krzmbrzl Krzmbrzl merged commit b8cd0be into mumble-voip:master Mar 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug A bug (error) in the software client
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants