You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have some packages which are both installed locally and stored in a backup, but the backup contains newer versions as is indicated in the backup diff. When I restore the backup, I get a successful restore notification, but packages are still in the same outdated versions as previously and the backup diff is still the same. Although new packages have been successfully installed during the restore.
#3336
Closed
lizzby opened this issue
Mar 28, 2021
· 0 comments
I have some packages which are both installed locally and stored in a backup, but the backup contains newer versions as is indicated in the backup diff. When I restore the backup, I get a successful restore notification, but packages are still in the same outdated versions as previously and the backup diff is still the same. Although new packages have been successfully installed during the restore.
When I open Updates in the Atom Settings, all three packages are listed there with the same versions as listed in the backup diff:
Is the backup restore process supposed to update packages to newer versions?
Versions
OS: Windows 10 (the backup was created on MacOS 10.15.4)
I have some packages which are both installed locally and stored in a backup, but the backup contains newer versions as is indicated in the backup diff. When I restore the backup, I get a successful restore notification, but packages are still in the same outdated versions as previously and the backup diff is still the same. Although new packages have been successfully installed during the restore.
When I open Updates in the Atom Settings, all three packages are listed there with the same versions as listed in the backup diff:
Is the backup restore process supposed to update packages to newer versions?
Versions
Originally posted by @ferenczy in atom-community/sync-settings#614
The text was updated successfully, but these errors were encountered: