[svk-users] "Transaction is out of date" in smerge?
Mark Eichin
eichin at metacarta.com
Wed Feb 13 17:37:43 EST 2008
Anyone seen anything like this:
> Transaction is out of date: Out of date: '/branches/eichin/monster-merge-trial-1/XXX/YYY in transaction '72190-1'
> Please sync mirrored path /mirror/all/branches/eichin/monster-merge-trial-1 first.
in smerge (or anything else where the "please sync" message both
doesn't help, and doesn't make any sense?) Pasting a die in to the
"Please sync" handler gets me this traceback:
> at SVK::Command::Commit::__ANON__(/usr/share/perl5/SVK/Command/Commit.pm:309)
> at SVK::Command::handle_error(/usr/share/perl5/SVK/Command.pm:946)
> at SVK::Command::__ANON__(/usr/share/perl5/SVK/Command.pm:187)
> at <eval>(/usr/lib/perl5/SVN/Delta.pm:173)
> at SVN::Delta::Editor::AUTOLOAD(/usr/lib/perl5/SVN/Delta.pm:173)
> at SVK::Editor::ByPass::AUTOLOAD(/usr/share/perl5/SVK/Editor/ByPass.pm:87)
> at SVK::Editor::MapRev::AUTOLOAD(/usr/share/perl5/SVK/Editor/MapRev.pm:80)
> at SVK::Editor::ByPass::AUTOLOAD(/usr/share/perl5/SVK/Editor/ByPass.pm:87)
> at SVK::Editor::ByPass::AUTOLOAD(/usr/share/perl5/SVK/Editor/ByPass.pm:87)
> at SVK::Editor::Delay::apply_textdelta(/usr/share/perl5/SVK/Editor/Delay.pm:111)
> at SVK::Editor::Merge::apply_textdelta(/usr/share/perl5/SVK/Editor/Merge.pm:451)
> at SVK::Editor::Copy::apply_textdelta(/usr/share/perl5/SVK/Editor/Copy.pm:288)
> at SVK::Editor::Delay::apply_textdelta(/usr/share/perl5/SVK/Editor/Delay.pm:111)
> at SVK::XD::depot_delta(/usr/share/perl5/SVK/XD.pm:860)
> at SVK::Merge::run(/usr/share/perl5/SVK/Merge.pm:699)
> at SVK::Command::Merge::run(/usr/share/perl5/SVK/Command/Merge.pm:234)
> at SVK::Command::Smerge::run(/usr/share/perl5/SVK/Command/Smerge.pm:74)
> at <eval>(/usr/share/perl5/SVK/Command.pm:222)
> at <eval>(/usr/share/perl5/SVK/Command.pm:220)
> at SVK::Command::run_command(/usr/share/perl5/SVK/Command.pm:200)
> at App::CLI::dispatch(/usr/share/perl5/App/CLI.pm:79)
> at <eval>(/usr/share/perl5/SVK/Command.pm:164)
> at SVK::Command::invoke(/usr/share/perl5/SVK/Command.pm:164)
> at main::(/usr/bin/svk:169)
The actual (sanitized) path in the original message doesn't actually
matter - based on a comment elsewhere in the list, I cleaned out
$SVKROOT/cache and the path changed (repeating the command gives a
consistent report, but clearly something odd is going on if nuking the
cache changes it, and the point where it fails seems fairly random
anyway - in the middle of a large directory, as it turns out.)
I'm poking around trying to reproduce a similar demo-repository (even
if it weren't proprietary, $SVKROOT/local is 56G so it isn't going
anywhere :-) but smaller cases have been succeeding... I'm asking at
least partly because someone might have a less tangled example...
More information about the svk-users
mailing list