On Wed, Mar 31, 2021 at 7:37 PM Glen Barber wrote:
>
> On Wed, Mar 31, 2021 at 11:22:58AM -0500, Antonio Olivares wrote:
> > On Wed, Mar 31, 2021 at 11:03 AM Glen Barber wrote:
> > >
> > > On Tue, Mar 30, 2021 at 07:54:45PM -0500, Antonio Olivares wrote:
> > > > Dear all,
> > > >
> > > > after up
On Wed, Mar 31, 2021 at 06:49:55PM -0400, Thomas Dickey wrote:
> On Wed, Mar 31, 2021 at 09:40:49PM +0200, Juraj Lutter wrote:
> >
> > > On 31 Mar 2021, at 15:53, Henric Jungheim wrote:
> > >
> > >>
> > >> Knowing that would help me see whether the problem is faulty
> > >> initialization
> > >
On Wed, Mar 31, 2021 at 09:40:49PM +0200, Juraj Lutter wrote:
>
> > On 31 Mar 2021, at 15:53, Henric Jungheim wrote:
> >
> >>
> >> Knowing that would help me see whether the problem is faulty initialization
> >> from libtextstyle (i.e., the SCREEN pointer is null, making the path via
> >> the s
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
> On 31 Mar 2021, at 15:53, Henric Jungheim wrote:
>
>>
>> Knowing that would help me see whether the problem is faulty initialization
>> from libtextstyle (i.e., the SCREEN pointer is null, making the path via
>> the static structure), or some ifdef-combination in ncurses that I've
>> neglecte
Also, this release seems to have gotten a lot more attention than
usual. So probably more people are testing.
On 3/31/21 1:24 PM, Rainer Duffner wrote:
Am 31.03.2021 um 17:58 schrieb Glen Barber :
A small set of updates that we consider blocking the 13.0 release have
been brought to our att
> Am 31.03.2021 um 17:58 schrieb Glen Barber :
>
> A small set of updates that we consider blocking the 13.0 release have
> been brought to our attention. As such, the 13.0-RELEASE schedule has
> been updated to include a fifth release candidate (RC5).
>
> The updated schedule is available on
On Tue, Mar 30, 2021 at 08:48:03PM -0400, Thomas Dickey wrote:
> On Tue, Mar 30, 2021 at 08:37:22AM +0200, Juraj Lutter wrote:
> > Hi,
> >
> > very similar behavior is observed in editors/poke, on recent 13.0-STABLE
> > (stable/13-85ad493677a2):
> >
> > (lldb) bt
> > * thread #1, name = 'poke',
On Wed, Mar 31, 2021 at 03:58:51PM +, Glen Barber wrote:
> A small set of updates that we consider blocking the 13.0 release have
> been brought to our attention. As such, the 13.0-RELEASE schedule has
> been updated to include a fifth release candidate (RC5).
>
> The updated schedule is avai
On Wed, Mar 31, 2021 at 11:22:58AM -0500, Antonio Olivares wrote:
> On Wed, Mar 31, 2021 at 11:03 AM Glen Barber wrote:
> >
> > On Tue, Mar 30, 2021 at 07:54:45PM -0500, Antonio Olivares wrote:
> > > Dear all,
> > >
> > > after updating to RC4 with
> > > # freebsd-update -r upgrade 13.0RC4
> > > W
On Wed, Mar 31, 2021 at 11:03 AM Glen Barber wrote:
>
> On Tue, Mar 30, 2021 at 07:54:45PM -0500, Antonio Olivares wrote:
> > Dear all,
> >
> > after updating to RC4 with
> > # freebsd-update -r upgrade 13.0RC4
> > When I shutdown, I get error messages AE_??? PCI
> >
> >
> > Press any key to reboo
On Fri, Mar 5, 2021 at 11:25 AM Graham Perrin wrote:
>
> On 05/03/2021 14:01, Antonio Olivares wrote:
> > On Thu, Mar 4, 2021 at 8:39 PM Graham Perrin wrote:
> >> On 05/03/2021 00:53, Antonio Olivares wrote:
> >>> … It had worked before since a while. But 2 updates ago I see this error
> >>> mes
On Tue, Mar 30, 2021 at 07:54:45PM -0500, Antonio Olivares wrote:
> Dear all,
>
> after updating to RC4 with
> # freebsd-update -r upgrade 13.0RC4
> When I shutdown, I get error messages AE_??? PCI
>
>
> Press any key to reboot
>
> It shutdown before from 13.0-BETA4 updated all the way to RC3.
A small set of updates that we consider blocking the 13.0 release have
been brought to our attention. As such, the 13.0-RELEASE schedule has
been updated to include a fifth release candidate (RC5).
The updated schedule is available on the FreeBSD Project website:
https://www.freebsd.org/releases
Am 31.03.21 um 14:24 schrieb Ronald Klop:
Van: Jochen Neumeister
Datum: woensdag, 31 maart 2021 13:26
Aan: Christoph Moench-Tegeder ,
freebsd-current@freebsd.org
Onderwerp: Re: Blacklisted certificates
Am 31.03.21 um 13:02 schrieb Christoph Moench-Tegeder:
> ## Jochen Neumeister (jon...@f
> On 31 Mar 2021, at 15:53, Henric Jungheim wrote:
>
>>
>> So... the question I have is what is $TERM in this case,
>> and where is the related terminal description (in terminfo or termcap).
>
> In the example in my original email, $TERM was "xterm-256color"
> (connected through "Windows Term
On Wed, Mar 31, 2021 at 7:25 AM Ronald Klop wrote:
>
>
> Van: Jochen Neumeister
> Datum: woensdag, 31 maart 2021 13:26
> Aan: Christoph Moench-Tegeder ,
> freebsd-current@freebsd.org
> Onderwerp: Re: Blacklisted certificates
> >
> >
> > Am 31.03.21 um 13:02 schrieb Christoph Moench-Tegeder:
> >
Van: Jochen Neumeister
Datum: woensdag, 31 maart 2021 13:26
Aan: Christoph Moench-Tegeder , freebsd-current@freebsd.org
Onderwerp: Re: Blacklisted certificates
Am 31.03.21 um 13:02 schrieb Christoph Moench-Tegeder:
> ## Jochen Neumeister (jon...@freebsd.org):
>
>> Why are this certificates bl
On Wed, 31 Mar 2021 13:02:21 +0200
Christoph Moench-Tegeder wrote:
> ## Jochen Neumeister (jon...@freebsd.org):
>
> > Why are this certificates blacklisted?
>
> Various reasons:
> - Symantec (which owned Thawte and VeriSign back in the time) made
> the news in a bad way:
> https://www.
Am 31.03.21 um 13:02 schrieb Christoph Moench-Tegeder:
## Jochen Neumeister (jon...@freebsd.org):
Why are this certificates blacklisted?
Various reasons:
- Symantec (which owned Thawte and VeriSign back in the time) made
the news in a bad way:
https://www.theregister.com/2017/09/12/chr
## Jochen Neumeister (jon...@freebsd.org):
> Why are this certificates blacklisted?
Various reasons:
- Symantec (which owned Thawte and VeriSign back in the time) made
the news in a bad way:
https://www.theregister.com/2017/09/12/chrome_66_to_reject_symantec_certs/
- some certificates are sim
Hi,
a make installworld stop with this:
>>> Installing everything completed on Wed Mar 31 11:45:55 CEST 2021
--
Scanning /usr/share/certs/blacklisted for certificates...
Scanning /usr/share/certs/trusted for certificates...
Skipping bl
On 2021-03-28 16:09, Hans Petter Selasky wrote:
> On 3/27/21 11:54 AM, Santiago Martinez wrote:
>> Hi, i have the same output as @Nils B. If i run with steal =2 and dtrace the
>> micro stutter doesn't happen but as soon as i stop the dtrace script it the
>> stutters come back again.
>>
>
> Here
>> I have trouble with recent 14.0-CURRENT 146 (e.x. main-6a762cfae,
>> main-3ead60236, main-25bfa4486).
>> It works well on recent 14.0-CURRENT until starting firefox.
>> If I start firefox (v87.0), system freeze but no core dumps.
>> If it booted old kernel 145 (e.x. main-b5449c92
28.03.2021 08:03, Masachika ISHIZUKA пишет:
> I have trouble with recent 14.0-CURRENT 146 (e.x. main-6a762cfae,
> main-3ead60236, main-25bfa4486).
> It works well on recent 14.0-CURRENT until starting firefox.
> If I start firefox (v87.0), system freeze but no core dumps.
> If it booted
25 matches
Mail list logo
