[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn:author revision property set to ^C

From: Garrett Rooney <rooneg_at_electricjellyfish.net>
Date: 2006-07-31 20:12:43 CEST

On 7/31/06, Jeffrey Chang <jeffrey.t.chang@gmail.com> wrote:
> Hello,
> I am using an FSFS-based SVN repository using svn 1.2.1 on linux. The
> repository is on a nfs-mounted drive. I am accessing it via local
> file (file://), and I am the only user of this repository.
> A few days ago, I started seeing an odd behavior where when I "svn
> commit" changes to the repository, the command fails with an error:
> [... commit messages]
> Transmitting file data .svn: Commit succeeded, but other errors follow:
> svn: Error bumping revisions post-commit (details follow):
> svn: Malformed XML: not well-formed (invalid token) at line 6
> I tracked this down to the .svn/log file containing an ETX (^C) character:
> <modify-entry
> committed-rev="1740"
> name="filefns.py"
> committed-date="2006-07-31T13:40:15.040549Z"
> last-author="^C"/>
> The svn:author revision property in the <repository>/db/revprops/1740
> file is similarly set incorrectly:
> svn:author
> V 1
> ^C
> K 8
> That directory within the repository is locked and won't clean up
> until I remove the log file and fix the revprops by hand.
> Since this problem just started a few days ago, I suspect that the
> problem stems from the network upgrades made at the same time
> (although arguably svn should check to make sure the values it
> receives will not generate files that muck up the repository).

In theory svn does verify that properties it sets (like svn:author)
won't muck up the repository. If you've found a way to get control-c
in as svn:author, you've found a bug.

> Where does the value of svn:author come from? Where would be a good
> place for the IT folk to begin looking? I am using default
> pre-revprop-change and other scripts, so those should not be affecting
> the value.

What exactly are you trying to do? Debug how it got there in the
first place? Or just make the problem go away?

If it's a fsfs repository it's not that hard to make the problem go
away (svn pset over file:// should be able to do it, if you've got a
pre-revprop-change hook that allows modification of svn:author,
alternatively you can tweak the revision's properties file on disk by
hand). Tracking down where the problem came from is far more work.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jul 31 20:14:30 2006

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.