Modify

Opened 10 years ago

Last modified 9 years ago

#963 new defect

'Browse Source' doesn't work after installation

Reported by: vikas.bn@… Owned by: Lewis Baker
Priority: normal Component: PerforcePlugin
Severity: normal Keywords:
Cc: Trac Release: 0.10

Description

Hi,

I have successfully installed PyPerforce and TracPerforce. Followed the instructions on the PerforcePlugin page and have set the repository_dir and repository_path to proper values. But still, when i click on the 'Browse Source' link on the trac-page, I get a page with an error -- "Unsupported version control system -perforce".

Did I miss anything during config?

-vikas

Attachments (0)

Change History (5)

comment:1 Changed 10 years ago by jlachapelle@…

I also have problems after installation. I have confirmed that python does have a perforce module.

==============================================

Traceback (most recent call last):

File "/usr/local/lib/python2.4/site-packages/trac/web/main.py", line 387, in dispatch_request

dispatcher.dispatch(req)

File "/usr/local/lib/python2.4/site-packages/trac/web/main.py", line 191, in dispatch

chosen_handler = self._pre_process_request(req, chosen_handler)

File "/usr/local/lib/python2.4/site-packages/trac/web/main.py", line 263, in _pre_process_request

chosen_handler = f.pre_process_request(req, chosen_handler)

File "/usr/local/lib/python2.4/site-packages/trac/versioncontrol/api.py", line 73, in pre_process_request

self.get_repository(req.authname) # triggers a sync if applicable

File "/usr/local/lib/python2.4/site-packages/trac/versioncontrol/api.py", line 91, in get_repository

raise TracError('Unsupported version control system "%s"'

TracError: Unsupported version control system "perforce"

comment:2 Changed 10 years ago by anonymous

I have also Problems: I got this error message:

Python Traceback

Traceback (most recent call last):
  File "/usr/local/lib/python2.5/site-packages/trac/web/main.py", line 406, in dispatch_request
    dispatcher.dispatch(req)
  File "/usr/local/lib/python2.5/site-packages/trac/web/main.py", line 237, in dispatch
    resp = chosen_handler.process_request(req)
  File "/usr/local/lib/python2.5/site-packages/trac/versioncontrol/web_ui/browser.py", line 112, in process_request
    rev_or_latest = rev or repos.youngest_rev
  File "/usr/local/lib/python2.5/site-packages/trac/versioncontrol/api.py", line 210, in <lambda>
    youngest_rev = property(lambda x: x.get_youngest_rev())
  File "/usr/local/lib/python2.5/site-packages/trac/versioncontrol/cache.py", line 218, in get_youngest_rev
    return self.youngest
AttributeError: 'PerforceCachedRepository' object has no attribute 'youngest'

comment:3 in reply to:  2 Changed 10 years ago by Lewis Baker

Replying to anonymous:

I have also Problems: I got this error message:

<...>
AttributeError: 'PerforceCachedRepository' object has no attribute 'youngest'

This error is the subject of #1655.

comment:4 Changed 9 years ago by Michael Baird

For those who might encounter this issue in the future (or these posters if they're still in need)... I had to run the service logged on as someone with above-average permissions.

For me, I had to do this for both a user-created TracD service and the Apache service. If you're using either of these configurations, you can enter 'services.msc' from the Start->Run dialog and find the service name, then select Properties, and its "Log On" tab. Change the radio button from "Local System Account" to the one below it and enter the account credentials.

I'm not sure if you need to give it an administrative user (which is what I did)... so users in the User or Power User group may still work.

comment:5 Changed 9 years ago by anonymous

I got this error before I had added a [components] section to trac.ini. Unfortunately the README doesn't mention this, so it is assumed knowledge when adding any plugins. This is supposed to be required for central plugin installs. For a local plugin install it shouldn't be needed, however I was unable to get that working at all (copying the generated egg file into the project plugins directory left me with the same message.

Modify Ticket

Change Properties
Set your email in Preferences
Action
as new The owner will remain Lewis Baker.

Add Comment


E-mail address and name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.