Hello,
I've just installed FishEye, and tried to add a first repository 'library' to it. However, I encountered the following error when I try to do it:
Unable to get info for the repository root for library
svn: E180001: Unable to open an ra_local session to URL
svn: E180001: Unable to open repository 'file:///R:/Projects/002%20Java%20library/svn'
svn: E180001: Unable to open repository 'file:///R:/Projects/002%20Java%20library/svn'
at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64)
at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51)
at org.tmatesoft.svn.core.internal.io.fs.FSRepository.openRepository(FSRepository.java:796)
at org.tmatesoft.svn.core.internal.io.fs.FSRepository.getLatestRevision(FSRepository.java:121)
at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.getRevisionNumber(SvnNgRepositoryAccess.java:118)
Unable to get Repository Root URL for library:file:///R:/Projects/002%20Java%20library/svn/
Exception getting FishEye access control
svn: E180001: Unable to open an ra_local session to URL
svn: E180001: Unable to open repository 'file:///R:/Projects/002%20Java%20library/svn'
svn: E180001: Unable to open repository 'file:///R:/Projects/002%20Java%20library/svn'
at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64)
at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51)
at org.tmatesoft.svn.core.internal.io.fs.FSRepository.openRepository(FSRepository.java:796)
at org.tmatesoft.svn.core.internal.io.fs.FSRepository.getLatestRevision(FSRepository.java:121)
at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.getRevisionNumber(SvnNgRepositoryAccess.java:118)
Error testing connection.
svn: E180001: Unable to open an ra_local session to URL
svn: E180001: Unable to open repository 'file:///R:/Projects/002%20Java%20library/svn'
svn: E180001: Unable to open repository 'file:///R:/Projects/002%20Java%20library/svn'
at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64)
at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51)
at org.tmatesoft.svn.core.internal.io.fs.FSRepository.openRepository(FSRepository.java:796)
at org.tmatesoft.svn.core.internal.io.fs.FSRepository.getLatestRevision(FSRepository.java:121)
at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.getRevisionNumber(SvnNgRepositoryAccess.java:118)
Repository:
D:\Java\library>svn info
Pfad: .
Wurzelpfad der Arbeitskopie: D:\Java\library
URL: file:///R:/Projects/002%20Java%20library/svn/logging
Relative URL: ^/logging
Basis des Projektarchivs: file:///R:/Projects/002%20Java%20library/svn
UUID des Projektarchivs: faa73236-9377-d642-b0ac-812f93e88f56
Revision: 1877
Knotentyp: Verzeichnis
Plan: normal
Letzter Autor: ...
Letzte geänderte Rev: 1877
Letztes Änderungsdatum: 2015-12-07 14:24:21 +0100 (Mo, 07. Dez 2015)
The repository is on a network mapped drive, so FishEye user only has the read access to it (can this be a problem?). Repository structure:
R:\Projects\002 Java library\svn>dir
Volume in drive R is Data
Volume Serial Number is E409-B6FA
Directory of R:\Projects\002 Java library\svn
19.12.2014 11:09 <DIR> .
19.12.2014 11:09 <DIR> ..
19.12.2014 11:08 <DIR> conf
19.12.2014 11:08 <DIR> dav
07.12.2015 14:24 <DIR> db
10.03.2009 08:40 2 format
19.12.2014 11:09 <DIR> hooks
19.12.2014 11:09 <DIR> locks
10.03.2009 08:40 234 README.txt
2 File(s) 8'428 bytes
7 Dir(s) 110'791'135'232 bytes free
R:\Projects\002 Java library\svn>cat format
5
(So it's NOT a subversion 1.9 structure)
Note that FishEye can successfully connect to another repository over https://. So it's somehow related to the file:// access.
Does anybody have any hints about this?
I am trying to fix a similar problem, but have figured out that 'format' is different than the filesystem format in 'db/format'. Values for the filesystem format are documented in https://svn.apache.org/repos/asf/subversion/trunk/subversion/libsvn_fs_fs/structure.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.