LuKreme wrote:
configure: WARNING: unrecognized options: --with-group-name
Because it's spelled --with-groupname
Yeah, I don't get that.
And you do get another warning that I don't get. ???
# python --version Python 2.5.5 # bash --version GNU bash, version 4.0.35(0)-release (i386-portbld-freebsd6.2) Copyright (C) 2009 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software; you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. #
checking for --with-python... no
No idea, python is certainly installed.
That only means you didn't specify --with-python. The next lines
checking for python... /usr/local/bin/python checking Python interpreter... /usr/local/bin/python checking Python version... 2.5.5
say it found your python OK.
Could there be something in your environment that's affecting this? Or your shell? What shell is invoked by /bin/sh?
running straight bash, nothing set in my environment. In fact, I tried to compile it just now with su root (no .profile or .bashrc active at all).
and even if you try to make at that point, there is no Makefile
Are you saying configure completes and makes a config.status and runs that and there is no Makefile after that? Really strange=85
Yes, exactly.
Very strange.
I've downloaded the tarball twice now.
You could try running autoconf to generate a new configure from configure.in. There might be some idiosyncrasy between the packaged configure and what, I don't know.
Note that the expected group (mailman) is compiled into the mailman/mail/mailman wrapper (from configure's --with-mail-gid) in standard Mailman. I don't know how to set it in your package.
I keep trying to get it to work properly with the mailman user and group but it is not playing nice. I would prefer, of course, to have this all working properly (with uid and gid of mailman) but working -at all- would be better.
If the aliases are found in an aliases.db file whose owner (not group) is 'mailman', Postfix will invoke the wrapper as the mailman user:group.
I am truly puzzled as to why the configure in the tarball apparently isn't working correctly.
Also, You said you first saw this when you attempted to post to a low-traffic announce-list. Were other lists working at that time?
I'm going to try and recompile the port with mailman/mailman and split the aliases out into the data/aliases file, set those perms, re-postalias all the files, wave a fresh chicken bone over the server, and hope for the best.
OK
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan