Upgraded from 0.9.3 to 1.1.2 - Repositories give "Could not fetch resource information."
Added by A. Wegner over 15 years ago
I upgraded from 0.9.3 to 1.1.2 and encountered an error:
The Repository tab now brings up this message:
Did I miss a step in my upgrade?
My production.log only contains this:
My apache error log contains this:
[Fri Mar 11 12:41:14 2011] [error] [client 70.32.35.210] (20014)Internal error: Can't open file '/redmine/svn/freelance/format': No such file or directory [Fri Mar 11 12:41:14 2011] [error] [client 70.32.35.210] Could not fetch resource information. [500, #0] [Fri Mar 11 12:41:14 2011] [error] [client 70.32.35.210] Could not open the requested SVN filesystem [500, #2] [Fri Mar 11 12:41:14 2011] [error] [client 70.32.35.210] Could not open the requested SVN filesystem [500, #2] [Fri Mar 11 12:41:14 2011] [error] [client 70.32.35.210] (20014)Internal error: Can't open file '//redmine/svn/freelance/format': No such file or directory [Fri Mar 11 12:41:14 2011] [error] [client 70.32.35.210] Could not fetch resource information. [500, #0] [Fri Mar 11 12:41:14 2011] [error] [client 70.32.35.210] Could not open the requested SVN filesystem [500, #2] [Fri Mar 11 12:41:14 2011] [error] [client 70.32.35.210] Could not open the requested SVN filesystem [500, #2]
The missing file does exist - with the correct user permissions (I've verified that against the backups from 0.9.3):
Replies (1)
RE: Upgraded from 0.9.3 to 1.1.2 - Repositories give "Could not fetch resource information."
-
Added by A. Wegner over 15 years ago
I solved this by modifying config/configuration.yml to contain this: scm_subversion_command: /usr/bin/svn
I can browse the repositories now. I still have issues authenticating against the repository (so I can't commit any changes). Any ideas?