This problem has been resolved, thanks to my new friend Alex Zbyslaw!
The problem was that my /usr/local/lib/python2.4 was set with perms
754 rather than 755. I didn't realize that doing a port uninstall and
reinstall doesn't necessarily correct permission problems on parent
directories.
Joe Auty wrote:
$ sh -x /usr/local/etc/rc.d/mailman.sh start
and if that finds nothing
Same problem, would you like a copy of this output? I'm presuming the
lines prefaced by a "+" are of interest to you?
Yes, very much! They're what the shell actually does. Most will be
useless to us
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jun 19, 2006, at 4:34 AM, Alex Zbyslaw wrote:
Joe Auty wrote:
On Jun 18, 2006, at 1:28 PM, Alex Zbyslaw wrote:
Joe Auty wrote:
On Jun 15, 2006, at 6:16 AM, Alex Zbyslaw wrote:
Joe Auty wrote:
jauty# python -v /usr/local/mailman/bin/q
Joe Auty wrote:
On Jun 18, 2006, at 1:28 PM, Alex Zbyslaw wrote:
Joe Auty wrote:
On Jun 15, 2006, at 6:16 AM, Alex Zbyslaw wrote:
Joe Auty wrote:
jauty# python -v /usr/local/mailman/bin/qrunner
[...snip...]
# /usr/local/lib/python2.4/getopt.pyc matches /usr/local/lib/
python2.4/geto
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I sent on this problem to the Mailman list and got the following
response is this useful?
Joe Auty wrote:
On Jun 18, 2006, at 12:41 PM, Mark Sapiro wrote:
Joe Auty wrote:
When I try to startup the Mailport FreeBSD port via its rc
On Jun 18, 2006, at 1:28 PM, Alex Zbyslaw wrote:
Joe Auty wrote:
On Jun 15, 2006, at 6:16 AM, Alex Zbyslaw wrote:
Joe Auty wrote:
jauty# python -v /usr/local/mailman/bin/qrunner
[...snip...]
# /usr/local/lib/python2.4/getopt.pyc matches /usr/local/lib/
python2.4/getopt.py
import getop
Joe Auty wrote:
On Jun 15, 2006, at 6:16 AM, Alex Zbyslaw wrote:
Joe Auty wrote:
jauty# python -v /usr/local/mailman/bin/qrunner
[...snip...]
# /usr/local/lib/python2.4/getopt.pyc matches /usr/local/lib/
python2.4/getopt.py
import getopt # precompiled from /usr/local/lib/python2.4/getopt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jun 15, 2006, at 6:16 AM, Alex Zbyslaw wrote:
Joe Auty wrote:
On Jun 14, 2006, at 1:10 PM, Alex Zbyslaw wrote:
And one which may spew quite a lot. Cut it off if it gets to
printing help.
$ python -v /usr/local/mailman/bin/qrunner
Joe Auty wrote:
On Jun 14, 2006, at 1:10 PM, Alex Zbyslaw wrote:
And one which may spew quite a lot. Cut it off if it gets to
printing help.
$ python -v /usr/local/mailman/bin/qrunner
jauty# python -v /usr/local/mailman/bin/qrunner
[...snip...]
# /usr/local/lib/python2.4/getopt.pyc m
PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Joe Auty
Sent: Wednesday, June 14, 2006 12:11 PM
To: Alex Zbyslaw
Cc: FreeBSD Questions
Subject: Re: Python port problems
On Jun 14, 2006, at 6:01 AM, Alex Zbyslaw wrote:
Joe Auty wrote:
Sorry for the delay in response here. This is still a problem for
Try reloading the cvs base for changes / updates before reinstalling
both Python and Mailman.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Joe Auty
Sent: Wednesday, June 14, 2006 12:11 PM
To: Alex Zbyslaw
Cc: FreeBSD Questions
Subject: Re: Python port
On Jun 14, 2006, at 1:10 PM, Alex Zbyslaw wrote:
I've truncated the tests since nothing there showed any problem
whatsoever. I'm running out of ideas, so this one may be off the
wall:
($ to indicate command lines but don;t type the $ :-))
Just as a preface, Mailman is working fine on
Joe Auty wrote:
On Jun 14, 2006, at 6:01 AM, Alex Zbyslaw wrote:
Joe Auty wrote:
Sorry for the delay in response here. This is still a problem for
me, and I would still like this problem resolved.
Yes, I've tried reinstalling both Python and Mailman, and upgraded
to newer port revi
On Jun 14, 2006, at 6:01 AM, Alex Zbyslaw wrote:
Joe Auty wrote:
Sorry for the delay in response here. This is still a problem for
me, and I would still like this problem resolved.
Yes, I've tried reinstalling both Python and Mailman, and upgraded
to newer port revisions of Mailman w
Joe Auty wrote:
Sorry for the delay in response here. This is still a problem for me,
and I would still like this problem resolved.
Yes, I've tried reinstalling both Python and Mailman, and upgraded to
newer port revisions of Mailman which have been released since this
message. I'm stil
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jun 13, 2006, at 7:51 PM, Michael P. Soulier wrote:
On 13/06/06 Joe Auty said:
Sorry for the delay in response here. This is still a problem for me,
and I would still like this problem resolved.
Yes, I've tried reinstalling both Python and Ma
On 13/06/06 Joe Auty said:
> Sorry for the delay in response here. This is still a problem for me,
> and I would still like this problem resolved.
>
> Yes, I've tried reinstalling both Python and Mailman, and upgraded to
> newer port revisions of Mailman which have been released since this
On May 23, 2006, at 12:42 PM, Alex Zbyslaw wrote:
Lowell Gilbert wrote:
Joe Auty <[EMAIL PROTECTED]> writes:
$ python -c 'import sys; print sys.path'
['', '/usr/local/lib/python24.zip', '/usr/local/lib/python2.4', '/
usr/ local/lib/python2.4/plat-freebsd5', '/usr/local/lib/
python2.4/lib
Lowell Gilbert wrote:
Joe Auty <[EMAIL PROTECTED]> writes:
$ python -c 'import sys; print sys.path'
['', '/usr/local/lib/python24.zip', '/usr/local/lib/python2.4', '/usr/
local/lib/python2.4/plat-freebsd5', '/usr/local/lib/python2.4/lib-
tk', '/usr/local/lib/python2.4/lib-dynload', '/usr/
Joe Auty <[EMAIL PROTECTED]> writes:
> On May 22, 2006, at 8:27 PM, Michael P. Soulier wrote:
>
>> On 5/22/06, Joe Auty <[EMAIL PROTECTED]> wrote:
>>> Starting up Mailman on one machine I'm on produces the following
>>> error message (see below). For some reason, this is not a problem
>>
>> Test y
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 22, 2006, at 8:27 PM, Michael P. Soulier wrote:
On 5/22/06, Joe Auty <[EMAIL PROTECTED]> wrote:
Starting up Mailman on one machine I'm on produces the following
error message (see below). For some reason, this is not a problem
Test your p
On 5/22/06, Joe Auty <[EMAIL PROTECTED]> wrote:
Starting up Mailman on one machine I'm on produces the following
error message (see below). For some reason, this is not a problem
Test your python installation. Try
python -c 'import sys; print sys.path'
See which python interpreter this is, /u
22 matches
Mail list logo
