svn: Invalid diff stream: insn 0 cannot be decoded

[Julian312]

Hello everybody,

here is my problem:

First, I create a brand new repository

Then, I import a directory into my repository with SVNKit using the sample code at

https://wiki.svnkit.com/Managing_A_Working_Copy (Step2)

After doing that, SVNCommitInfo.toString() gives me "r1 by 'user' at Fri Jun 06 14:12:17 CEST 2008" so everything seems to have worked all right.

But now, if I try to checkout my repository using the native SVN command line client, I get the following error:
"svn: Invalid diff stream: insn 0 cannot be decoded"
or sometimes also:
"svn: Invalid diff stream: [tgt] insn 1 starts beyond the target view position"
and the file I imported before is not there.

When I use the native command line client for import, checking out works normal. So I think the problem SVNKit related.

I am using:
Suse 9.3
Subversion 1.1.3 (is this sufficient for SVNKit?)
SVNKit 1.1.7 (Eclipse plugin)
JDK 1.6.0_06

Any idea what the problem is?
If possible, I want to avoid upgrading anything.

Thanks in advance

Julian

[Julian312]

Julian312 wrote:

But now, if I try to checkout my repository using the native SVN command line client, I get the following error:
"svn: Invalid diff stream: insn 0 cannot be decoded"
or sometimes also:
"svn: Invalid diff stream: [tgt] insn 1 starts beyond the target view position"
and the file I imported before is not there.

OK, when I use svn:// instead of file:// to access my repository with SVNKit, then everything works. Is this a bug in SVNKit?

[Alexander Kitaev-3]

Hello Julian,

I suspect that the reason of the problem is that SVNKit (I assume you're
importing files to repository over "file" protocol) writes file deltas
in compressed format that is not supported by native 1.1.3 client.

In case repository is created with SVNKit, then there it is not a bug of
course, it just old Subversion client not supporting new format.

In case you've created repository with the old version native svnadmin,
then it is probably a bug in SVNKit, in a sense, that SVNKit should
check repository format and not use features not supported by this
particular repository or upgrade format to let old Subversion client
provide correct error message.

I think that upgrading native client to 1.4.x should resolve the problem.

You also wrote that it works fine with svnserve - what version of
svnserve did you use?

Alexander Kitaev,
TMate Software,
http://svnkit.com/ - Java [Sub]Versioning Library!

Julian312 wrote:

>
> Julian312 wrote:
>> But now, if I try to checkout my repository using the native SVN command
>> line client, I get the following error:
>> "svn: Invalid diff stream: insn 0 cannot be decoded"
>> or sometimes also:
>> "svn: Invalid diff stream: [tgt] insn 1 starts beyond the target view
>> position"
>> and the file I imported before is not there.
>>
> OK, when I use svn:// instead of file:// to access my repository with
> SVNKit, then everything works. Is this a bug in SVNKit?
>

---------------------------------------------------------------------
To unsubscribe, e-mail: svnkit-users-unsubscribe@...
For additional commands, e-mail: svnkit-users-help@...

[Alexander Kitaev-3]

Hello Julian,

We've fixed this problem in 1.1.x branch of SVNKit - now it should not
use new delta format for repositories created with old version of
svnadmin program. The reason of the problem is that old version of
svnadmin didn't create "db/format" file in repository, and SVNKit
instead of treating lack of this file as the oldest format treated it as
the newest.

You may get binaries at https://teamcity.svnkit.com/ - follow
"artifacts" link in 1.1.x build configuration to download binaries (fix
is available from version #1.1.7.4314).

Thank you for reporting this problem!

Alexander Kitaev,
TMate Software,
http://svnkit.com/ - Java [Sub]Versioning Library!

Julian312 wrote:

>
> Julian312 wrote:
>> But now, if I try to checkout my repository using the native SVN command
>> line client, I get the following error:
>> "svn: Invalid diff stream: insn 0 cannot be decoded"
>> or sometimes also:
>> "svn: Invalid diff stream: [tgt] insn 1 starts beyond the target view
>> position"
>> and the file I imported before is not there.
>>
> OK, when I use svn:// instead of file:// to access my repository with
> SVNKit, then everything works. Is this a bug in SVNKit?
>

---------------------------------------------------------------------
To unsubscribe, e-mail: svnkit-users-unsubscribe@...
For additional commands, e-mail: svnkit-users-help@...