[Trac] [changeset:???] function
Hi, is there any way of showing the author of a commit using the [changeset:] command in a wiki page? I want the tooltip you get when putting the cursor over the changeset link in a wiki page to show the author as well. Thanks for your help. Rob http://www.zuken.com/ Zuken Logo - Visit our website for more information Robert Moore Constraint Manager Team Leader 1500 Aztec West, Almondsbury, Bristol, BS32 4RF, UK T: +44 (0) 1454 207800 DDi: +44 (0) 1454 207817 F: +44 (0) 1454 207803 E: mailto:first.l...@zuken.co.uk rob.mo...@zuken.co.uk W: http://www.zuken.com www.zuken.com Zuken Ltd // Registered office: Bristol // Registered No. 956340 // Directors: Jinya Katsube, Kazuhiro Kariya, S Yukawa This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited. -- You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com. To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en. image001.gif
Re: [Trac] Access to tickets on the command line?
W. Martin Borgert, 12.12.2011 14:30: Hi, I'm running Trac 0.11.7 and would like to access individual tickets on the command line. With trac-admin I can remove tickets, but I would like to access/read the summary and other fields. Is there any way to do this? (I know, there is psql, of course.) TIA! Martin. All ticket information is stored in a database. Often this is a SQLite database file, but can be another database system like PostgreSQL or MySQL. To reach your tickets you could touch the ticket table(s) inside the database. For SQLite for example you can read and modify a database with the sqlite3 command line tool. But be warned: You will have to know about the database structure and you need to know some SQL before you modify the database. Anyway just changing a ticket summary for example should not be too complicated or dangerous. Good luck Clemens -- You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com. To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
Re: [Trac] Access to tickets on the command line?
Quoting Clemens Feige c.fe...@osypkamed.com: W. Martin Borgert, 12.12.2011 14:30: I'm running Trac 0.11.7 and would like to access individual tickets on the command line. With trac-admin I can remove tickets, but I would like to access/read the summary and other fields. Is there any way to do this? (I know, there is psql, of course.) All ticket information is stored in a database. Often this is a SQLite database file, but can be another database system like PostgreSQL or MySQL. To reach your tickets you could touch the ticket table(s) inside the database. For SQLite for example you can read and modify a database with the sqlite3 command line tool. That's why I wrote there is psql, of course :~) psql is the command line client to PostgreSQL. I do not recommend to use Trac with SQLite. But be warned: You will have to know about the database structure and you need to know some SQL before you modify the database. Anyway just changing a ticket summary for example should not be too complicated or dangerous. Accessing the database is not always sufficient. Tickets might contain attachments, that are stored in the file system. E.g. if you do: $ trac-admin trac-env ticket remove id not only the database entry is cleared, but also the file system (trac-env/attachments/tickets/). The right solution is probably to use the XML-RPC plugin. It contains nice Python client examples. Cheers -- You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com. To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
[Trac] turning on trac post-commit script in trac v12.1, RHEL6
Hi, I attempted to e-mail this message earlier, but it was apparently from the wrong address, so I'm posting via the web interface instead. Apologies if this ends up producing a duplicate message. I've installed the version (v12) of Trac maintained by EPEL (Extra Packages for Enterprise Linux) for RHEL6. This is an upgrade for us, we've been using Trac for years, and this upgrade is from v11, also installed on RHEL (v5) via EPEL. A smooth upgrade from v11, for the most part, with the exception of the required changes to the post-commit configuration. I see from the wiki that I need to enable the CommitTicketUpdater plugin, and that this plugin is part of the standard installation of Trac, but must be enabled. I can confirm the commit_updater.py code is present on the system: locate commit_updater.py /usr/lib/python2.6/site-packages/tracopt/ticket/commit_updater.py /usr/lib/python2.6/site-packages/tracopt/ticket/commit_updater.pyc /usr/lib/python2.6/site-packages/tracopt/ticket/commit_updater.pyo I have added the following lines to our trac.ini file: ... [components] ... tracopt.ticket.commit_updater.committicketreferencemacro = enabled tracopt.ticket.commit_updater.committicketupdater = enabled ... [ticket] commit_ticket_update_check_perms = true commit_ticket_update_commands.close = commit_ticket_update_commands.refs = ALL commit_ticket_update_envelope = [] commit_ticket_update_notify = true ... And I've upgraded the post-commit hook script in the svn repository, so that it reads: #REPOS=$1 REPOS=/svr/svn/our_repository_name REV=$2 # e-mail a message detailing this commit /usr/local/path/bin/commit-email.pl $REPOS $REV --from ad...@mywork.edu -s commit: ourdevmaill...@mywork.edu # call the trac-post-commit-hook LOG=`/usr/bin/svnlook log -r $REV $REPOS` AUTHOR=`/usr/bin/svnlook author -r $REV $REPOS` TRAC_ENV='/svr/trac/ourrepository/' TRAC_URL='https://oururl/ourrepository' $REPOS/hooks/bin/trac-svn-hook\ $REPOS \ $REV \ $AUTHOR The $REPOS/hooks/bin/trac-svn-hook script was copied directly from /usr/share/doc/trac-0.12.1/contrib/trac-svn-hook First, the symptoms: * Commits are working as expected: messages are sent from the post- commit hook to ourdevmaillist * Commands in commit messages no longer update tickets in Trac. This used to work with our v11 installation of Trac. * The admin interface of our Trac site does not indicate that the plugin tracopt.ticket.commit_updater.committicketreferencemacro is enabled, nor that it's even an available plugin. So, I'm wondering if anyone else has successfully made a similar upgrade in a RHEL environment, and if so, would you be able to share the secrets of your success with me? Or, even if you're not working in this environment, if you have any tips for me, they'd be appreciated. Thanks! -- You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com. To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
[Trac] Re: Access to tickets on the command line?
On Jan 24, 7:00 pm, W. Martin Borgert deba...@debian.org wrote: Quoting Clemens Feige c.fe...@osypkamed.com: W. Martin Borgert, 12.12.2011 14:30: I'm running Trac 0.11.7 and would like to access individual tickets on the command line. With trac-admin I can remove tickets, but I would like to access/read the summary and other fields. Is there any way to do this? (I know, there is psql, of course.) All ticket information is stored in a database. Often this is a SQLite database file, but can be another database system like PostgreSQL or MySQL. To reach your tickets you could touch the ticket table(s) inside the database. For SQLite for example you can read and modify a database with the sqlite3 command line tool. That's why I wrote there is psql, of course :~) psql is the command line client to PostgreSQL. I do not recommend to use Trac with SQLite. But be warned: You will have to know about the database structure and you need to know some SQL before you modify the database. Anyway just changing a ticket summary for example should not be too complicated or dangerous. Accessing the database is not always sufficient. Tickets might contain attachments, that are stored in the file system. E.g. if you do: $ trac-admin trac-env ticket remove id not only the database entry is cleared, but also the file system (trac-env/attachments/tickets/). The right solution is probably to use the XML-RPC plugin. It contains nice Python client examples. Somebody already started a TracShell project, but I don't know the current status: http://code.google.com/p/tracshell/ It also uses the RPC plugin, so RPC would most likely be the way to go regardless of tool. Install the RPC plugin, and you can even make your own tiny shell wrappers for curl to fetch format the information - see the API docs available in your site after install enable. :::simon https://www.coderesort.com http://trac-hacks.org/wiki/osimons -- You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com. To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
[Trac] Re: turning on trac post-commit script in trac v12.1, RHEL6
I'm beginning to think I need to repackage the /usr/lib/python2.6/site- packages/tracopt/ticket/commit_updater.py code as an egg and park it in the plugins folder. This is just a guess at this point, and if anyone has a better hint for me, I'll take it. Otherwise, I'll keep plodding on. If I figure it out, I'll post to this list. Thanks! On Jan 24, 12:57 pm, HardyPottinger hardy.pottin...@gmail.com wrote: Hi, I attempted to e-mail this message earlier, but it was apparently from the wrong address, so I'm posting via the web interface instead. Apologies if this ends up producing a duplicate message. I've installed the version (v12) of Trac maintained by EPEL (Extra Packages for Enterprise Linux) for RHEL6. This is an upgrade for us, we've been using Trac for years, and this upgrade is from v11, also installed on RHEL (v5) via EPEL. A smooth upgrade from v11, for the most part, with the exception of the required changes to the post-commit configuration. I see from the wiki that I need to enable the CommitTicketUpdater plugin, and that this plugin is part of the standard installation of Trac, but must be enabled. I can confirm the commit_updater.py code is present on the system: locate commit_updater.py /usr/lib/python2.6/site-packages/tracopt/ticket/commit_updater.py /usr/lib/python2.6/site-packages/tracopt/ticket/commit_updater.pyc /usr/lib/python2.6/site-packages/tracopt/ticket/commit_updater.pyo I have added the following lines to our trac.ini file: ... [components] ... tracopt.ticket.commit_updater.committicketreferencemacro = enabled tracopt.ticket.commit_updater.committicketupdater = enabled ... [ticket] commit_ticket_update_check_perms = true commit_ticket_update_commands.close = commit_ticket_update_commands.refs = ALL commit_ticket_update_envelope = [] commit_ticket_update_notify = true ... And I've upgraded the post-commit hook script in the svn repository, so that it reads: #REPOS=$1 REPOS=/svr/svn/our_repository_name REV=$2 # e-mail a message detailing this commit /usr/local/path/bin/commit-email.pl $REPOS $REV --from ad...@mywork.edu -s commit: ourdevmaill...@mywork.edu # call the trac-post-commit-hook LOG=`/usr/bin/svnlook log -r $REV $REPOS` AUTHOR=`/usr/bin/svnlook author -r $REV $REPOS` TRAC_ENV='/svr/trac/ourrepository/' TRAC_URL='https://oururl/ourrepository' $REPOS/hooks/bin/trac-svn-hook\ $REPOS \ $REV \ $AUTHOR The $REPOS/hooks/bin/trac-svn-hook script was copied directly from /usr/share/doc/trac-0.12.1/contrib/trac-svn-hook First, the symptoms: * Commits are working as expected: messages are sent from the post- commit hook to ourdevmaillist * Commands in commit messages no longer update tickets in Trac. This used to work with our v11 installation of Trac. * The admin interface of our Trac site does not indicate that the plugin tracopt.ticket.commit_updater.committicketreferencemacro is enabled, nor that it's even an available plugin. So, I'm wondering if anyone else has successfully made a similar upgrade in a RHEL environment, and if so, would you be able to share the secrets of your success with me? Or, even if you're not working in this environment, if you have any tips for me, they'd be appreciated. Thanks! -- You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com. To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
