Date: Sat, 19 Mar 2022 12:33:13 -0700 From: Mark Millard <marklmi@yahoo.com> To: Mark Johnston <markj@FreeBSD.org> Cc: freebsd-ports@freebsd.org, FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org> Subject: Re: git: 43741377b143 - main - security/openssl: Security update to 1.1.1n Message-ID: <9F2CBEBA-040D-4628-BCC3-032D38F06B00@yahoo.com> In-Reply-To: <A21C14CC-7DB8-49B0-8C36-C43E8AFDD636@yahoo.com> References: <A21C14CC-7DB8-49B0-8C36-C43E8AFDD636@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 that point. May be the history will help. https://lists.freebsd.org/archives/freebsd-current/2021-November/001052.html I've not had problems with the issue on main since then. === Mark Millard marklmi at yahoo.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9F2CBEBA-040D-4628-BCC3-032D38F06B00>