On 7/31/06, Jeffrey Chang <firstname.lastname@example.org> wrote:
> On 31/07/06, Garrett Rooney <email@example.com> wrote:
> > On 7/31/06, Jeffrey Chang <firstname.lastname@example.org> wrote:
> [cut description of problem: svn:author gets set to ^C]
> > > 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?
> Top priority is to make the problem go away, permanently. Figuring
> out how it got there would be a bonus.
> > 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.
> Yes, that works. I can fix the properties file by hand, and the
> repository then appears to work normally.
> This occurs every time I check files into the repository. So the
> procedure now is to svn commit, fix the revision properties, move the
> broken .svn/log, svn cleanup, and svn update to update the revision
> number (which didn't get updated in the broken svn commit); which is
> too painful to do every time.
> It appears that this error occurs only over file:// and not over
> svn+ssh://. Since it looks like tracking down the problem will be
> difficult, maybe I'll just switch over to svn+ssh. Are there any
> relatively easy tests I can do to see where the author might be
> getting messed up when accessing with file://?
Well, if I had to guess it's that your username is being cached as ^C
in ~/.subversion/auth/svn.username (which is used by file:// not
svn+ssh://), and you're using an old enough version of svn that it
doesn't validate that usernames shouldn't contain control characters.
Or, alternatively, I'm mistaken and there is no validation of
usernames, but I'm pretty sure there is. I know we have validation on
other properties, since I've tracked down related problems in the
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Mon Jul 31 20:43:39 2006