Error "wrong magic" when using scm-Manager with codesys svn

SCM-Manager Bug Reports SCM-Manager
1

  • bug description (occurred issue):

    • I use e!cockpit 1.11 (codesys 3.5) with svn plugin 1.11.3. When I create a new repository, connect to it and try to commit changes, I get the error message:
      Error while reading: Wrong magic; actual=488701952, expected=2234522913

  • expected result / system behavior:

    • updating the svn project

  • observed result / system behavior:

    • the “actual” and “expected” values are always the same
    • project could not be committed
    • when ignoring the message another error pops up:
      svn-metadata property is missing […] possible cause: system does not support properties correctly

  • SCM-Manager version and installed package:

    • 3.9.0

I also tried to set the svn compatible mode to 1.7, no effect. When I use the svn server from my synology NAS (svn 1.12 I think), everything works fine…

If nescessary I could maybe provide vm’s for testing purposes…

Regards

[EDIT: Logfiles added]

8IUumy8RCb.zip (28.0 KB)

2

Hi @weasel , thanks for this report! Did this work with older versions of SCM-Manager or did you just start using SCM-Manager with e!cockpit?

3

well I just found scm-manager because I was looking for a new svn system (native svn plugin on my synology is deprecated). So this is the first version I tried. It first occured after importing my svn dump from synology, so I thought maybe there was something wrong with the dump. But the same behaviour occures when I create new repositories, as in the original post.

BTW: It’s only codesys related, all other repositories work fine (mostly using tortoise svn client).

I found this toppic which is exactly the same, using an older version of scm (scm 2.x) - unfortunately without solution. I also tried the parameters suggested in this toppic but nothing changed…

So far…

Regards!

[edit]

If nescessary I could try older versions, if you like. Simply instruct me :slight_smile:

1 Like
4

Hi guys,

are there any new news concerning this topic? I’m just asking if I can wait for a investigation / fix or if I have to look for another solution…

Thanks so far…

Weasel