: Re: [Mailman-Users] Mailman would not start after upgrade to 2.1.26
On 02/12/2018 12:34 PM, Amardeo Sarma wrote:
>
> Does anyone have an idea what could have changed the write permissions for
> the logs during an upgrade? I use portmaster under FreeBSD.
This would seem to be
On 2/13/2018 12:29 PM, Keith Seyffarth wrote:
If you're installing from ports, whether building from within the ports
tree or using a port management tool like portupgrade or portmaster, you
are installing from source.
...installing using the source code of whatever version the port is
Carl Zwanzig writes:
> On 2/13/2018 10:25 AM, Mark Sapiro wrote:
>> This would seem to be an issue with FreeBSD ports. You should report
>> this to whoever is responsible for that
>
> FWIW, while I like FreeBSD's ports & packages, I've found that installing
> mailman from the
On 2/13/2018 10:25 AM, Mark Sapiro wrote:
This would seem to be an issue with FreeBSD ports. You should report
this to whoever is responsible for that
FWIW, while I like FreeBSD's ports & packages, I've found that installing
mailman from the source generally is more reliable and updating is
On 02/12/2018 12:34 PM, Amardeo Sarma wrote:
>
> Does anyone have an idea what could have changed the write permissions for
> the logs during an upgrade? I use portmaster under FreeBSD.
This would seem to be an issue with FreeBSD ports. You should report
this to whoever is responsible for
Hi,
After upgrading to Mailman 2.1.26 via ports in FreeBSD 11.1 and a reboot of the
server, I just could not start Mailman at all. It would not indicate any error.
The Mailman logs here: /usr/local/mailman/logs did not record anything.
On second looks, I found that, after the upgrade, the