Custom Query (332 matches)


Show under each result:

Results (316 - 318 of 332)

Ticket Resolution Summary Owner Reporter
#345 fixed trac installation detection exception false positive bas quinn@…
On a new installation of email2trac 2.8.4, I got this error:

{q@oak/0 ~} echo hello | sudo -u apache /usr/bin/email2trac --project=asdf
Can not find a a valid trac installation, solutions could be:
        set PYTHONPATH
        use the --virtualenv <dir> option

However Trac is installed in the default location, and python is able to
find it with the default configuration:

{q@oak/0 ~} python -c 'from trac import __version__ as trac_version; print

So I discovered the problem is not that email2trac cannot find Trac, but
that there was a missing dependancy. I modified /usr/bin/email2trac to
display the detail of the exception:

--- /usr/bin/email2trac.orig    2014-11-17 09:25:11.000000000 -0600
+++ /usr/bin/email2trac 2014-11-17 09:25:16.000000000 -0600
@@ -2755,6 +2755,7 @@
         from trac import config as trac_config

     except ImportError, detail:
+        print detail
         print "Can not find a a valid trac installation, solutions could
         print "\tset PYTHONPATH"
         print "\tuse the --virtualenv <dir> option"

And it displayed this:

{q@oak/0 ~} echo hello | sudo -u apache /usr/bin/email2trac --project=ex
No module named genshi.builder
Can not find a a valid trac installation, solutions could be:
        set PYTHONPATH
        use the --virtualenv <dir> option

Installing package `python-genshi` solved the problem. However, while
installing the `python-genshi` package (version 0.5.1-7.1.el6) fixed the
problem, allowing email2trac to run correctly, it broke Trac exactly in the
way described by this user:
<>. When I have only the
package `python-genshi06` installed with Trac 0.12.5 it works fine, but not

In reference to this problem, setting `PYTHONPATH` didn't help. instead I
found the solution was to create a symlink:
sudo ln -s /usr/lib/python2.6/site-packages/Genshi-0.6-py2.6.egg/genshi

This is probably only a problem for CentOS/RHEL users who have Trac
installed form the EPEL repository.

#346 fixed too eager subject parsing in ticket update bas thomas.moschny@…

For this example subject

[hic] #1529?owner=bas,priority=medium: Re: LRZ

the fields part is parsed as:

owner=bas,priority=medium: Re

so in the end, the ticket field priority would be set to

medium: Re

This can be easily fixed:


    18591859        #
    18601860        ticket_regex = r'''
    18611861            (?P<new_fields>[#][?].*)
    1862             |(?P<reply>(?P<id>[#][\d]+)(?P<fields>\?.*)?:)
     1862            |(?P<reply>(?P<id>[#][\d]+)(?P<fields>\?[^:]*)?:)
    18631863            '''
    18651865        ## Check if  FullBlogPlugin is installed
#354 fixed qmail configuration example bas ttt@…

I would like to contribute with a full working example of qmail setup
for a multi Trac environment, making use of the parentdir configuration
option of email2trac.

You can add it all or in parts to the instructions page if you like.

Note that I could get the --virtualenv option to work for me and I had
to explicitly run the script with the Python from the desired
VirtualEnv. Maybe there is some bug in the VirtualEnv setting in
email2trac or wrong usage by me, I did not have enough time to find the
root cause and I could work around the problem.

Thank you for your effort developing and supporting this valuable
integration point between email system and Trac.

Best regards.

= qmail Configuration

This configuration was based on the following references:
 * man qmail-users

Configuration changes:

 * To accept emails for the new domain:
root@server:/etc/qmail# echo >> rcpthosts

 * To declare the new domain as a virtual domain, to ensure namespace
separation of local usernames:
root@server:/etc/qmail# echo >>

 * Add a rule to match all possible users of the new virtual domain to a
directory where per-user .qmail files determine further processing of
messages, running as www-data user:
root@server:/etc/qmail# sed -i

 * Make changes take effect:
root@server:/etc/qmail# qmail-newu
root@server:/etc/qmail# /etc/init.d/qmail restart

 * Put per-user .qmail files in place, making messages go to the
email2trac script:
root@server:/servers/trac/email2trac# echo '|/usr/bin/preline
/servers/trac/email2trac/bin/email2trac --project=one' > .qmail-one
root@server:/servers/trac/email2trac# echo '|/usr/bin/preline
/servers/trac/email2trac/bin/email2trac --project=two' > .qmail-two
root@server:/servers/trac/email2trac# echo '|/usr/bin/preline
/servers/trac/email2trac/bin/email2trac --project=three' > .qmail-three
Note: See TracQuery for help on using queries.