Re: keygen problem generating cryptkey
Kevin Goodsell <[email protected]> Tue, 8 Feb 2011 10:03:24 -0800
| Newsgroups | gmane.mail.spam.tmda.user |
|---|---|
| Message-ID | <[email protected]> |
On Tue, Feb 8, 2011 at 8:29 AM, J. Maxwell <[email protected]> wrote: > Experiencing difficulty generating crypt_key > > O/S: FreeBSD 7.2; MTA: Qmail 1.03; DELIVERY: ~/Maildir > > #1737:> tmda-keygen -b >> crypt_key > Traceback (most recent call last): > File "/usr/local/bin/tmda-keygen", line 37, in <module> > from TMDA import Version > ImportError: No module named TMDA > #1738:> > > Any suggestions? not much found in the Archives. > >From http://tmda.sourceforge.net/cgi-bin/moin.cgi/TmdaInstallation: "TMDA is designed to run directly from its source directory. For example, if installed in /usr/local/tmda-1.1.0/, you'd run tmda-keygen by invoking /usr/local/tmda-1.1.0/bin/tmda-keygen. Do not move the bin/* programs outside the source tree..." The problem is that the TMDA/ directory is not in python's sys.path. TMDA tries to fix this itself in the paths.py file, but that has the same problem (it needs to be in Python's path to work). If TMDA/ isn't in the same directory as the script, you'll need to put it somewhere in sys.path, or modify sys.path to include the location of TMDA/ (possibly with the PYTHONPATH environment variable or a path configuration file as used by the 'site' module). -Kevin ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ tmda-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tmda-users