Custom Query (332 matches)

Hi,

after a long time of inactivity on the Debian package for
email2trac, I'm planning now an upload of the current version
2.4.5. There are two bugs open, which I have patched on my
production server, but I was never confident, that my patches
are correct, nor do I know whether they are necessary for the
current version. Could you maybe take a look at them?

 1. Error on wrongly encoded e-mail
    http://bugs.debian.org/593613
 2. Support for X-Spam-Flag/-Result
    http://bugs.debian.org/644916

Thanks in advance!

Cheers

I have an email that I am attempting to load into trac from within the command line. At the moment, the email2trac script fails with the following error:

Traceback (most recent call last):
  File "./.install/bin/email2trac", line 956, in ?
    tktparser.parse(sys.stdin)
  File "./.install/bin/email2trac", line 539, in parse
    if self.ticket_update(m):
  File "./.install/bin/email2trac", line 415, in ticket_update
    tkt.save_changes(self.author, body_text, when)
  File "/home/lendor/python/lib/python2.4/site-packages/Trac-0.11b1-py2.4.egg/trac/ticket/model.py", line 211, in save_changes
    when_ts = to_timestamp(when)
  File "/home/lendor/python/lib/python2.4/site-packages/Trac-0.11b1-py2.4.egg/trac/util/datefmt.py", line 55, in to_timestamp
    diff = dt - _epoc
TypeError: unsupported operand type(s) for -: 'int' and 'datetime.datetime'

I am using trac 0.11b1 and email2trac 0.9.5.

In building an RPM for email2trac 0.80, it is unable to find the python 2.6 binary in /usr/bin. I've attempted to set this on the configure line of the spec file, but I cannot determine the correct option to use. The scripts appear to scan all of /usr/bin to find an acceptable python binary, but doesn't see that there is one there.

I am attaching my rpmbuild output in hopes that whatever error I'm making can be corrected.