Fully updated the SVN-way but still 11709

[Bob]

Good day,

Every time when there's a new update for aMSN I update it the following way:

- cd /Applications/aMSN.app/Contents/Resources/
- sudo rm -rf Scripts
- /opt/subversion/bin/svn co https://amsn.svn.sourceforge.net/svnroot/amsn/trunk/amsn Scripts

At the end of the process it tells you the new SVN-version. Earlier today it was 11723 but when I click in the menu on aMSN/About aMSN, it says the current SVN- version is 11709. This has been for days now. Am I missing something , do I something wrong? Please enlighten me.

Fyi: running Mac OS X.4.11

[BW]

Hi Bob,

as you can see here
the directory amsn is still at 11711, so this would be the correct number to be
shown in the aMSN/About window according to the version of the last file changed,
BUT only some .tcl files are used to determine at which version we are,
(non of the files in the plugins directory are taken into account)
and as you can see here 11711 and here 11710
only /lang/langit and plugins/winks/winks.tcl have been changed

more about that here


I hope that answers you question

and btw as you can see here
there is no need to remove and re-download the hole scripts directory every time you
want the newest version, just in case you didn't know that

EDIT @arantes: thx for the summary

[arantes]

More clearly, the number shown in "about" is changed only when certain files are updated(TCL). If there is a new revision updating some other files (like binaries) it won't be shown in about

Edit : Super Power User \o/

[kakaroto]

BW and arantes (congrats on super power user status) explained it well.. I'll just add that when you want to update, just do this :

- cd /Applications/aMSN.app/Contents/Resources/Scripts
- /opt/subversion/bin/svn update

it's much simpler and it will take a LOT less time (and will also tell you what exactly was updated).

[Bob]

Thanks for the insight, chaps.
Updating as was suggested in the previous was quick but I am sad to say that all aMSN data is gone. Is this common when updating aMSN as suggested in the previous post?
The size of the aMSN application folder is now 40kb. Everything is gone. Profiles, chat logs, settings, the lot. Is there a way to retrieve this data without going through a back-up? To be honest, I'm rather sad that all data is gone.

[kakaroto]

Humm.. no, it's definitely not normal, I think you may be mistaken, What you did is to update /Application/aMSN.app while your profiles, chat logs, etc.. are stored in $HOME/Library/Application support/amsn which has nothing to do with /Applications/aMSN.app.. also, your old method was actually deleting stuff (rm -rf) while this method doesn't delete anything (although the other method you used wouldn't delete your profiles either). I think you may have done something wrong, most probably just misinterpreted something...  but in any case, there's no way it would have deleted your profiles. Make sure you're not wrong..
in the very improbable worst case scenario where everything magically disappeared, then I guess that no, there's no way to get it back without a backup.

[Bob]

I'm aware what is updated (and where it is stored), the app aMSN and not profiles, chat logs or other user-generated data.

In the old days, I updated aMSN by downloading the SVN snapshot from the Download page. I did that every day and I have never had what I have experienced earlier today.
A few weeks ago I started to update aMSN as explained in the first post. I did that each time (untill yesterday) there was an update and I have never had what I have experienced earlier today. All data was intact.
Today I have updated aMSN the way as was suggested by kakaroto. I copied & pasted the lines into the terminal and it did all the steps as it did with the precious method. No errors, typos or other unwanted things occured. Nothing was updated. SVN is still 11723. I opened aMSN and it showed me a window with the current SVN-number. This only happens when you have installed the app with the installer. You know the rest of the story.

[kakaroto]

Humm... yes, well, did you check your Home/Library/Application support/amsn directory for profiles ? I really don't know what could have happened, you know it yourself, it can't be the svn command that did that, something else did..
Check the profiles directory to make sure everything is in there, what could have happened is somehow, for some unknown mystical reason, amsn can't read your profiles directory (or it's running or thinks it's running as a different user), and it creates a separate profile directory (would be in /Applications/aMSN.app/Content/Resources/Scripts/amsn_config/ )