Re: Mariabackup core dump

On 2021 Apr 20, at 13:06, @lbutlr wrote: > On 20 Apr 2021, at 11:34, Kurt Jaeger wrote: >> >>> >>> >>> This was posted 3 years ago, and I am having the identical issue. From what >>> I can see on that page, no activity has taken place. Anyone have a

Re: git: 43741377b143 - main - security/openssl: Security update to 1.1.1n

On 2022-Mar-19, at 14:34, Mark Millard wrote: > On 2022-Mar-19, at 14:24, Mark Millard wrote: > >> On 2022-Mar-19, at 12:54, Mark Johnston wrote: >> >>> On Sat, Mar 19, 2022 at 12:00:20PM -0700, Mark Millard wrote: On 2022-Mar-19, at 11:07, Thomas Zander wrote: > On Sat, 19 Ma

Re: git: 43741377b143 - main - security/openssl: Security update to 1.1.1n

On 2022-Mar-19, at 14:24, Mark Millard wrote: > On 2022-Mar-19, at 12:54, Mark Johnston wrote: > >> On Sat, Mar 19, 2022 at 12:00:20PM -0700, Mark Millard wrote: >>> On 2022-Mar-19, at 11:07, Thomas Zander wrote: >>> On Sat, 19 Mar 2022 at 18:32, Mark Millard wrote: > May be repo

Re: git: 43741377b143 - main - security/openssl: Security update to 1.1.1n

## Mark Johnston (ma...@freebsd.org): > > The primary difference is that I've never used ccache and > > did not try to do so here. The "zfs pool is a single disk, > > no raid, mirror or anything fancy" is accurate, as is the > > use of ALLOW_MAKE_JOBS= . That's basically my setup: "single-SSD zpo

Re: git: 43741377b143 - main - security/openssl: Security update to 1.1.1n

On 2022-Mar-19, at 12:54, Mark Johnston wrote: > On Sat, Mar 19, 2022 at 12:00:20PM -0700, Mark Millard wrote: >> On 2022-Mar-19, at 11:07, Thomas Zander wrote: >> >>> On Sat, 19 Mar 2022 at 18:32, Mark Millard wrote: May be report to Mark J. how to run the same test builds that fail

Re: git: 43741377b143 - main - security/openssl: Security update to 1.1.1n

On Sat, Mar 19, 2022 at 12:00:20PM -0700, Mark Millard wrote: > On 2022-Mar-19, at 11:07, Thomas Zander wrote: > > > On Sat, 19 Mar 2022 at 18:32, Mark Millard wrote: > >> May be report to Mark J. how to run the same test builds > >> that failed for -p8 but worked for -p7? > > > > Sure, good po

Re: git: 43741377b143 - main - security/openssl: Security update to 1.1.1n

The reports of corrupted files with zero-bytes seemed vaguely familiar, including my own addition to the list. Turns out I'd reported such for main [so: 14] back in 2021-Nov. My context at the time was aarch64. The following has my report sequence, including where I got past the problem vs. before

Re: git: 43741377b143 - main - security/openssl: Security update to 1.1.1n

On 2022-Mar-19, at 11:07, Thomas Zander wrote: > On Sat, 19 Mar 2022 at 18:32, Mark Millard wrote: >> May be report to Mark J. how to run the same test builds >> that failed for -p8 but worked for -p7? > > Sure, good point. > A build that reliably causes broken packages on p8 but not on p7 for

Re: git: 43741377b143 - main - security/openssl: Security update to 1.1.1n

> From: Mark Johnston > Date: Sat, 19 Mar 2022 12:42:59 -0400 > On Sat, Mar 19, 2022 at 12:40:45PM +0100, Thomas Zander wrote: > > On Sat, 19 Mar 2022 at 12:11, Rene Ladan wrote: > > > > > > On Sat, Mar 19, 2022 at 11:04:58AM +0100, Thomas Zander wrote: > > > > On Sat, 19 Mar 2022 at 09:00, Matt

FreeBSD ports you maintain which are out of date

Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you