Yes, I ran “port selfupdate” and “port upgrade” again and the last ports after
qt5 (including py27-pyqt5 @5.8.2_0 ) are now upgraded successfully, so the port
system fixed whatever was wrong before. The scan for broken ports helps a lot
for those of us who are not so careful with our maintenance.
-----Original Message-----
From: Ryan Schmidt <ryandes...@macports.org>
Date: Tuesday, April 18, 2017 at 7:20 AM
Well it looks good now. 5.7.1 is the latest, and it's what you have active,
so hopefully things are fine now?
> On Apr 18, 2017, at 09:19, Fielding, Eric J (329A)
<eric.j.field...@jpl.nasa.gov> wrote:
>
> Thanks for the help.
>
> I did run “port selfupdate” before doing the “port upgrade”, but I think
the last time I did the “port upgrade” it did not complete due to some error
that I forgot. I didn’t have time to figure out what was wrong at that time,
which was likely my mistake. Probably the ports were in some kind of
inconsistent state.
>
> Anyway, here is the present state for qt5:
>> port installed name:qt5
> The following ports are currently installed:
> py27-pyqt5 @5.7.1_0
> py27-pyqt5 @5.8.1_0 (active)
> qt5 @5.6.2_0
> qt5 @5.7.1_0 (active)
> qt5-qt3d @5.6.2_0
> qt5-qt3d @5.7.1_0 (active)
> qt5-qtbase @5.6.2_0
> qt5-qtbase @5.7.1_0+openssl
> qt5-qtbase @5.7.1_1+openssl (active)
> qt5-qtcanvas3d @5.6.2_0
> qt5-qtcanvas3d @5.7.1_0 (active)
> qt5-qtconnectivity @5.6.2_0
> qt5-qtconnectivity @5.7.1_0 (active)
> qt5-qtdeclarative @5.6.2_0
> qt5-qtdeclarative @5.7.1_0 (active)
> qt5-qtgraphicaleffects @5.6.2_0
> qt5-qtgraphicaleffects @5.7.1_0 (active)
> qt5-qtimageformats @5.6.2_1
> qt5-qtimageformats @5.7.1_0 (active)
> qt5-qtlocation @5.6.2_0
> qt5-qtlocation @5.7.1_0 (active)
> qt5-qtmacextras @5.6.2_0
> qt5-qtmacextras @5.7.1_0 (active)
> qt5-qtmultimedia @5.6.2_0
> qt5-qtmultimedia @5.7.1_0 (active)
> qt5-qtquickcontrols @5.6.2_0
> qt5-qtquickcontrols @5.7.1_0 (active)
> qt5-qtscript @5.6.2_0
> qt5-qtscript @5.7.1_0 (active)
> qt5-qtsensors @5.6.2_0
> qt5-qtsensors @5.7.1_0 (active)
> qt5-qtserialport @5.6.2_0
> qt5-qtserialport @5.7.1_0 (active)
> qt5-qtsvg @5.6.2_0
> qt5-qtsvg @5.7.1_0 (active)
> qt5-qttools @5.6.2_1
> qt5-qttools @5.7.1_0 (active)
> qt5-qttranslations @5.6.2_0
> qt5-qttranslations @5.7.1_0 (active)
> qt5-qtwebchannel @5.6.2_0
> qt5-qtwebchannel @5.7.1_0 (active)
> qt5-qtwebsockets @5.6.2_0
> qt5-qtwebsockets @5.7.1_0 (active)
> qt5-qtxmlpatterns @5.6.2_0
> qt5-qtxmlpatterns @5.7.1_0 (active)
> qt5-sqlite-plugin @5.6.2_0
> qt5-sqlite-plugin @5.7.1_0 (active)
>
> ++Eric
>
> -----Original Message-----
> From: Ryan Schmidt <ryandes...@macports.org>
> Date: Tuesday, April 18, 2017 at 4:34 AM
>
>> On Apr 17, 2017, at 20:27, Fielding, Eric J (329A)
<eric.j.field...@jpl.nasa.gov> wrote:
>>
>> I might have missed something in the last few months, but I didn’t find
a mention of this.
> …
>> Is this the correct procedure? Seems to be working (although taking a
while to compile webkit2-gtk).
>
> qt5-qtenginio is obsolete and should be uninstalled.
>
> Your old version of qt5 still depended on it. If you had first
upgraded qt5 to the latest version, 5.7.1, it would no longer have depended on
it and you could have uninstalled it without issue.
>
> Your transcript shows that when you told MacPorts to install qt5, it
did nothing, which means qt5 was already installed at the latest version. Are
you sure your ports are up to date? Have you run `sudo port selfupdate` lately?
Do you have any local portfiles that override any of the official portfiles?
What is the output of `port installed name:qt5`?
>
> webkit2-gtk does take hours to build; that's normal enough.
>
> You shouldn't have had to recompile anything, because nothing should
have been broken. Some ports may be broken because you have an older version of
qt5, and that problem would go away if you properly upgrade qt5.
>
>
>
>
