Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 24 Apr 2015 07:21:53 -0700
From:      David Wolfskill <david@catwhisker.org>
To:        freebsd-ports@freebsd.org
Subject:   [Circumvented] issue updating ports after icu update
Message-ID:  <20150424142153.GM37361@albert.catwhisker.org>

next in thread | raw e-mail | index | archive | help

--NZtAI5QFBF0GmLcW
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Now that my older laptop has been replace with one that is a fair bit
faster, in addition to tracking stable/10 and head daily (and updating
installed ports under stable/10 daily) for i386, I'm also doing the same
for amd64 (on the same machine -- different slices of the same drive).

I'm using portmaster to update my ports (as I have for some years).

This morning, after building & booting:

FreeBSD g1-254.catwhisker.org 10.1-STABLE FreeBSD 10.1-STABLE #46  r281921M=
/281927:1001512: Fri Apr 24 04:24:32 PDT 2015     root@g1-254.catwhisker.or=
g:/common/S1/obj/usr/src/sys/CANARY  i386

running "portmaster -ad" informed me that the following actions were
to be taken:

=3D=3D=3D>>> The following actions will be taken if you choose to proceed:
        Upgrade icu-53.1 to icu-55.1
        Upgrade pkgconf-0.9.9 to pkgconf-0.9.10
        Upgrade R-3.0.2_3 to R-3.0.2_4
        Upgrade boost-libs-1.55.0_4 to boost-libs-1.55.0_5
        Upgrade harfbuzz-0.9.40 to harfbuzz-0.9.40_1
        Upgrade libvisio01-0.1.1 to libvisio01-0.1.1_1
        Upgrade libxul-31.6.0 to libxul-31.6.0_1
        Upgrade p5-IO-stringy-2.110_1 to p5-IO-stringy-2.111
        Upgrade qt4-corelib-4.8.6_4 to qt4-corelib-4.8.6_5
        Upgrade texlive-base-20140525_6 to texlive-base-20140525_7
        Upgrade webkit-gtk2-2.4.8_1 to webkit-gtk2-2.4.8_2
        Upgrade firefox-37.0.2,1 to firefox-37.0.2_1,1
        Upgrade raptor2-2.0.15 to raptor2-2.0.15_1

=3D=3D=3D>>> Proceed? y/n [y]=20

As indicated, I told it to proceed, which it did -- as far as math/R:

=2E..
=3D=3D=3D>>> Update for math/R failed
=3D=3D=3D>>> Aborting update

=3D=3D=3D>>> The following actions were performed:
        Upgrade of icu-53.1 to icu-55.1
        Upgrade of pkgconf-0.9.9 to pkgconf-0.9.10

=3D=3D=3D>>> You can restart from the point of failure with this command li=
ne:
       portmaster <flags> math/R devel/boost-libs print/harfbuzz textproc/l=
ibvisio01 www/libxul devel/p5-IO-stringy devel/qt4-corelib print/texlive-ba=
se www/webkit-gtk2 www/firefox textproc/raptor2=20


I had previously seen cases where, during an update, math/R will
be attempting before one or more of the ports on which it depends
-- and as far as I know, I have no ports that could possibly depend
on it -- so I just moved math/R to the end of the list & re-tried:

Script started on Fri Apr 24 04:45:21 2015
command: portmaster -d devel/boost-libs print/harfbuzz textproc/libvisio01 =
www/libxul devel/p5-IO-stringy devel/qt4-corelib print/texlive-base www/web=
kit-gtk2 www/firefox textproc/raptor2 math/R
=2E..
Stop.
make: stopped in /common/ports/print/harfbuzz

=3D=3D=3D>>> make build failed for print/harfbuzz
=3D=3D=3D>>> Aborting update

=3D=3D=3D>>> Update for print/harfbuzz failed
=3D=3D=3D>>> Aborting update
=2E...


Cutting out a fair bit of trial and erro, it turns out that
devel/glib20 needed to be (re-)built in order for print/harfbuzz
to build successfully.


To test this, when it came time to update my installed amd64 ports:

