On 06/17/2016 07:22 PM, Fabian Santiago wrote:
>
> Now, any chance you could give me a hand with mm3? Hehe...
I have recently installed 2 'production' instances of MM 3 basically
starting with mailman-bundler, but upgrading all the Mailman components
to the heads of their respective branches
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Thank you Sir!
Now, any chance you could give me a hand with mm3? Hehe...
On June 17, 2016 9:13:29 PM EDT, Mark Sapiro wrote:
>On 06/17/2016 04:50 PM, Fabian Santiago wrote:
>> I run 2.1.22; that ok to install on top of?
>
>
>If you installed
On 06/17/2016 04:50 PM, Fabian Santiago wrote:
> I run 2.1.22; that ok to install on top of?
If you installed 2.1.22 from source, you can just bzr branch that branch
and configure it with exactly the same configure command you used for
2.1.22 and make install it to upgrade.
There should be no pr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
I run 2.1.22; that ok to install on top of?
On June 17, 2016 5:25:34 PM EDT, Mark Sapiro wrote:
>On 06/17/2016 11:39 AM, Fabian Santiago wrote:
>>
>> I've come across:
>>
>https://wiki.list.org/DOC/How%20do%20I%20make%20the%20archives%20searchable
On 06/17/2016 11:39 AM, Fabian Santiago wrote:
>
> I've come across:
> https://wiki.list.org/DOC/How%20do%20I%20make%20the%20archives%20searchable
>
> but the info there seems outdated. Ht://dig won't even ./configure on my
> centos 7.2.x box.
I use ht://Dig and essentially the Mailman branch a
Hello,
What is the current best way of implementing searchable archives hosted
directly by my own server? Thanks.
I've come across:
https://wiki.list.org/DOC/How%20do%20I%20make%20the%20archives%20searchable
but the info there seems outdated. Ht://dig won't even ./configure on my
centos 7.2.x bo
