Some concerns about our postgresql and plpython ports

Chris Rees crees at
Wed Aug 17 17:24:24 UTC 2011

On 17 August 2011 17:56, Ruslan Mahmatkhanov <cvs-src at> wrote:
> I'm sorry, Mark, but your mailserver still dislikes me, so i can't reply to
> to you directly:
> """
> <linimon at>: host[] said: 553 5.7.1
> <cvs-src at>: Sender address rejected: Refused Blocked due
> to mail abuse: go away spamming scum (in reply to RCPT TO command)
> """
> -------- Исходное сообщение --------
> Тема: Re: Some concerns about our postgresql and plpython ports
> Дата: Wed, 17 Aug 2011 20:50:26 +0400
> От: Ruslan Mahmatkhanov <cvs-src at>
> Кому: Mark Linimon <linimon at>
> Mark Linimon wrote on 17.08.2011 20:26:
>> have you emailed the individual port maintainers?
> No. plpython is unmantained, postgresql ports are belongs to girgen@,
> that (by looking at commit's history) is not there, since all the recent
> changes was committed with "maintainer timeout" message.
>> fwiw, I usually recommend send-pr for large fixes (OTOH dividing it up
>> with one PR for postgresql and one for plpython would make life a little
>> easier for us.)
>> mcl
> Ok, i'll do right now. But you should take into account that plpython
> can't be fixed without touching postgresqlXX-server ports. I can split
> this up to python pkg-plist fix, postgresql9x-client build fix, and the
> very plpython unbreak.

Careful; those timeout commits were only mine from the USERS change
(unfortunately I had to revert them too... I wouldn't go so far as to
say he's inactive-- in fact I had spoken to him recently IIRC.


More information about the freebsd-ports mailing list