Date: Wed, 10 Apr 2019 10:57:22 -0500 From: "Matthew D. Fuller" <fullermd@over-yonder.net> To: Torfinn Ingolfsen <tingox@gmail.com> Cc: FreeBSD Ports ML <freebsd-ports@freebsd.org> Subject: Re: upgrade of port fails because of existing link Message-ID: <20190410155722.GJ6019@over-yonder.net> In-Reply-To: <CAJ_iqtZdZQLJARUJ32O5kc6Y-jE--xJeYOwihPqe6WZDmpOaXA@mail.gmail.com> References: <CAJ_iqtZdZQLJARUJ32O5kc6Y-jE--xJeYOwihPqe6WZDmpOaXA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Apr 10, 2019 at 04:13:33PM +0200 I heard the voice of Torfinn Ingolfsen, and lo! it spake thus: > > Often, a port fails to upgrade because of an existing link. Example: > > ---> Preserving /usr/local/lib/qt5/libQt5DBus.so.5 as > /usr/local/lib/compat/pkg/libQt5DBus.so.5 > cp: symlink: libQt5DBus.so.5.12.1: File exists > Copy failed! That's not the port, that's portupgrade and its handling of stashed up compat libs. It has a bug and does something poorly with symlinks. It bites me on mesa-libs regularly too, and occasionally elsewhere. I grumble, manually delete the compat symlink, then go `portupgrade -w` the thing again to get it to retry the install. And hope it annoys someone else enough that they go fix it... -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190410155722.GJ6019>