Custom Query (332 matches)
Results (13 - 15 of 332)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#14 | fixed | rpmbuild from spec installation fails | bas | Archon810 |
Description |
I am at the installation point of email2trac and I'm trying to install using rpmbuild but it fails with this error: Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.57580 + umask 022 + cd /usr/src/packages/BUILD + /bin/rm -rf /var/tmp/email2trac-0.9.5-1-root ++ dirname /var/tmp/email2trac-0.9.5-1-root + /bin/mkdir -p /var/tmp + /bin/mkdir /var/tmp/email2trac-0.9.5-1-root + cd email2trac-0.9.5 + mkdir /var/tmp/email2trac-0.9.5-1-root mkdir: cannot create directory `/var/tmp/email2trac-0.9.5-1-root': File exists error: Bad exit status from /var/tmp/rpm-tmp.57580 (%build) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.57580 (%build) The following change is required in order for this build to succeed: Line 32 add -p mkdir -p $RPM_BUILD_ROOT Now the installation completes without problems. |
|||
#15 | fixed | Milestone Handling | bas | Garrett McGrath <gmcgrath@…> |
Description |
To whom it may concern: I'm looking at modifying the email2trac script to enable it to handle a 'category' flag. Specifically we are using Trac as a data portal for our users and are exploring using the ticket system to track help requests to make life easier for our users (quick referrence to past issues and etc.). I'm thinking that the milestones system would be an easy way to segregate our emailed tickets automatically. eg. if we get a feature request for our calendar that goes to 1 email, and general help to a second email address, these simply populate the same ticket system in trac but with different milestones attached to them (or components as that would be nice to split things up with as well). So my question is has anyone does this before, and do I just need to modify the email2trac.py program or do the .c and .h files get modified as well. -Garrett McGrath |
|||
#18 | fixed | Support replying to ticket notifications | bas | chrivers@… |
Description |
I'm trying to use trac+email2trac as a request tracket for the support@ email address at our company. It mostly works, except for the following problems:
To solve these problems, I suggest something like the following scenario:
I hope you can see the idea I have for using trac as a sort of mediator, or ticket gateway, if you will. As far as I can see, it should already be able to update tickets, although I have not successfully made this work yet. Can you tell me what kind of work would be required to make email2trac act as outlined here? Would patches be accepted? |