Jesse Jacobs wrote:
This updated the changeset for the repo but did not update the ticket
status and resolution.
Did it add a comment with the commit message to the ticket? It doesn't
seem so, as you should have a log message saying Updating ticket #1.
Do you commit with the same username as
Gary Oberbrunner wrote:
Here's a few of the things that bug us right now: there's some mismatch
between Trac's svn-like model of the world and git's;
Yes, most of these shortcomings should be fixed in the context of #1492,
and we have a strong incentive to achieve that for 0.13, as we started
On 10/14/2010 05:27 PM, Gary Oberbrunner wrote:
Our repo has around 7k files and around 17k commits total, so it's not
huge. But the trac source browser takes upwards of 30-60 seconds just to
display the top-level source dir!
We actually dodged this problem because we needed git
Hello Remy,
First ty for your response.
Unfortunately it did not update the ticket.
The svn user and the trac user are both the same username.
The user has TRAC_ADMIN privileges.
I added the TICKET_MODIFY privilege just in case.
Performed a svn commit. The ticket still did not get updated.
To follow up,
I disabled the perms check
check_perms = BoolOption('ticket', 'commit_ticket_update_check_perms',
'false',
Check that the committer has permission to perform the requested
operations on the referenced tickets.
This requires that the user
On Fri, Oct 15, 2010 at 9:54 AM, Remy Blank remy.bl...@pobox.com wrote:
Jesse Jacobs wrote:
This updated the changeset for the repo but did not update the ticket
status and resolution.
Did it add a comment with the commit message to the ticket? It doesn't
seem so, as you should have a log
On Fri, Oct 15, 2010 at 6:35 PM, Joakim Olsson joa...@unbound.se wrote:
On Fri, Oct 15, 2010 at 9:54 AM, Remy Blank remy.bl...@pobox.com wrote:
Jesse Jacobs wrote:
This updated the changeset for the repo but did not update the ticket
status and resolution.
Did it add a comment with the
Hi, indeed I had not updated my plugins when I upgraded to 0.12.
All is well again thanks.
Samuel.
--
You received this message because you are subscribed to the Google Groups Trac
Users group.
To post to this group, send email to trac-us...@googlegroups.com.
To unsubscribe from this group,
On 10/15/2010 8:28 AM, Matthew Caron wrote:
On 10/14/2010 05:27 PM, Gary Oberbrunner wrote:
Our repo has around 7k files and around 17k commits total, so it's not
huge. But the trac source browser takes upwards of 30-60 seconds just to
display the top-level source dir!
We actually dodged
Joakim Olsson wrote:
I'm using Git instead of Subversion and I'm
using OpenId for authentication of users so my usernames are not the
same as my user information from Git.
Does that mean that it won't be possible to make the commit_updater work
in my setup?
The commit updater doesn't
Jesse Jacobs wrote:
2010-10-15 14:13:24,726 Trac[api] DEBUG: Event changeset_added on for
changesets ()
Ah, that's the issue. Your post-commit hook is not configured correctly.
You must call the changeset added command with the repository name or
path and the revision name. The log message
Remy Bud,
I could freakin kiss u
Thank you sooo much.
All working and greatly appreciated.
Jesse
On Oct 15, 2010, at 5:43 PM, Remy Blank wrote:
Jesse Jacobs wrote:
2010-10-15 14:13:24,726 Trac[api] DEBUG: Event changeset_added on for
changesets ()
Ah, that's the issue. Your
Jesse Jacobs wrote:
I could freakin kiss u
Please don't :) You're welcome.
-- Remy
signature.asc
Description: OpenPGP digital signature
13 matches
Mail list logo
