Re: Setting for displaying utf8 characters on all vt consoles results in panic on 14-CURRENT and 13.0-ALPHA3

2021-01-31 Thread Yasuhiro Kimura
From: Yasuhiro Kimura Subject: Setting for displaying utf8 characters on all vt consoles results in panic on 14-CURRENT and 13.0-ALPHA3 Date: Mon, 01 Feb 2021 11:41:35 +0900 (JST) > To display utf8 characters on all vt console I did following settings. > > 1. Download GNU Unifont BDF file >

Re: (n244517-f17fc5439f5) svn stuck forever in /usr/ports?

2021-01-31 Thread Rick Macklem
Rick Macklem wrote: >Guido Falsi wrote: >[good stuff snipped] >>Performed a full bisect. Tracked it down to commit aa906e2a4957, adding >>KTLS support to embedded OpenSSL. >> >>I filed a bug report about this: >> >>https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253135 >> >> >>Apart from switchin

Setting for displaying utf8 characters on all vt consoles results in panic on 14-CURRENT and 13.0-ALPHA3

2021-01-31 Thread Yasuhiro Kimura
To display utf8 characters on all vt console I did following settings. 1. Download GNU Unifont BDF file (http://unifoundry.com/pub/unifont/unifont-13.0.05/font-builds/unifont-13.0.05.bdf.gz) 2. gunzip unifont-13.0.05.bdf.gz 3. vtfontcvt unifont-13.0.05.bdf unifont.fnt 4. cp unifont.fnt /usr/sh

Re: (n244517-f17fc5439f5) svn stuck forever in /usr/ports?

2021-01-31 Thread Rick Macklem
Guido Falsi wrote: [good stuff snipped] >Performed a full bisect. Tracked it down to commit aa906e2a4957, adding >KTLS support to embedded OpenSSL. > >I filed a bug report about this: > >https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253135 > > >Apart from switching to svn:// scheme, another wor

Re: (n244517-f17fc5439f5) svn stuck forever in /usr/ports?

2021-01-31 Thread Guido Falsi via freebsd-current
On 31/01/21 10:35, Hartmann, O. wrote: On Sat, 30 Jan 2021 16:22:50 +0100 Guido Falsi via freebsd-current wrote: On 30/01/21 12:34, Guido Falsi via freebsd-current wrote: On 30/01/21 11:25, Tomoaki AOKI wrote: On Sat, 30 Jan 2021 07:39:23 +0100 "Hartmann, O." wrote: We recently updated

Re: Failure of release build with release.sh on 14-CURRENT amd64

2021-01-31 Thread tech-lists
Hello, I also tried to build a release and failed. My context is different to yours, though. The failure error is different. Just thought I'd mention it as "make release on -current is broken for me as well". In my context, it ignores the installed pkg and tries, and fails to get a -current pkg b

Re: (n244517-f17fc5439f5) svn stuck forever in /usr/ports?

2021-01-31 Thread Hartmann, O.
On Sat, 30 Jan 2021 16:22:50 +0100 Guido Falsi via freebsd-current wrote: > On 30/01/21 12:34, Guido Falsi via freebsd-current wrote: > > On 30/01/21 11:25, Tomoaki AOKI wrote: > >> On Sat, 30 Jan 2021 07:39:23 +0100 > >> "Hartmann, O." wrote: > >> > >>> We recently updated to FreeBSD 14.0-C