From nobody Mon Nov 08 07:54:38 2021 X-Original-To: freebsd-pkg@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id D7309184AF99 for ; Mon, 8 Nov 2021 07:54:41 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Hnk0d5q28z3tS7; Mon, 8 Nov 2021 07:54:41 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: from aniel.nours.eu (nours.eu [IPv6:2001:41d0:8:3a4d::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: bapt) by smtp.freebsd.org (Postfix) with ESMTPSA id 9021F7913; Mon, 8 Nov 2021 07:54:41 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: by aniel.nours.eu (Postfix, from userid 1001) id AF5579B9DB; Mon, 8 Nov 2021 08:54:38 +0100 (CET) Date: Mon, 8 Nov 2021 08:54:38 +0100 From: Baptiste Daroussin To: freebsd@ohreally.nl Cc: freebsd-pkg@FreeBSD.org Subject: Re: Questions about /usr/local/lib/compat/pkg Message-ID: <20211108075438.jtqkak6n22n5rlg7@aniel.nours.eu> References: <15967907-03dc-a2ab-df86-6097d8d808f6@ohreally.nl> List-Id: Binary package management and package tools discussion List-Archive: https://lists.freebsd.org/archives/freebsd-pkg List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-pkg@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <15967907-03dc-a2ab-df86-6097d8d808f6@ohreally.nl> X-ThisMailContainsUnwantedMimeParts: N On Sun, Nov 07, 2021 at 08:36:54PM +0100, freebsd@ohreally.nl wrote: > Hello list, > > I have some questions about /usr/local/lib/compat/pkg. I can find very > little documentation about that directory. /usr/local/lib/compat/pkg is mecanism to save old libraries, during upgrade, ensure programs still linked to those old libs continues to run It only happens if BACKUP_LIBRARIES is set to true (which is not the default). > > My current problem is that devel/boost-libs won't upgrade, with the > following message: > > No such file or directory @ rb_check_realpath_internal - > /usr/local/lib/compat/pkg/libboost_atomic.so.1 > > Actually, the mentioned file does exist. But it is a symlink to > libboost_atomic.so.1.72.0 which does not exist. So the file pointed does not exist > > So my first question is if I can just delete this dead symlink, in the hopes > that the upgrade will then succeed? Yes you can > > But I have some more questions. > > What exactly is this directory for? > The pkg.conf(5) man page states that libraries are backed up to this > directory (BACKUP_LIBRARY_PATH), but it doesn't say what these backups are > used for. Or when the backups should be restored. And when they can be > deleted. Pkg do not use them. > > Also, just above that line in the pkg.conf man page, it says that > BACKUP_LIBRARIES should be set to true to have libraries backed up. However, > it also says that this variable defaults to NO, and I never edited pkg.conf > (and I just checked: this var is not set in the default file). > So why does pkg back up these libraries anyway? > In my case, this directory contains about 30 libraries, and over twice that > amount in symlinks. What does pkg -vv shows you ? > > Thanks to anyone who can shine a light on this for me. > > Best, > Rob > > -- > :wq > >