From owner-freebsd-questions@freebsd.org Tue Apr 6 02:50:46 2021 Return-Path: Delivered-To: freebsd-questions@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id C7EE65CE5FA for ; Tue, 6 Apr 2021 02:50:46 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Received: from outgoing.tristatelogic.com (segfault.tristatelogic.com [69.62.255.118]) by mx1.freebsd.org (Postfix) with ESMTP id 4FDsTd6K9rz4dp5 for ; Tue, 6 Apr 2021 02:50:45 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Received: by segfault.tristatelogic.com (Postfix, from userid 1237) id DCF7E4E670; Mon, 5 Apr 2021 19:50:44 -0700 (PDT) From: "Ronald F. Guilmette" To: freebsd-questions@freebsd.org Subject: Yet another (fatal?) pkg upgrade error MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2516.1617677444.1@segfault.tristatelogic.com> Date: Mon, 05 Apr 2021 19:50:44 -0700 Message-ID: <2517.1617677444@segfault.tristatelogic.com> X-Rspamd-Queue-Id: 4FDsTd6K9rz4dp5 X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of rfg@tristatelogic.com designates 69.62.255.118 as permitted sender) smtp.mailfrom=rfg@tristatelogic.com X-Spamd-Result: default: False [-3.01 / 15.00]; ARC_NA(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[69.62.255.118:from]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; DMARC_NA(0.00)[tristatelogic.com]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[69.62.255.118:from:127.0.2.255]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.71)[-0.708]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:14051, ipnet:69.62.128.0/17, country:US]; MAILMAN_DEST(0.00)[freebsd-questions]; SUBJECT_HAS_QUESTION(0.00)[] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Apr 2021 02:50:46 -0000 I'm trying to work out what I can do to get around the problem(s) described in my prior message, and now it appears that even the "pkg info" command is seriously malfunctioning for some unknown reason, making the resolution of that prior problem all that much harder. Specifically, in response to the following command: pkg info --file /usr/local/lib/libglib-2.0.so.0 I get only the following rather unhelpfuland uninformative error message: pkg: archive_read_open_fd: Unrecognized archive format What is the solution for this? It appears that some data base file somewhere (where?) is most probably corrupted. (I don't believe that corruption was in any way my fault, but I am altogether less interested in assigning blame at the moment than I am in just fixing the problem(s).) So, what data base file, specifically, is corrupted and how many I recreate or regerenate it again into a "good" state? And why doesn't the above error message provide me with even the slightest clue as to what file, exactly, has gone goofy? Would it have been all that hard to include the pathname, you know, just as a small courtesy for exactly such situations?