On 25 Feb 2003, Karl Fogel wrote:
>
> Note that there was some weird noise in the output. Before every
> revision it would report a conflict:
>
> CONFLICTS: '_e08d0f08_p_char'
> new revision: 8
>
> However, that code in cvs2svn.py is, shall we say, subject to
> examination at the moment. It reads:
>
> conflicts, new_rev = fs.commit_txn(txn)
>
> # set the time to the proper (past) time
> fs.change_rev_prop(t_fs, new_rev, 'svn:date', date, c_pool)
>
> ### how come conflicts is a newline?
> if conflicts != '\n':
> print ' CONFLICTS:', `conflicts`
> print ' new revision:', new_rev
>
> There seems to be some type conversion lossage going on here; since
> the revisions did keep incrementing, I don't think there was ever an
> actual conflict.
>
> But anyway, that's all a separate problem from what you reported,
> which was far more severe.
>
I've seen this too. In fact I wrote 3 emails about 4 weeks ago on this.
I guess everyone was a little to busy to pay attention at the time.
http://subversion.tigris.org/servlets/ReadMsg?list=dev&msgNo=30456
This message has a script attached that shows more examples of this bug.
Another message in that thread has a potential patch to fix it.
In the current bindings SOME functions that have "const char **" parameters return Pythong string
objects and some do not (they return that *_p_char crap instead). From the digging around I did,
it looked like they ALL should work the same way. That was what my patch did.
Thanks,
Marshall White
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Feb 26 20:51:27 2003