#2006 closed defect (worksforme)
Unable to access hooks directory
| Reported by: | Owned by: | Robert Barsch | |
|---|---|---|---|
| Priority: | normal | Component: | TracSvnHooksPlugin |
| Severity: | normal | Keywords: | |
| Cc: | Trac Release: | 0.10 |
Description
Installed tracsvnhooks 0.2 into a trac 0.10.3.
svn contains a number of projects, the configuration for this project is:
repository_dir c:\svnrepositories\WEBMIP
repository_type svn
Running the plugin produces:
Internal Error: Can't access repository hook directory c:\svnrepositories\WEBMIP\hooks
The hooks directory is found at c:\svnrepositories\hooks - the WEBMIP reference is the location of the project within the repository (I think that this is standard practice for trac and multiple svn repositories?)
Attachments (0)
Change History (3)
comment:1 follow-up: 2 Changed 18 years ago by
| Resolution: | → worksforme |
|---|---|
| Status: | new → closed |
comment:2 Changed 18 years ago by
Replying to Bombenbodo:
An easy solution to the problem above, would be a symlink from
c:\svnrepositories\WEBMIP\hookstoc:\svnrepositories\hooks.
Unfortunately this doesn't work with the fsfs environment - there are no 'project' levels above the repository directory.
Another way would be the introduction of an optional option in
trac.ini, i.e.repository_hooks_dir. If there is a strong request for this option, I'm going to integrate this.
This sounds useful, I'll add my vote!
Thanks for your help,



In our environment we use an own svn tree for each project - therefore each got his own
hookssubdirectory - the default structure which is created via thesvn-admincommand. This allows to have different hooks for each project.An easy solution to the problem above, would be a symlink from
c:\svnrepositories\WEBMIP\hookstoc:\svnrepositories\hooks.Another way would be the introduction of an optional option in
trac.ini, i.e.repository_hooks_dir. If there is a strong request for this option, I'm going to integrate this.