Date: Sun, 25 Feb 2018 17:42:03 -0800 From: Eitan Adler <lists@eitanadler.com> To: Alan Somers <asomers@freebsd.org> Cc: freebsd-current Current <freebsd-current@freebsd.org> Subject: Re: iocage on current seems broken / ascii errors with iocage Message-ID: <CAF6rxg=nDYovCA=Wc6exZ=qcbpzjis1m=W3uM21aUNZw3GGmbQ@mail.gmail.com> In-Reply-To: <CAOtMX2jG20r9F8E_d8BU%2BQP7r7SUahA5npnmxZa0x-=LDn5zCQ@mail.gmail.com> References: <CAF6rxgnmfuL60UoydnjfaEA1w4CqtF73XCxwTXUNZH%2BxhLwAvA@mail.gmail.com> <CAOtMX2jG20r9F8E_d8BU%2BQP7r7SUahA5npnmxZa0x-=LDn5zCQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 25 February 2018 at 15:15, Alan Somers <asomers@freebsd.org> wrote: > On Sun, Feb 25, 2018 at 3:50 PM, Eitan Adler <lists@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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAF6rxg=nDYovCA=Wc6exZ=qcbpzjis1m=W3uM21aUNZw3GGmbQ>