Hi, If fact 0000000 means that you have to put your Perforce password, if you don't use it, keep it empty. Config options p4port, p4user & p4passwd should be the same than your perforce option in trac.ini Thomas
-----Original Message----- From: trac-dev@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Wiinz Trac Mailinglist Sent: mercredi 5 septembre 2007 12:04 To: trac-dev@googlegroups.com Subject: [Trac-dev] Re: Perforce integration question Ok, then I need a little help (some more help...) There is a password (0000000000000000) in the conf, does the zeroes mean 'we do not use passwords' or what? When I run it (with or without the zeroes in the password row) and with both stable and latest version I get: [EMAIL PROTECTED]:~# python p4_trac_jobs.py.1 --file p4trac.conf{'check_delay': 60, 'dry_run': 0, 'first_check': -1, 'p4job_prefix': 'job', 'p4user': 'infosys', 'trac_project': '/home/perforce/trac/', 'trac_to_p4': {'assigned': u'assigned', 'new': u'open', 'reopened': u'open', 'closed': u'closed'}, 'debug': 2, 'p4passwd': 0, 'p4port': 'server:1666', 'p4_to_trac': {'assigned': u'assigned', 'open': u'new', 'suspended': u'assigned', 'working': u'assigned', 'closed': u'closed'}} Traceback (most recent call last): File "p4_trac_jobs.py.1", line 414, in <module> ticket = TicketSynchronizer(settings) File "p4_trac_jobs.py.1", line 330, in __init__ self.tktperforce = PerforceJob(settings) File "p4_trac_jobs.py.1", line 117, in __init__ except (ConnectionFailed, PerforceError), e: NameError: global name 'ConnectionFailed' is not defined Can anyone tell me what I am doing wrong? /Philip On 04/09/07, Thomas Tressieres <[EMAIL PROTECTED]> wrote: Yes the pyperforce-0.4 contains the patch (thanks to Lewis Baker). So you have nothing to do. -----Original Message----- From: trac-dev@googlegroups.com [mailto: <mailto:trac-dev@googlegroups.com> [EMAIL PROTECTED] On Behalf Of Trac Mailinglist Sent: mardi 4 septembre 2007 16:04 To: trac-dev@googlegroups.com Subject: [Trac-dev] Re: Perforce integration question Hi, The patched version of pyperforce... is that not a part of the pyperforce-0.4 version? easy_install automatically installs that version, so I'm curious if I should downgrade? And how do I go about patching it when there is an egg installed (I have a very bad understanding of the egg stuff, any help is warmly welcome). /Philip On 04/09/07, Trac Mailinglist <[EMAIL PROTECTED]> wrote: Thankyou, I figured using v0.11 would only cause me problems. But at some point I will need the workflow, so a port would be great. Let me know if you need a guinea pig to test your stuff on. /Philip On 04/09/07, Thomas Tressieres < <mailto:[EMAIL PROTECTED]> [EMAIL PROTECTED]> wrote: Him Thank you very much.... I developed and use a script that you can find here: http://trac-hacks.org/wiki/PerforceJobScript <http://trac-hacks.org/wiki/PerforceJobScript> By now, it works only with Trac 0.10.x, but i'm working on porting it to 0.11 and PerforcePlugin also. Regards, Thomas -----Original Message----- From: trac-dev@googlegroups.com [mailto: <mailto:trac-dev@googlegroups.com> [EMAIL PROTECTED] On Behalf Of Trac Mailinglist Sent: mardi 4 septembre 2007 14:05 To: trac-dev@googlegroups.com Subject: [Trac-dev] Perforce integration question Hi, I used to use trac with subversion and now we are using perforce. I have the trac-hacks perforce plugin working. It is really easy to install. Nice job guys! But I miss the commit hook I had on svn that chained the commits to an issue. Is there anyway to achieve this with perforce? /Philip Ce message et ses pièces jointes (le "message") est destiné à l'usage exclusif de son destinataire. Si vous recevez ce message par erreur, merci d'en aviser immédiatement l'expéditeur et de le détruire ensuite. Le présent message pouvant être altéré à notre insu, CALYON Crédit Agricole CIB ne peut pas être engagé par son contenu. Tous droits réservés. This message and/or any attachments (the "message") is intended for the sole use of its addressee. If you are not the addressee, please immediately notify the sender and then destroy the message. As this message and/or any attachments may have been altered without our knowledge, its content is not legally binding on CALYON Crédit Agricole CIB. All rights reserved. Ce message et ses pièces jointes (le "message") est destiné à l'usage exclusif de son destinataire. Si vous recevez ce message par erreur, merci d'en aviser immédiatement l'expéditeur et de le détruire ensuite. Le présent message pouvant être altéré à notre insu, CALYON Crédit Agricole CIB ne peut pas être engagé par son contenu. Tous droits réservés. This message and/or any attachments (the "message") is intended for the sole use of its addressee. If you are not the addressee, please immediately notify the sender and then destroy the message. As this message and/or any attachments may have been altered without our knowledge, its content is not legally binding on CALYON Crédit Agricole CIB. All rights reserved. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to trac-dev@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~----------~----~----~----~------~----~------~--~---
Ce message et ses pièces jointes (le "message") est destiné à l'usage exclusif de son destinataire. Si vous recevez ce message par erreur, merci d'en aviser immédiatement l'expéditeur et de le détruire ensuite. Le présent message pouvant être altéré à notre insu, CALYON Crédit Agricole CIB ne peut pas être engagé par son contenu. Tous droits réservés. This message and/or any attachments (the "message") is intended for the sole use of its addressee. If you are not the addressee, please immediately notify the sender and then destroy the message. As this message and/or any attachments may have been altered without our knowledge, its content is not legally binding on CALYON Crédit Agricole CIB. All rights reserved.