Answer by thp for HowTo: restore lost 3rd party apps settings after Update...
Here's a small utility that helps with carrying out the steps described in pycage's post: http://thp.io/2014/sailfish/harbour-migration-1.0.0-1.noarch.rpm Source code:...
View ArticleAnswer by thp for HowTo: restore lost 3rd party apps settings after Update...
Some explanation why the path was changed in the first place, why leaving the old things as-is wasn't an option (for architectural and/or time resource reasons) and what app developers and users can do...
View ArticleComment by rainisto
rm -rf part in there is dangerous, I would leave that out. And just replace it with "mkdir -p $dir/$name"
View ArticleComment by ossi1967
(But: After checking for duplicates in the list that might have caused the old settings to be deleted, running the script worked fine and saved me a lot of manual work.)
View ArticleComment by ossi1967
Yes, I think there's a problem with the script when there was more than just one directory in the /home/nemo/.local/share/harbour-myapp/ path. Tidings, for example, had bot QML/ and .QtWebKit there,...
View ArticleComment by ZeiP
Doesn't this mean that the command would remove the QML directory for good, since it's first transferred to /home/nemo/.local/share/harbour-webcat/harbour-webcat which is on the next row rm -rf:d again?
View ArticleComment by veskuh
@pycage At least on my device this would skip friends and tweetian and that is correct behavior since this issue did not affect those.
View ArticleComment by pycage
@veskuh No, not 100% sure, so it's always a good idea to verify the echo output before firing the gun.
View ArticleComment by veskuh
Are you sure that this does not move stuff for apps that were not affected?
View ArticleAnswer by pycage for HowTo: restore lost 3rd party apps settings after Update...
Thought I'd share... Close the affected apps first. For copy & paste: for d in `find /home/nemo/.local/share/harbour-* -mindepth 1 -maxdepth 1 \! -newer /`; do dir=`dirname $d`; name=`basename...
View ArticleComment by tokaru
@Kaacz: have a look at the link above, line 91 of `src/sailfishapp_priv.cpp`. Obviously there are cases when the app name is used as organization name, probably when the app developer did not provide...
View ArticleComment by rcasta74
I can see another difference: new folders are created with 'nemo' group owner, instead older ones have 'privileged' group owner. [nemo@localhost share]$ ls -ld harbour-webcat/{,harbour-webcat/}QML...
View ArticleComment by Kaacz
@tokaru I don't see "organization name / application name". We all see "application name / application name" .. This is ugly and i still mean: "somewhere is something wrong!" => Bug.
View ArticleComment by simosagi
I also think that OTA upgrades should NEVER mess with user data. As solution seems relatively simple, IMHO it would have been better if the issue was mentioned before the upgrade, and that a conversion...
View ArticleComment by canne
Why not make a symbolic link back to the original config directory, this way the double path, if it will ever be backported, will not affect the original location. Like this, example with SailOTP cd...
View ArticleComment by stozze
Indeed, hope they release a hotfix for this. Not everyone wants to mess around with developer mode and ssh.
View ArticleComment by tokaru
@Kaacz, actually it seems to be organization name / application name, so I do not think this is a bug (even though the files should have been moved during the upgrade).... see...
View ArticleComment by Kaacz
Will be good to get fixed ASAP by Jolla. IMHO this look like a new bug - doubled field in path. :)
View ArticleComment by stozze
Yepp, easy fix, but it should not have happened in the first place imao, kinda critical issue really :/
View Article