Add SVN-Properties MimeType not correct working

[service...@gmail.com]

Hello,

We have installed SCM Manager on Windows Server 2013. We use SVN in our PLC development system (codesys 3s).

Unfortunately, this system only uses binaries as data elements and has its own internal interpretation of the data.

At the moment we are not able to use SCM-Manager as SVN-Server because the items does have svn-properties.

See picture below as example the properties which are used(Using TortoiseSVN to see the properties)

This properties were set by the development system itself and we have no further influence on it.

In case we using the scm-manager this properties missing and the development system stop working

If we try to set the properties via TortoiseSVN manually we getting an exception after commit. Especially the SVN-MimeType binary is not working

In our current SVN-Server(collabnet) the operation is working.

Thanks

Uwe

[Sebastian Sdorra]

Hi,

there are some properties to control the behaviour of svn binary properties in scm-manager.

Could you please test version 1.60 and start it with -Dsonia.svnkit.fsfs.ignoreInvalidEncodedProperties=true?

And if the error still occurs, please try -Dsonia.svnkit.fsfs.alwaysAllowBinaryProperties=true instead.

Sebastian

--
You received this message because you are subscribed to the Google Groups "scmmanager" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scmmanager+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[service...@gmail.com]

Hi,

I have test it with both options. In case of -Dsonia.svnkit.fsfs.ignoreInvalidEncodedProperties=true

I have the result.

In case of -Dsonia.svnkit.fsfs.alwaysAllowBinaryProperties=true the result...

 

What does it mean "Wrong magic"? If you convert the expected value into hex it's 0x85301D21. All actual value's converted have some parts from the expected value's

488701952  =  0x1D210000

4012907809 = 0xEF301D21

Uwe

[Service SVNSomm]

Hi,

I have test it with both options. In case of -Dsonia.svnkit.fsfs.ignoreInvalidEncodedProperties=true

I have the result.

In case of -Dsonia.svnkit.fsfs.alwaysAllowBinaryProperties=true the result...

 

What does it mean "Wrong magic"? If you convert the expected value into hex it's 0x85301D21. All actual value's converted have some parts from the expected value's

488701952  =  0x1D210000

4012907809 = 0xEF301D21

Uwe

[Service SVNSomm]

Hi,

in addition I've changed the logging level from scm-manager. The logging from the initial check is attached. 

There are a lot of "DEBUG svnkit - svn: E140000" and "org.tmatesoft.svn.core.SVNException: svn: E160013: Attempted to open non-existent child node 'svnobj'" entry.

Thanks

Uwe

Am Do., 7. Feb. 2019 um 20:32 Uhr schrieb Sebastian Sdorra <s.sd...@gmail.com>:

[Girish Kg]

This issue is still exist (v2.34.0, Linux OS). Anyone have any workaround?

[Eduard Heimbuch]

Hey girishKG,

could you provide some more informations? Do you know a reliable way to trigger this error? An example repo would be really helpful.

I assume the error might be somewhere here, but i cannot reproduce it: https://github.com/scm-manager/svnkit/blob/7bfdd6645e22b8d07553d88405a6a875bec1251d/svnkit/src/main/java/org/tmatesoft/svn/core/internal/io/fs/FSFile.java#L280

BR, Eduard