-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 27.10.2012 00:09, Skye Bender-deMoll wrote:
> On 10/26/2012 01:23 PM, RjOllos wrote:
>> On Tuesday, October 23, 2012 2:31:10 PM UTC-7, skyebend wrote:
>>
>>> Hi folks,
>>>
>>> The feature to close tickets with an svn commit message has stopped
>>> working for me.  It was definitely working a few weeks ago, I may have
>>> made some permissions changes during the process of getting commit
>>> emails working.  But I'm not getting any error messages, and file
>>> permissions appear to be correct.  Does anyone have any suggestions on
>>> how to debug this?
>>>
>>> More info:
>>>
>>> Post commit hook seems to still be working, commits show up on the
>>> timeline and ticket number #123 is hilighted and linked to ticket but
>>> "Fixes #123" or "Closes #123"  does not trigger the appropriate action.
>>> I've set logging to Debug, but don't recognize any issues in the log.
>>> Committing unix username is the same as trac user.
>>>
>>> Debian
>>> Trac 0.12.2
>>> CommitTicketUpdater enabled
>>>
>>> Any ideas?
>>>
>>>
>> This seems to be coming up pretty frequently on the list. If you
>> search the
>> group you'll find several threads over the past several months. You might
>> start here and see if any of the hints help you:
>> https://groups.google.com/forum/?fromgroups=#!searchin/trac-users/commit$20message%7Csort:date/trac-users/ERMj0xKtByE/g5r_KaSSNDMJ
>>
> Thanks for the response with links to more info.
> 
> It was a permissions problem after all.  Posting how I found it here
> just in case it helps others who are searching with a similar problem.
> 
> I'd verified that my trac settings were correct as per earlier threads.
> 
> I ran just the "/usr/bin/trac-admin changeset added ..."  command from
> my post-commit script.  The command failed as my ssh+svn user (Error:
> Command not found), but ran fine as sudo.  So I was pretty sure it was a
> permissions problem.  After a bit of chasing red herrings, a friend
> suggested  running with strace
> 
> strace /usr/bin/trac-admin /trac/repo_name changeset added
> "svn_repo_name" "svn_revision_id"
> 
> which eventually printed out:
> 
> open("/trac/repo_name/log/trac.log",
> O_WRONLY|O_CREAT|O_APPEND|O_LARGEFILE, 0666) = -1 EACCES (Permission
> denied)
> write(2, "Error: Command not found", 24Error: Command not found) = 24
> 
> I checked the permissions on the trac.log file, and found that it was
> missing group write permissions for the group containing the svn user.
> When I corrected that, the commit message  "fixes #123" worked fine again!
> 
> best,
>  -skye

Thanks for the feedback. This is valuable information indeed.

Just one minor nit-pick: Avoid top-posting. English an a lot of other
languages are read left-to-right and top-down. So top-posting totally
messes up the otherwise much tidier read-line.

Compare on your own: I've hand-edited above as if your post had followed
that style recommendation (net-etiquette). Thanks for consideration.

Steffen Hoffmann
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAlCLj5AACgkQ31DJeiZFuHeFrACgmP5UgPAT/QXOq4EH0rWjh5g0
XmkAnjZcxVTVHajlGiUk9hRlRZF6M1ud
=FvPD
-----END PGP SIGNATURE-----

-- 
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en.

Reply via email to