From owner-freebsd-current@freebsd.org Wed Oct 17 08:38:13 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1BC5810CDB11 for ; Wed, 17 Oct 2018 08:38:13 +0000 (UTC) (envelope-from brennan@umanwizard.com) Received: from smtp.umanwizard.com (smtp.umanwizard.com [54.203.248.109]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1FFB7766D8; Wed, 17 Oct 2018 08:34:15 +0000 (UTC) (envelope-from brennan@umanwizard.com) From: Brennan Vincent To: Kubilay Kocak , Date: Wed, 17 Oct 2018 04:36:00 Subject: Re: Git segfaulting in libcrypto.so when trying to clone. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Oct 2018 08:38:13 -0000 No, I've never run `delete-old` and `delete-old-lib` while upgrading. I can try upgrading again tomorrow and running those. But if my installation of curl is for whatever reason depending on libcrypto.so.8 and that command deletes it, won't that just cause curl to stop working? (I tried manually moving libcrypto.so.8 to libcrypto.so.8.bak and as expected, now `git clone` failed because the .so couldn't be found.)