On Fri, Feb 21, 2020 at 3:27 AM Pavel Timofeev wrote:
>
> пт, 10 янв. 2020 г. в 22:05, Kyle Evans :
> >
> > On Fri, Jan 10, 2020 at 12:59 PM Pavel Timofeev wrote:
> > >
> > > пт, 10 янв. 2020 г. в 17:48, Kyle Evans :
> > > >
> > > > On Fri, Jan 10, 2020 at 12:31 AM Pavel Timofeev
> > > > wrote:
On Sat, 15 Feb 2020 at 05:03, Bjoern A. Zeeb
wrote:
>
> I am also worried that the change will make a lot of machines
> unprotected upon updating to 13 if there is no big red warning flag
> before the install.
At least having sshd emit a warning is a prerequisite, certainly. I
don't yet know if t
On Fri, Feb 21, 2020 at 03:24:16PM +0100, O. Hartmann wrote:
> Hallo,
>
>
> recent CURRENT r358220 (host operating on FreeBSD 13.0-CURRENT #48 r358183:
> Thu Feb 20 22:33:34
> CET 2020 amd64), fails to build for me on a couple of boxes:
>
> [...]
>
I had no issues building r358220 from r3
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hallo,
recent CURRENT r358220 (host operating on FreeBSD 13.0-CURRENT #48 r358183: Thu
Feb 20 22:33:34
CET 2020 amd64), fails to build for me on a couple of boxes:
[...]
In file included from
/usr/src/contrib/llvm-project/llvm/include/llvm/Supp
A heads up for any powerd++ users on CURRENT. For me at least it's been
broken for a few weeks & a fix may not be forthcoming.
Link to GitHub issue: https://github.com/lonkamikaze/powerdxx/issues/10
-- Forwarded message -
De : Dominic Fandrey
Date: ven. 21 févr. 2020 04 h 30
Subje
пт, 10 янв. 2020 г. в 22:05, Kyle Evans :
>
> On Fri, Jan 10, 2020 at 12:59 PM Pavel Timofeev wrote:
> >
> > пт, 10 янв. 2020 г. в 17:48, Kyle Evans :
> > >
> > > On Fri, Jan 10, 2020 at 12:31 AM Pavel Timofeev wrote:
> > > >
> > > > чт, 9 янв. 2020 г. в 16:52, Pavel Timofeev :
> > > > >
> > > >
