b-vol wrote:
>The problem seems to
>be 'bin/update' which runs only on new installations (where there is not
>already a mailing list configured).
The problem appeared when bin/update did "import md5", but if
bin/update hadn't run, Mailman would have encountered the same problem
in operatio
On Thursday 07 August 2008 03:40:07 pm Mark Sapiro wrote:
> b-vol wrote:
> >On Wednesday 06 August 2008 03:29:13 pm Mark Sapiro wrote:
> >> I've seen this exact problem myself. In my case, I had python 2.4.3
> >> installed in /usr and I installed python 2.5.1 from source in
> >> /usr/local. I don't
b-vol wrote:
>On Wednesday 06 August 2008 03:29:13 pm Mark Sapiro wrote:
>> I've seen this exact problem myself. In my case, I had python 2.4.3
>> installed in /usr and I installed python 2.5.1 from source in
>> /usr/local. I don't remember the details, but I played around with
>> symlinks and mad
On Wednesday 06 August 2008 03:29:13 pm Mark Sapiro wrote:
> I've seen this exact problem myself. In my case, I had python 2.4.3
> installed in /usr and I installed python 2.5.1 from source in
> /usr/local. I don't remember the details, but I played around with
> symlinks and made some progress, bu
b-vol wrote:
>
>I am new to this list. i have been trying to compile mailman-2.1.10 and
>mailman-2.1.11 (I have compiled mailman successfully a couple of years
>ago ). The computer is an athlon-based PC with LFS
>(linuxfromscratch) -kernel 2.6.25.8, gcc-4.2.2, openssl-0.98 is
>in /usr/lo
Greetings,
I am new to this list. i have been trying to compile mailman-2.1.10 and
mailman-2.1.11 (I have compiled mailman successfully a couple of years
ago ). The computer is an athlon-based PC with LFS
(linuxfromscratch) -kernel 2.6.25.8, gcc-4.2.2, openssl-0.98 is
in /usr/local and
