Ryan Steele wrote:
>
>There are two Default.py'sone 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.
Check the cron
Yes, it contains the "from Defaults import *" line.
Yes, there is a paths.py with the correct prefix.
There are two Default.py'sone 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
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 optio
Mark,
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
previou
Ryan Steele wrote:
>
>Solved my problem by putting the following in mm_cfg.py:
>
>OLD_STYLE_PREFIXING = No
But you still have a problem because either you don't have a 2.1.8
Defaults.py which contains
OLD_STYLE_PREFIXING = Yes
or your mm_cfg.py is missing the stuff near the beginning that says
All,
Solved my problem by putting the following in mm_cfg.py:
OLD_STYLE_PREFIXING = No
Thanks,
Ryan
Ryan Steele wrote:
> Thanks for the tips guys, that helped me figure out which values to give
> those fields in configure. The upgrade seemed to go smoothly, however I
> can no longer send mai
Thanks for the tips guys, that helped me figure out which values to give
those fields in configure. The upgrade seemed to go smoothly, however I
can no longer send mail. Here's the error I get in Mailman's logs:
Jun 21 10:50:10 2006 (1861) Uncaught runner exception: 'module' object
has no att
Ryan Steele wrote:
>
>I have a question about the options for the configure script. I'm
>upgrading an installation of Mailman to 2.1.8, but I'm not sure what the
>previous sysadmin configured for the --with-mail-gid option. He has
>apparently deleted the mailman- directory, leaving only the
>
On 6/20/06, Ryan Steele <[EMAIL PROTECTED]> wrote:
> target installation directory in his wake. Is there any other place
> besides the config.log that would yield the options fed to configure?
> If not explicitly, is there a way to extrapolate this simply from the
> installation directory? Thanks
List,
I have a question about the options for the configure script. I'm
upgrading an installation of Mailman to 2.1.8, but I'm not sure what the
previous sysadmin configured for the --with-mail-gid option. He has
apparently deleted the mailman- directory, leaving only the
target installation
10 matches
Mail list logo
