Re: mail/mailman port installation failing

2014-05-30 Thread John Marshall
On 31/05/2014 00:36, Patrick Powell wrote: > I must be suffering from advanced memory loss--- when did > /usr/local/etc/ports.conf creep into this? > > Is there a link to documentation on this? /usr/local is the clue. It's not part of the base system, it belongs to a port (ports-mgmt/portconf).

Re: mail/mailman port installation failing

2014-05-30 Thread Patrick Powell
On 05/28/14 21:16, John Marshall wrote: On Wed, 28 May 2014, 16:36 +1000, John Marshall wrote: I'm having no joy trying to install mailman on a new system. Builds fine but won't install. Any tips appreciated. ===> Registering installation for mailman-2.1.18.1_1 pkg-static: lstat(/kits

Re: mail/mailman port installation failing

2014-05-29 Thread Matthias Andree
Am 29.05.2014 08:34, schrieb Lowell Gilbert: > John Marshall writes: > >> After helpful off-list mail from mandree@ which pointed at this being a >> local problem, I eventually found the following line in >> /usr/local/etc/ports.conf. >> >> mail/mailman: CONFIGURE_ARGS=--with-var-prefix=/data/m

Re: mail/mailman port installation failing

2014-05-28 Thread Lowell Gilbert
John Marshall writes: > After helpful off-list mail from mandree@ which pointed at this being a > local problem, I eventually found the following line in > /usr/local/etc/ports.conf. > > mail/mailman: CONFIGURE_ARGS=--with-var-prefix=/data/mailman > > One of those tweaks one implements to accom

Re: mail/mailman port installation failing

2014-05-28 Thread John Marshall
On Wed, 28 May 2014, 16:36 +1000, John Marshall wrote: > I'm having no joy trying to install mailman on a new system. Builds > fine but won't install. Any tips appreciated. > ===> Registering installation for mailman-2.1.18.1_1 > pkg-static: > lstat(/kits/ports/mail/mailman/work/stage/usr

mail/mailman port installation failing

2014-05-27 Thread John Marshall
I'm having no joy trying to install mailman on a new system. Builds fine but won't install. Any tips appreciated. I've tried winding the port back several versions (svn update -r) and still strike essentially the same snag, so I'm guessing this may have been triggered by a change somewhere other