Re: SVN::Client not committing?

[Sandy]

Hello

Based only on my knowlege of SVN, I believe I know what the problem is:

After committing a working copy to the repository, the svn info shows that you are still at the last revision.

To update the information about your working copy (i.e. make it up-to-date with the repository) you must update.

I presume that there is an update method for SVN::Client?

So, try an update right after the commit, and see if that 'fixes' the problem.

Sandy

[zigdon]

Actually, I believe when you do an 'svn commit' from the command line, it does implicitly update the committed resources in the working copy. But I did add an '$svn->update' call at the end of the script, but the checking after the script runs, it still shows the directory as just "marked for adding":

$ svn info mkdir                
Path: mkdir
URL: file:///home/boger_d/lib/tmp/svn/test/mkdir
Revision: 0
Node Kind: directory
Schedule: add

$ svn update
At revision 1.

$ svn info mkdir                
Path: mkdir
URL: file:///home/boger_d/lib/tmp/svn/test/mkdir
Revision: 0
Node Kind: directory
Schedule: add

[duncs]

Was there any answer to this in the end? I am suffering from the same problem.

Duncs

[zigdon]

Sadly, I never did figure it out. Ended up writing the code in python, as the svn bindings there were more mature. Of course, it's been almost 2 years since then, so hopefully that is no longer the case.

[Avi]

not very great docs indeed.. the issue is the log_msg (nice that it doesn't report it).. use something like this instead:

    my $log_msg_handler = sub {
        my $stringptr = shift;
        $$stringptr = "testing mkdir";
        return 1;
    };
    $svn->log_msg($log_msg_handler);

That should do the trick -- hopefully this prevents someone pulling out their hair.