Opened 10 years ago

# debugging perforce server setup

Reported by: Owned by: Georg Baumann ttressieres normal PerforcePlugin normal 0.10

### Description

Is there any way to debug the communication with the Perforce server? I have tried all kinds of modifications of the trac.ini settings, but the only message i can get is this one:

 > trac-admin pwd resync
Resyncing repository history...
Command failed:


Setting the trac logging to DEBUG does not show any information. What do i need to do to get a clue?

BTW: i am using perforceplugin_trunk-r2724.zip and i am trying to connect to a 2006.2 Perforce server (using trac 0.10.4)

Thanks, Georg

### comment:1 Changed 10 years ago by Georg Baumann

Alternatively, when using the "single line configuration method", then i get:

 > trac-admin pwd resync
Resyncing repository history...
Command failed: The 'repository_dir' has changed a 'trac-admin resync' operation is needed
}}


### comment:2 Changed 10 years ago by anonymous

I see this exact issue w/ 10.4 and the latest Perforce server and PyPerforce bindings.

### comment:3 Changed 10 years ago by anonymous

This is all more than a little confusing. I have tried various combinations of

[trac]
perforce_type = perforce
perforce_dir = perforce

[trac]
perforce_type = p4://user:passwd@perforce:1666/path_of_depot?unicode=0
perforce_dir = perforce


The 1.4.2 readme does not appear to mention the need for:

[components]
p4trac.* = enable


entry. So I put it in anyway.

Then there is the [perforce] section:

[perforce]
port = perforce:1666
user = p4trac
unicode = 0


Maybe it would be less confusing to have an option to get these from the environment, but anyway.

All I can get is this message!!!

\$ trac-admin /var/trac resync
Resyncing repository history...
"Command failed: The 'repository_dir' has changed a 'trac-admin resync' operation is needed


### comment:4 Changed 10 years ago by ttressieres

Owner: changed from Lewis Baker to ttressieres new → assigned

### comment:5 Changed 10 years ago by ttressieres

could you re-try it with perforceplugin at [2973]. browse source perforceplugin/branches/trac-0.10

### Modify Ticket

Change Properties