Vick Khera wrote:
> any possibility of snapping a 1.2.18 with the fix for this problem?
> people on freebsd lists keep asking to update the port from 1.2.16,
> but I cannot do that since it will break existing 1.2.17 installations
> on upgrade.
>
> On Fri, Oct 23, 2009 at 9:10 AM, Jeff <threshar at torgo.978.org> wrote:
>   
>> On Oct 21, 2009, at 8:55 AM, Christopher Browne wrote:
>>     
>>> The following patch should rectify this...
>>>       
>   [ ... ]
>   
>>> That's working and committed to 2.0 + HEAD.
>>>
>>>       
>> This works for me.
>> My origin is 8.2, slave is 8.4 (preparing for an upgrade! wheeee!)
>>
>>     
> _______________________________________________
> Slony1-general mailing list
> Slony1-general at lists.slony.info
> http://lists.slony.info/mailman/listinfo/slony1-general
>   
Done.

See <http://slony.info/> for 1.2.18...