may we have the add-on logs from that repository for analysis? Logs can be collected on the Repository Settings - SVN Mirror - Support tab by the Create zip button. Could you advise do I understand correctly that the issue occurs at the configuration stage before the Import/Mirror button has been pressed? Also, could you please try to access the SVN repository remotely over https as it set in the Bitbucket and provide us with the svn log for that revision:
@ildarhm: Thanks for looking into this issue.
yes, your understanding is correct that this error message is coming before the Import button.
I am not able to find way to create support zip as you described in your comment. I am not getting Support tab in Repository Setting --> SVN mirror (attached is the screen shot for the same). Please let me know if I am missing anything here.
Attached is log from SVN. I guess this log is coming correctly because r52631 is not available at this path /Fire/Fire3 instead this is available for path /Fire/Fire2 as i described in my first comment.
We are able to access that repo. Please find the attached screenshot for the same.
the Fire/Fire3 directory might have been renamed from Fire2 somewhen back in time and that may be the reason why this the add-on tries to reach that path. It’s still unclear, however, whether this is the real file absence in SVN or the add-on is doing something wrong. To find this out we would need more information, may we additionally have the following logs:
Meanwhile, it’s still possible to proceed with the import even despite this issue. Instead of using ‘Automatic configuration’ select ‘Manual Configuration’ – in this case the add-on doesn’t search the SVN history, it just creates a mapping configuration for ‘standard’ layout. Your repository has that exact layout, so you can proceed with this configuration making no changes to it.