You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Quinn Taylor <qu...@mac.com> on 2009/12/08 22:33:49 UTC
RE: Re: Invalid change kind in rev file
> > I traced this down to the new format of the changes file which
> > now includes node-kinds (e.g. modify-file) which the old svnlook
> > cannot parse.
> >
> > Is this an unsupported configuration or do we need to check a
> > version number whether or not to write node-kinds to that file?
> If this is true, it sounds like a bug. The Subversion promise is that
> any 1.x client will work with any 1.x server, and it sounds like
> you've found a case where this is not true.
Has anyone figured out the cause of this, or happen to know which versions of SVN are affected? We've run into this while trying to upgrade our work servers from 1.4.4 to 1.6.6, and it causes our pre-commit hooks to fail in our test environment. I'm really pushing for the auto merge-tracking features in 1.5+ and want to use the most recent version possible, but this is a troubling problem. Is there an SVN bug filed for this, and hopefully a workaround or patch for the time being?
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2428700
Please start new threads on the <us...@subversion.apache.org> mailing list.
To subscribe to the new list, send an empty e-mail to <us...@subversion.apache.org>.
Re: Re: Invalid change kind in rev file
Posted by Stefan Sperling <st...@elego.de>.
On Tue, Dec 08, 2009 at 02:33:49PM -0800, Quinn Taylor wrote:
> > > I traced this down to the new format of the changes file which
> > > now includes node-kinds (e.g. modify-file) which the old svnlook
> > > cannot parse.
> > >
> > > Is this an unsupported configuration or do we need to check a
> > > version number whether or not to write node-kinds to that file?
>
> > If this is true, it sounds like a bug. The Subversion promise is that
> > any 1.x client will work with any 1.x server, and it sounds like
> > you've found a case where this is not true.
Since repositories usually don't auto-upgrade, a 1.4.x-style repository
should stay at 1.4.x-style format even if a 1.6.x server is used to access
the repository. It should still be usable with a set of real 1.4.x
binaries.
> Has anyone figured out the cause of this, or happen to know which
> versions of SVN are affected? We've run into this while trying to
> upgrade our work servers from 1.4.4 to 1.6.6, and it causes our
> pre-commit hooks to fail in our test environment.
Please provide much more information. Nobody will be able to reproduce
the problem in their environment from what you have described so far.
We need to independently reproduce the problem to understand it.
Can you provide a list of commands that starts off with creating
an empty repository and ends with the problem you are seeing?
Since you may need to use multiple versions of Subversion binaries to
trigger the problem, please be clear about what version of svnlook is
running in the hook, what version of svnadmin is used to create the
repository, and which svn client version is used to commit to the
repository, and the type of URL the client is using (e.g. file:// URL).
Best, post a complete transcript of a command line session reproducing
the problem, with the output of svn{look,admin} --version at appropriate
places.
> I'm really pushing
> for the auto merge-tracking features in 1.5+ and want to use the most
> recent version possible, but this is a troubling problem. Is there an
> SVN bug filed for this, and hopefully a workaround or patch for the
> time being?
Once we know more, we can probably tell you what you need to do to
get rid of the problem, and whether there's a bug.
Thanks,
Stefan
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2428754
Please start new threads on the <us...@subversion.apache.org> mailing list.
To subscribe to the new list, send an empty e-mail to <us...@subversion.apache.org>.
RE: Re: Invalid change kind in rev file
Posted by "Michael P. Reilly" <ar...@gmail.com>.
Quinn Taylor wrote:
>
>> > I traced this down to the new format of the changes file which
>> > now includes node-kinds (e.g. modify-file) which the old svnlook
>> > cannot parse.
>> >
>> > Is this an unsupported configuration or do we need to check a
>> > version number whether or not to write node-kinds to that file?
>
>> If this is true, it sounds like a bug. The Subversion promise is that
>> any 1.x client will work with any 1.x server, and it sounds like
>> you've found a case where this is not true.
>
> Has anyone figured out the cause of this, or happen to know which versions
> of SVN are affected? We've run into this while trying to upgrade our work
> servers from 1.4.4 to 1.6.6, and it causes our pre-commit hooks to fail in
> our test environment. I'm really pushing for the auto merge-tracking
> features in 1.5+ and want to use the most recent version possible, but
> this is a troubling problem. Is there an SVN bug filed for this, and
> hopefully a workaround or patch for the time being?
>
I just ran in the issue myself. It deals with the assumption of the path
being set appropriately in the hooks. The previous manual install of
Subversion (1.5.x) that I was running was installed in /usr/local, the new
install (1.6.x) was from an RPM and installed to /opt/CollabNet_Subversion.
Even with using the CollabNet_Subversion Apache2 server, the PATH does not
automatically include /opt/CollabNet_Subversion/bin. So 'svnlook' looks in
the default path, which includes /usr/local/bin.
I changed my scripts to insert /opt/CollabNet_Subversion/bin at the
beginning of the path and they are now working appropriately.
This would probably be a problem with just about any system that went with
an manual install to an RPM/DEB install. The manual installs (using
configure) typically install to /usr/local, which would get picked up by
default, and the automated installs would install to an application specific
directory, which would need to be added to the path.
--
View this message in context: http://old.nabble.com/Invalid-change-kind-in-rev-file-tp23075826p26780284.html
Sent from the Subversion Users mailing list archive at Nabble.com.
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2430404
Please start new threads on the <us...@subversion.apache.org> mailing list.
To subscribe to the new list, send an empty e-mail to <us...@subversion.apache.org>.