Modify ↓
#12138 closed defect (fixed)
[Errno 2] No such file or directory
Reported by: | ikerazpeitia | Owned by: | Ryan J Ollos |
---|---|---|---|
Priority: | normal | Component: | TracHacksPlugin |
Severity: | normal | Keywords: | trachack, creation, |
Cc: | Trac Release: | 1.0 |
Description
I installed Trac system and TracHackPlugin in my server (AMD64 Red Hat Enterprise Linux Server release 5.11 (Tikanga))
When I try to create a new Hack an error is showed. The log registers this information:
Trac[web_ui] ERROR: [Errno 2] No such file or directory Traceback (most recent call last): File "build/bdist.linux-x86_64/egg/trachacks/web_ui.py", line 463, in create_hack selected_releases) File "build/bdist.linux-x86_64/egg/trachacks/web_ui.py", line 545, in _create_repository_paths env=env) File "/usr/local/lib/python2.5/subprocess.py", line 594, in __init__ errread, errwrite) File "/usr/local/lib/python2.5/subprocess.py", line 1097, in _execute_child raise child_exception OSError: [Errno 2] No such file or directory
It seems is a problem with the paths on the repository linked to the selected release. I have created only one release type: "deployed". Does creating a release imply a certain structure on the repository?
Attachments (0)
Change History (8)
comment:1 Changed 10 years ago by
Owner: | changed from Michael Renzmann to Ryan J Ollos |
---|---|
Status: | new → accepted |
comment:7 Changed 10 years ago by
Resolution: | → fixed |
---|---|
Status: | accepted → closed |
After installing and enabling the plugin:
- Make at least one page tagged with type.
- Make at least one page tagged with release-filter
- Create a default repository
- Create an authz file:
$ touch $env/conf/authz.ini $ trac-admin $env config set trac authz_file authz.ini
Let me know if you discover any additional issues.
Note: See
TracTickets for help on using
tickets.
Replying to ikerazpeitia:
It's probably something like that. There hasn't been much care given to ensuring that the plugin is usable by others. I'm surprised there would be much interest in deploying it elsewhere.
I'll try to find time to do some testing this weekend.