[Mailman-Users] Question about the configure script.
steele at agora-net.com
Thu Jun 22 19:22:57 CEST 2006
Yes, it contains the "from Defaults import *" line.
Yes, there is a paths.py with the correct prefix.
There are two Default.py's....one in an abandoned installation of
another version. I inherited this box not long ago, but I've checked to
make sure the init.d script looks for it in the proper prefix...I can't
imagine why it would try to find the other. The current installation is
/home/mailman ...the apparently abandoned installation (maybe the
previous sysadmin tried this?) is in /usr/local/mailman. However, as I
stated, there is absolutely no reference in the current working
installation to the /usr/local/mailman directory. If there was, I
highly doubt the qrunner would work properly. Any thoughts? Thanks in
Mark Sapiro wrote:
> Ryan Steele wrote:
>> All I did was follow the instructions in UPGRADE included with 2.1.8.
>> There is a Defaults.py at /path/to/mailman/Mailman/Defaults.py with the
>> line OLD_STYLE_PREFIXING = Yes in it. So, unless the instructions in
>> UPGRADE (basically, to run ./configure with the same options as the
>> previous install and then execute a make install) are flawed, there
>> shouldn't be any reason why I got that error.
> The instructions should be OK.
> Is mm_cfg.py in the '/path/to/mailman/' directory, and does it contain
> from Defaults import *
> and does the '/path/to/mailman/bin/' directory contain a paths.py file
> with the line
> prefix = '/path/to/mailman/'
>> Nevertheless, I seem to
>> get no errors in any of Mailman's logs or Exim's logs after I made that
>> change. Not sure why it wouldn't pick up the line in Defaults.py....
> The only thing I can think of is it's looking at the wrong file for
> some reason (some related questions above).
> Is you search (find / -name Defaults.py) do you find more than 1
More information about the Mailman-Users