Repository Groups support with SVN

Support
1

Hi,

I’ve set up a Rhodecode instance using the new rcstack and I have an issue when trying to use Repository Groups with SVN. Only the SVN repositories that are at the root seems to work properly.

I’m using Rhodecode 4.28.0.REL.2023.04.05.1

In the rc_cluster_apps-svn-1 logs I can see that this request: “filename”:“dav_svn:/var/opt/rhodecode_repo_store/repository_group_name/test_repository” generate this error: “Can’t open file ‘/var/opt/rhodecode_repo_store/repository_group_name/format’: No such file or directory”
And the svn client output this error : “Could not find the requested SVN filesystem”

Is it that repository groups cannot be used with SVN or do I have an error in my config?

Thanks,
Fred

2

Hi,

can you try to restart SVN instance ?

./rcstack stack rhodecode restart svn

The way it works is that a NEW group needs to modify apache config, once this is done once all repos in that group would work.

3

That fixed it, thanks a lot!

4

If you’re a heavy SVN user, please try our 5.0.0 release which is available in docker.hub This comes with latest 1.14.X SVN support and also is python3

to switch from 4.X to 5.X simply following this

    ./rcstack cli set-runtime-image beta
    ./rcstack stack all down
    ./rcstack stack all up -d

We’d love your feedback on SVN support for this major upgrade that we did.

5

Hello,

RhodeCode 5.3.1
RCStack 5.23.0

I’m getting the same error quite frequently and I wonder if there is a way to fix on the server side. I mean, without restarting SVN manually.

What we do:

  1. A user creates a repo group
  2. The user creates a repo inside the new repo group
  3. The user tries to checkout the newly created repo

What happens:

The user gets the “Could not find the requested SVN filesystem” error at checkout.
He/she must ask the sysadmin to run sudo ./rcstack stack rhodecode restart svn for things to get back on track.

What’s expected:

Would be awesome to get things working right after creation. I mean, what’s the point of enabling rights delegation for new repo creation if it still requires the sysadmin intervention? :innocent:
Can’t we think of a way to automatically refresh the Apache config with a reload or something similar, without disturbing the rest of the system?

Thanks in advance.

6

We created a ticket for this but not sure on the timeline yet