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

Synchronized directory path containing symlink #1037

Open
GammaRBurst opened this issue Jan 5, 2025 · 1 comment
Open

Synchronized directory path containing symlink #1037

GammaRBurst opened this issue Jan 5, 2025 · 1 comment

Comments

@GammaRBurst
Copy link

Issue


Summary

I own two computers, a desktop from when I'm at home, and a laptop for when I travel. I'm using MEGAsync to synchronize the saves directory of a game I'm playing, so that I can play on both computers using always the latest saves. This works well in general, but there is an issue with games coming from Snap.

Snap programs are all organized in the same way. The directory ~/snap contains all the Snap programs. Each Snap program contains (usually) four directories: the latest version (usually a number, e.g. 1234), the previous version, a common directory, and a symlink to the latest version directory. Every time a Snap program is updated, the previous version directory is removed, the newest version directory is added, and the symlink is updated to point to the newest version.

I'm trying to share a directory like ~/snap/game/latest/saves, but every time I do this, latest is automatically replaced with the currently latest version of the game. When the game is updated, the saves are automatically copied to the newest version, including the MEGAsync config files inside the saves directory, but since the synchronization is explicitly locked on the now previous version, the saves are not synchronized anymore.


What did you expect to happen?

I expect that MEGAsync would not automatically convert symlinks in shared directory paths. It should either ask if I want to use the real path, or not convert the path altogether.


Environment Details

Provide details about the environment where the issue occurred.

  • OS: Ubuntu MATE 24.04 on both computers
  • MEGASync Version: 5.3.0 and all previous versions of the last couple of years
@mfm-mega
Copy link
Contributor

Good afternoon,

We have studied your case and have been able to reproduce it.

Our system syncs the folder that the symlink points to, not the symlink itself, so when the game is saved and the symlink is modified, our system continues to sync the old folder as long as it is not deleted.

We know there is currently no way to fix this other than recreating the sync every time you save the game, so we are going to implement improvements so that the application itself detects when the local sync folder changes and offers you an easy way to update the local sync path without recreating the sync, keeping the sync state intact.

You will see this improvement in the near future.

Thank you very much and sorry for the inconvenience.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants