Re: iocage on current seems broken / ascii errors with iocage

From: Eitan Adler <lists_at_eitanadler.com>
Date: Sun, 25 Feb 2018 17:42:03 -0800
On 25 February 2018 at 15:15, Alan Somers <asomers_at_freebsd.org> wrote:
> On Sun, Feb 25, 2018 at 3:50 PM, Eitan Adler <lists_at_eitanadler.com> wrote:

>> What should I do from here?
>>
>
> It's a well-known problem.  You need to patch your copy of py-libzfs.
> Unfortunately, the patch hasn't been picked up by upstream because the port
> maintainer believes it to be incorrect, but hasn't found the correct
> solution yet.

Thanks! I searched by email but not the iocage project. That fixed it.

-- 
Eitan Adler
Received on Mon Feb 26 2018 - 00:42:35 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:15 UTC