Yeah, and I've got it locally. Don't know how I missed it with find and locate.

However, the SVN version (and therefore the local checkout) is 2 months old code, while that version attached to the Mantis bug is different. So to rephrase that question more precisely, how come the current version of sync_pluto2amp.pl is not in SVN?

However, the SVN version (and therefore the local checkout) is 2 months old code, while that version attached to the Mantis bug is different. So to rephrase that question more precisely, how come the current version of sync_pluto2amp.pl is not in SVN?

How did you get the "2 months old code" information? My log shows that last two updates were at:r19507 2008-01-25r19474 2008-01-22correspondingly.

However, the SVN version (and therefore the local checkout) is 2 months old code, while that version attached to the Mantis bug is different. So to rephrase that question more precisely, how come the current version of sync_pluto2amp.pl is not in SVN?

How did you get the "2 months old code" information? My log shows that last two updates were at:r19507 2008-01-25r19474 2008-01-22correspondingly.

everything that I wrote, was about svn.linuxmce.org repository. It is in sync with Mantis version, as I explained in previous reply.

How come the Mantis and svn.linuxmce.org versions have different MD5sums?

Please re-read this comment:http://forum.linuxmce.org/index.php?topic=4030.msg23777#msg23777 - I have replied there, pointing that version before-the-latest is the same as Mantis version.

Ah, you mean "in sync" as in "common at the time of their creation". And the SVN has been updated since the time the Mantis version was posted. Clearer now. The real problem was that I've been browsing the CharonMedia SVN.