Custom Query (330 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (13 - 15 of 330)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
Ticket Resolution Summary Owner Reporter
#346 fixed too eager subject parsing in ticket update bas thomas.moschny@…
Description

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:

  • email2trac.py.in

     
    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            '''
    18641864
    18651865        ## Check if  FullBlogPlugin is installed
#345 fixed trac installation detection exception false positive bas quinn@…
Description
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
trac_version'
0.12.5
}}}

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
be:"
         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:
<https://oss.trac.surfsara.nl/email2trac/ticket/298>. When I have only the
package `python-genshi06` installed with Trac 0.12.5 it works fine, but not
email2trac.

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
/usr/lib/python2.6/site-packages/genshi
}}}

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

Quinn
#343 fixed Sender is not notified when new ticket is created bas leonardo.ascenso@…
Description

Today I made an upgrade to the last version. I don't upgrade email2trac for YEARS!

Now senders are not notified on new ticket/ticket update. I have this error on my log and I think that's why sender is not notified by email.

2014-07-17 18:52:28,574 email2trac lefatech.trac: function unique_attachment_names()
2014-07-17 18:52:28,574 email2trac lefatech.trac: function get_body_text()
2014-07-17 18:52:28,716 email2trac lefatech.trac: function attach_attachments()
2014-07-17 18:52:28,716 email2trac lefatech.trac: function mail_workflow: 
2014-07-17 18:52:28,717 email2trac lefatech.trac: function notify()
2014-07-17 18:52:28,754 email2trac lefatech.trac: Failure sending notification on creation of ticket #10060: [Errno -2] Name or service not known

It seems an error on email2trac line 2922 (tn.notify(tkt, new, modtime))

I'm I doing something wrong?

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
Note: See TracQuery for help on using queries.