On 7/28/07, Daniel Rall <email@example.com> wrote:
> > * build/generator/swig/checkout_swig_header.py:
> > (): Restore deleted file.
> > (checkout): Remove "long long" hacks which were obsoleted by r25740.
> David, this commit breaks invocation of gen-make.py:
> I haven't looked into the details, but reverting this commit removes this
It looks like my Subversion client somehow left out
"build/generator/swig/checkout_swig_header.py" when I committed
r25877. This looks like a bug in Subversion trunk. (I'm using
Subversion trunk from July 14.)
When I first committed my changes, Subversion said the following:
[djames@svn2 trunk]$ svn commit
svn: Commit failed (details follow):
svn: Your file or directory 'build.conf' is probably out-of-date
svn: The version resource does not correspond to the resource within
the transaction. Either the requested version resource is out of date
(needs to be updated), or the requested version resource is newer than
the transaction root (restart the commit).
svn: Your commit message was left in a temporary file:
After seeing this message, I typed 'svn up', and committed my changes again:
[djames@svn2 trunk]$ svn commit -F svn-commit.tmp
Transmitting file data ....
Committed revision 25877.
Notice that Subversion forgot to add checkout_swig_header.py? Looking
over the complete log of my session, I see that Subversion actually
marked checkout_swig_header.py as deleted in my working copy when I
typed 'svn up':
[djames@svn2 trunk]$ svn up
Yikes! It looks like my update got deleted when I typed 'svn up'.
Fortunately, 'checkout_swig_header.py' was still present in my working
copy, but, unfortunately, it wasn't marked as 'added' anymore.
I've attached a longer log of my session (which includes the output of
svn --version, and the full log of the update) as
P.S. (It looks like Justin re-added checkout_swig_header.py in r25880.
I committed the rest of my changes to the file in r25883.)
Received on Sun Jul 29 19:44:31 2007
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com