root@g1-254:/common/home/david # portmaster -adn^M
=2E..
0;portmaster: All >> (13)^G
=3D=3D=3D>>> The following actions will be taken if you choose to proceed:
        Upgrade icu-53.1 to icu-55.1
        Upgrade pkgconf-0.9.9 to pkgconf-0.9.10
        Upgrade R-3.0.2_3 to R-3.0.2_4
        Upgrade boost-libs-1.55.0_4 to boost-libs-1.55.0_5
        Upgrade harfbuzz-0.9.40 to harfbuzz-0.9.40_1
        Upgrade libvisio01-0.1.1 to libvisio01-0.1.1_1
        Upgrade libxul-31.6.0 to libxul-31.6.0_1
        Upgrade p5-IO-stringy-2.110_1 to p5-IO-stringy-2.111
        Upgrade qt4-corelib-4.8.6_4 to qt4-corelib-4.8.6_5
        Upgrade texlive-base-20140525_6 to texlive-base-20140525_7
        Upgrade webkit-gtk2-2.4.8_1 to webkit-gtk2-2.4.8_2
        Upgrade firefox-37.0.2,1 to firefox-37.0.2_1,1
        Upgrade raptor2-2.0.15 to raptor2-2.0.15_1

=3D=3D=3D>>> Proceed? y/n [y] n

I then proceeded to hand-craft the portmaster invocation, thus:

root@g1-254:/common/home/david # portmaster -d icu-53.1 pkgconf-0.9.9 devel=
/glib
20 boost-libs-1.55.0_4 harfbuzz-0.9.40 libvisio01-0.1.1 libxul-31.6.0 p5-IO=
-stringy-2.110_1 qt4-corelib-4.8.6_4 texlive-base-20140525_6 webkit-gtk2-2.=
4.8_1 firefox-37.0.2,1 raptor2-2.0.15 R-3.0.2_3^M

=3D=3D=3D>>> Working on:
        icu-53.1
        pkgconf-0.9.9
        devel/glib20
        boost-libs-1.55.0_4
        harfbuzz-0.9.40
        libvisio01-0.1.1
        libxul-31.6.0
        p5-IO-stringy-2.110_1
        qt4-corelib-4.8.6_4
        texlive-base-20140525_6
        webkit-gtk2-2.4.8_1
        firefox-37.0.2,1
        raptor2-2.0.15
        R-3.0.2_3

=3D=3D=3D>>> Gathering distinfo list for installed ports

=3D=3D=3D>>> icu-53.1 1/14
=2E...


This time, the update proceeded without interruption or perceived
problem.

I'm not precisely sure where the problem(s) might be that caused
what I observed, so I don't have the information I'd need to file
a PR.  But I believe the above provides a fair bit of evidence that
whatever is wrong should be fixable, as long as the dependency-tracking
is correct and proper actions are taken based on it.

Peace,
david
--=20
David H. Wolfskill				david@catwhisker.org
Those who murder in the name of God or prophet are blasphemous cowards.

See http://www.catwhisker.org/~david/publickey.gpg for my public key.

--NZtAI5QFBF0GmLcW
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQJ8BAEBCgBmBQJVOlGBXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ4RThEMDY4QTIxMjc1MDZFRDIzODYzRTc4
QTY3RjlDOERFRjQxOTNCAAoJEIpn+cje9Bk7gQYP/jKVLQez+7liFuz6FLuuYxxh
0E6GM/AF0uqi8sBVOe8ep3fJ0X9WOY4pKKFQiVjl1caHYJdb2b9kxPFU1PwqfKVq
vNYIGO65AkM0FFdEDx4C9E+H4vFy77clMQ2NnHwmJ+ZAbcxIGt6u2QLoLDWYcth1
1MvV39lvmnezpGGi69zsr5iRrJYcqV5M7HvnDivw1sQkDaPAhyfxQTF3Smx0wn+b
bI+QoNGJLDt4ks3vzhzWVhJJ8tRiupUy0HbQVL4b6BFWvxm8O/UXwubTJmRpQkcY
sYsFj5NdpG35DgeM8GEjcbZcyazPOVVL+yT2nUWFEJne1rZbc/xzIkDkH1Bg1EZE
6CQ05ju1Zy2qUWxbHrlyX7Al6t0fEDEoqkfR/G58OQm5AUz7eHgRSQJW0uUjx3D+
+JSillzPa6QhrW6bN25o1iTORFC7MNhOArbfkqPaI0rqcsvtAzhYGvcfraByFesM
o1rXx+D+g8FLa5Njry8LaK8OOC1+bIGl5wDkDu9UkcHfy0L8s576NVS7++5gzzuI
3VN/zMzdErQTqg7fIOk5xv3dHqbBKiIwowykPx9Pb8VSp6QiaNO8Kr93Tgy9odHT
4MrPCaCkMgzugDYfOFSTNObYTDWC300LWFkBvdSPCCgNA8BcbDns2TVxnzLtYBpE
CDu+reMewgMFTqrPPL0h
=hm/k
-----END PGP SIGNATURE-----

--NZtAI5QFBF0GmLcW--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150424142153.GM37361>