Date: Tue, 05 Aug 2014 11:25:54 -0500 From: Bryan Drewery <bdrewery@FreeBSD.org> To: office@FreeBSD.org Cc: ports@freebsd.org Subject: Libreoffice library caching [was Re: Yet another pkg bug?] Message-ID: <53E10592.1000308@FreeBSD.org> In-Reply-To: <62714296e76c28f63d8b7ca430882a37@shatow.net> References: <53DB9BF4.5070208@netfence.it> <62714296e76c28f63d8b7ca430882a37@shatow.net>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --NnNkTRCc7DcAQ3dg83eM13T97grGLfcKJ Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Can office@ chime in on this? On 8/1/2014 7:27 PM, Bryan Drewery wrote: > On 2014-08-01 08:53, Andrea Venturoli wrote: >> Hello. >> >> On a 10.0/amd64 system: >> >>> # cat /usr/ports/UPDATING >>> ... >>> 20140730: >>> AFFECTS: users of security/libgcrypt >>> AUTHOR: pi@FreeBSD.org >>> >>> libgcrypt has been updated to 1.6.1 and all shared libraries >>> versions have >>> been bumped. So you need to rebuild all applications that depend on= >>> libgcrypt. >>> >>> # portmaster -r libgcrypt >>> or >>> # portupgrade -fr security/libgcrypt >>> or >>> # pkg install -fR security/libgcrypt >>> ... >>> # pkg info -r libgcrypt|less >>> libgcrypt-1.6.1_1: >>> libgnome-keyring-2.32.0_8 >>> gnupg-2.0.25_1 >>> libxslt-1.1.28_4 >>> # pkg info -r libxslt | less >>> libxslt-1.1.28_4: >>> rarian-0.8.1_1 >>> gnome-doc-utils-0.20.10_2 >>> gtk-doc-1.18_1 >>> inkscape-0.48.4_4 >>> vala-0.20.1_1 >>> policykit-gnome-0.9.2_7 >>> raptor2-2.0.14 >>> xmlto-0.0.26_2 >>> shiboken-1.2.2 >>> apiextractor-0.10.10_2 >>> libreoffice-4.2.5_3 >>> # portupgrade -frn libgcrypt >>> ---> Listing the results (+:done / -:ignored / *:skipped / !:failed)= >>> + security/libgcrypt (libgcrypt-1.6.1_1 -> libgcrypt-1.6.1_1)= >>> + textproc/libxslt (libxslt-1.1.28_4 -> libxslt-1.1.28_4) >>> + security/gnupg (gnupg-2.0.25_1 -> gnupg-2.0.25_1) >>> + security/libgnome-keyring (libgnome-keyring-2.32.0_8 -> >>> libgnome-keyring-2.32.0_8) >> >> So, libreoffice is not rebuilt and after "portupgrade -fr libgcrypt"..= =2E >> >>> # libchk -v | less -S >>> ... >>> Binaries that are linked with: /usr/local/lib/compat/pkg/libgcrypt.so= =2E19 >>> /usr/local/lib/compat/pkg/libsoup-gnome-2.4.so.1.5.0 >>> /usr/local/lib/libreoffice/program/libxsltfilterlo.so >> >> ... libreoffice is still using the old library. >> >> >=20 > Agreed it is not a pkg problem, nor a portupgrade problem. >=20 > libreoffice is not directly depending on libgcrypt so it was not > rebuilt. Only direct dependencies are rebuilt. But this is not really > the problem. The problem is that Libreoffice seems to be doing somethin= g > special by building its own libxsltfilterlo.so into its own directory. > So the libxslt rebuild had no idea about it. It's not a file actually > provided by libxslt. >=20 > # pkg info -l libxslt|grep /usr/local/lib > /usr/local/lib/libexslt.a > /usr/local/lib/libexslt.la > /usr/local/lib/libexslt.so > /usr/local/lib/libexslt.so.8 > /usr/local/lib/libxslt.a > /usr/local/lib/libxslt.la > /usr/local/lib/libxslt.so > /usr/local/lib/libxslt.so.2 >=20 > Note the lack of libxsltfilterlo.so. >=20 > I'd say the instructions were lacking. My guess is a small handfull of > people realize what's going on here and none of the other committers do= =2E > So it's very likely that many UPDATING entries need special libreoffice= > care as well and have not had it documented. I.e., every dependency of > libreoffice would require rebuilding libreoffice. >=20 > I'm not sure what this program/ dir is, perhaps some cache. It would be= > safer to have it disabled so this special care is not needed. >=20 >=20 >> >> Is the command provided in "UPGRADING" wrong? >> Is it yet another bug in pkg? In portupgrade? In libreoffice? >> Is something wrong in my setup? >> >> bye & Thanks >> av. --=20 Regards, Bryan Drewery --NnNkTRCc7DcAQ3dg83eM13T97grGLfcKJ Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJT4QWSAAoJEDXXcbtuRpfPrXwH/2OT9NL52OlpR7cXd79vEwLu I0DDDOL2YhMJvM3nIhedp+JNhYhmorFFykgoSnUAvmzEcSvncj2mzlZ7hrKLRxI3 MslM8IV/INheujLaa1uLBC7ojYK4GqUxZCIGznXVmgrWjzBegBAjO4gVOIl4GTi9 89FbWEob77Rr2QUdyTUYQZAq3AZeqAFOpCr6keRmZ9pm0U6HV2qsCD3hNXzJbNxs 0nAI17ysYxugBm65RvoUe5L/E2mUcb5Mr1SttkX+xbxROGbv6dqGK7a6dZoopOj5 YI3Rg9mpGj9ynFP/cpds6ALs1D46fqUKW0KMJBUjU2qUwnhKG5Nm71Gv5lPP9mU= =AC33 -----END PGP SIGNATURE----- --NnNkTRCc7DcAQ3dg83eM13T97grGLfcKJ--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?53E10592.1000308>