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

2018-02-25 Thread Eitan Adler
On 25 February 2018 at 15:15, Alan Somers wrote: > On Sun, Feb 25, 2018 at 3:50 PM, Eitan Adler 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 > maint

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

2018-02-25 Thread Alan Somers
On Sun, Feb 25, 2018 at 3:50 PM, Eitan Adler wrote: > ∴sudo iocage activate zroot > ∴sudo iocage list > +-+--+---+-+-+ > | JID | NAME | STATE | RELEASE | IP4 | > +=+==+===+=+=+ > +-+--+---+-+-+ > ∴sudo iocage create -r 11.1-R

iocage on current seems broken / ascii errors with iocage

2018-02-25 Thread Eitan Adler
∴sudo iocage activate zroot ∴sudo iocage list +-+--+---+-+-+ | JID | NAME | STATE | RELEASE | IP4 | +=+==+===+=+=+ +-+--+---+-+-+ ∴sudo iocage create -r 11.1-RELEASE Fetching: 11.1-RELEASE Downloading : MANIFEST [#