Qt 5.9 is released , it's in Qt Overlay, but there appears to be no bug tracking the progress of it being merged into Gentoo.
There's substantial packaging work that still needs doing due to an upstream change of how the build system is handled. Unfortunately, nobody has had the time to take care of it yet.
I've completed a brief review of all 5.9 ebuild except for qtbase/webkit/webengine.
I have found a bug with current stable version of qt in portage (5.7.1). It is reproducible since 5.7.0 and fixed only in 5.9.0.
And looks like https://bugs.kde.org/show_bug.cgi?id=373628 is caused by qt bug.
It causes systemsettings5 crash. For example, when I try to switch to Display settings.
Please either mask 5.7.1 version of qt or bump 5.9.1 (or both).
(In reply to Pavel Kozlov from comment #3)
> Hi guys!
> I have found a bug with current stable version of qt in portage (5.7.1). It
> is reproducible since 5.7.0 and fixed only in 5.9.0.
> And looks like https://bugs.kde.org/show_bug.cgi?id=373628 is caused by qt
> It causes systemsettings5 crash. For example, when I try to switch to
> Display settings.
> Please either mask 5.7.1 version of qt or bump 5.9.1 (or both).
Qt 5.9 will be bumped in the tree as soon as the ebuilds are in a decent state. We certainly can't mask 5.7.1 being the latest stable version.
With the major blockers resolved, unless something else comes up I'd like to target 5.9.2 in the main tree in ~arch once it's released.
I've bumped 5.9.2 unmasked in the Qt overlay. I'll move it to the main tree as soon as there's no reports that it immediately explodes.
The bug has been referenced in the following commit(s):
Author: Michael Palimaka <firstname.lastname@example.org>
AuthorDate: 2017-10-08 01:37:36 +0000
Commit: Michael Palimaka <email@example.com>
CommitDate: 2017-10-08 01:46:26 +0000
dev-qt: version bump 5.9.2
Package-Manager: Portage-2.3.8, Repoman-2.3.3
dev-qt/assistant/Manifest | 1 +
dev-qt/assistant/assistant-5.9.2.ebuild | 37 +++++
dev-qt/designer/Manifest | 1 +
dev-qt/designer/designer-5.9.2.ebuild | 40 +++++
dev-qt/linguist-tools/Manifest | 1 +
dev-qt/linguist-tools/linguist-tools-5.9.2.ebuild | 35 +++++
dev-qt/linguist/Manifest | 1 +
dev-qt/linguist/linguist-5.9.2.ebuild | 28 ++++
dev-qt/pixeltool/Manifest | 1 +
dev-qt/pixeltool/pixeltool-5.9.2.ebuild | 25 ++++
dev-qt/qdbus/Manifest | 1 +
dev-qt/qdbus/qdbus-5.9.2.ebuild | 25 ++++
dev-qt/qdbusviewer/Manifest | 1 +
dev-qt/qdbusviewer/qdbusviewer-5.9.2.ebuild | 27 ++++
dev-qt/qdoc/Manifest | 1 +
dev-qt/qdoc/metadata.xml | 3 +
dev-qt/qdoc/qdoc-5.9.2.ebuild | 31 ++++
dev-qt/qt-docs/Manifest | 1 +
dev-qt/qt-docs/qt-docs-5.9.2_p201710050733.ebuild | 40 +++++
dev-qt/qt3d/Manifest | 1 +
dev-qt/qt3d/qt3d-5.9.2.ebuild | 32 ++++
dev-qt/qtbluetooth/Manifest | 1 +
dev-qt/qtbluetooth/qtbluetooth-5.9.2.ebuild | 33 +++++
dev-qt/qtcharts/Manifest | 1 +
dev-qt/qtcharts/qtcharts-5.9.2.ebuild | 29 ++++
dev-qt/qtconcurrent/Manifest | 1 +
dev-qt/qtconcurrent/qtconcurrent-5.9.2.ebuild | 23 +++
dev-qt/qtcore/Manifest | 1 +
dev-qt/qtcore/qtcore-5.9.2.ebuild | 66 +++++++++
dev-qt/qtdatavis3d/Manifest | 1 +
dev-qt/qtdatavis3d/qtdatavis3d-5.9.2.ebuild | 31 ++++
dev-qt/qtdbus/Manifest | 1 +
dev-qt/qtdbus/qtdbus-5.9.2.ebuild | 38 +++++
dev-qt/qtdeclarative/Manifest | 1 +
dev-qt/qtdeclarative/qtdeclarative-5.9.2.ebuild | 56 +++++++
dev-qt/qtdiag/Manifest | 1 +
dev-qt/qtdiag/metadata.xml | 4 +
dev-qt/qtdiag/qtdiag-5.9.2.ebuild | 36 +++++
dev-qt/qtgraphicaleffects/Manifest | 1 +
.../qtgraphicaleffects-5.9.2.ebuild | 21 +++
dev-qt/qtgui/Manifest | 1 +
dev-qt/qtgui/qtgui-5.9.2.ebuild | 164 +++++++++++++++++++++
dev-qt/qthelp/Manifest | 1 +
dev-qt/qthelp/qthelp-5.9.2.ebuild | 30 ++++
dev-qt/qtimageformats/Manifest | 1 +
dev-qt/qtimageformats/qtimageformats-5.9.2.ebuild | 23 +++
dev-qt/qtlocation/Manifest | 1 +
dev-qt/qtlocation/qtlocation-5.9.2.ebuild | 36 +++++
dev-qt/qtmultimedia/Manifest | 1 +
dev-qt/qtmultimedia/qtmultimedia-5.9.2.ebuild | 65 ++++++++
dev-qt/qtnetwork/Manifest | 1 +
dev-qt/qtnetwork/qtnetwork-5.9.2.ebuild | 53 +++++++
dev-qt/qtnetworkauth/Manifest | 1 +
dev-qt/qtnetworkauth/metadata.xml | 17 +++
dev-qt/qtnetworkauth/qtnetworkauth-5.9.2.ebuild | 20 +++
dev-qt/qtopengl/Manifest | 1 +
dev-qt/qtopengl/qtopengl-5.9.2.ebuild | 34 +++++
dev-qt/qtpaths/Manifest | 1 +
dev-qt/qtpaths/qtpaths-5.9.2.ebuild | 23 +++
dev-qt/qtplugininfo/Manifest | 1 +
dev-qt/qtplugininfo/qtplugininfo-5.9.2.ebuild | 23 +++
dev-qt/qtpositioning/Manifest | 1 +
dev-qt/qtpositioning/qtpositioning-5.9.2.ebuild | 37 +++++
dev-qt/qtprintsupport/Manifest | 1 +
dev-qt/qtprintsupport/qtprintsupport-5.9.2.ebuild | 42 ++++++
dev-qt/qtquickcontrols/Manifest | 1 +
.../qtquickcontrols/qtquickcontrols-5.9.2.ebuild | 32 ++++
dev-qt/qtquickcontrols2/Manifest | 1 +
dev-qt/qtquickcontrols2/metadata.xml | 3 +
.../qtquickcontrols2/qtquickcontrols2-5.9.2.ebuild | 30 ++++
dev-qt/qtscript/Manifest | 1 +
dev-qt/qtscript/qtscript-5.9.2.ebuild | 36 +++++
dev-qt/qtscxml/Manifest | 1 +
dev-qt/qtscxml/qtscxml-5.9.2.ebuild | 19 +++
dev-qt/qtsensors/Manifest | 1 +
dev-qt/qtsensors/qtsensors-5.9.2.ebuild | 28 ++++
dev-qt/qtserialbus/Manifest | 1 +
dev-qt/qtserialbus/metadata.xml | 17 +++
dev-qt/qtserialbus/qtserialbus-5.9.2.ebuild | 20 +++
dev-qt/qtserialport/Manifest | 1 +
dev-qt/qtserialport/qtserialport-5.9.2.ebuild | 27 ++++
dev-qt/qtspeech/Manifest | 1 +
dev-qt/qtspeech/metadata.xml | 17 +++
dev-qt/qtspeech/qtspeech-5.9.2.ebuild | 20 +++
dev-qt/qtsql/Manifest | 1 +
dev-qt/qtsql/qtsql-5.9.2.ebuild | 53 +++++++
dev-qt/qtsvg/Manifest | 1 +
dev-qt/qtsvg/qtsvg-5.9.2.ebuild | 23 +++
dev-qt/qttest/Manifest | 1 +
dev-qt/qttest/qttest-5.9.2.ebuild | 29 ++++
dev-qt/qttranslations/Manifest | 1 +
dev-qt/qttranslations/qttranslations-5.9.2.ebuild | 19 +++
dev-qt/qtvirtualkeyboard/Manifest | 1 +
.../qtvirtualkeyboard-5.9.2.ebuild | 38 +++++
dev-qt/qtwayland/Manifest | 1 +
dev-qt/qtwayland/metadata.xml | 1 +
dev-qt/qtwayland/qtwayland-5.9.2.ebuild | 39 +++++
dev-qt/qtwebchannel/Manifest | 1 +
dev-qt/qtwebchannel/qtwebchannel-5.9.2.ebuild | 26 ++++
dev-qt/qtwebengine/Manifest | 1 +
.../qtwebengine-5.9.0-paxmark-mksnapshot.patch | 46 ++++++
dev-qt/qtwebengine/qtwebengine-5.9.2.ebuild | 114 ++++++++++++++
dev-qt/qtwebkit/Manifest | 1 +
.../files/qtwebkit-5.8.0-disable-gstreamer.patch | 15 ++
dev-qt/qtwebkit/metadata.xml | 1 +
dev-qt/qtwebkit/qtwebkit-5.9.1.ebuild | 120 +++++++++++++++
dev-qt/qtwebsockets/Manifest | 1 +
dev-qt/qtwebsockets/qtwebsockets-5.9.2.ebuild | 27 ++++
dev-qt/qtwebview/Manifest | 1 +
dev-qt/qtwebview/qtwebview-5.9.2.ebuild | 21 +++
dev-qt/qtwidgets/Manifest | 1 +
dev-qt/qtwidgets/qtwidgets-5.9.2.ebuild | 49 ++++++
dev-qt/qtx11extras/Manifest | 1 +
dev-qt/qtx11extras/qtx11extras-5.9.2.ebuild | 21 +++
dev-qt/qtxml/Manifest | 1 +
dev-qt/qtxml/qtxml-5.9.2.ebuild | 25 ++++
dev-qt/qtxmlpatterns/Manifest | 1 +
dev-qt/qtxmlpatterns/qtxmlpatterns-5.9.2.ebuild | 19 +++
118 files changed, 2216 insertions(+)}
Thanks to everyone who was involved in testing, reporting bugs, sending patches, etc. - 5.9.2 has landed!
Thanks! That's quite the milestone; portage was on Qt 5.7 for what seems like forever!
For people who were using 5.9.2 from the Qt overlay, is there a need or benefit to re-emerging, or are the ebuilds identical?
(In reply to Nikos Chantziaras from comment #9)
> Thanks! That's quite the milestone; portage was on Qt 5.7 for what seems
> like forever!
5.8 was rather buggy, at least for kde folks (I run live-git kde-frameworks/plasma/apps and follow some of the commit logs, and saw it). I believe that's why gentoo (and some other distros too) skipped 5.8. 5.9 fixed some of that and the kde devs adapted to some of it, so 5.9 is better, but it still takes time on the gentoo side to test everything, during which both qt and consumer upstreams continue minor-bumping as well, so... 5.7.1 -> 5.9.2 doesn't look so bad knowing that.
> For people who were using 5.9.2 from the Qt overlay, is there a need or
> benefit to re-emerging, or are the ebuilds identical?
According to git log, there were two changes in the qt overlay, both slot adjustments, to designer and assistant, after 5.9.2 initially appeared in the overlay. I didn't check that the merge to gentoo was exactly the reverse of the removal from the overlay, but reasonable QA would suggest that any pre-gentoo-merge changes be done and tested in the overlay first, so you should be good on everything but perhaps those two, depending on when you merged from the overlay, before or after those slot adjustments.
And the slot adjustments could in theory be handled manually, adjusting /var/db/pkg/dev-qt/* instead of remerging, but it's likely simpler to just remerge those two packages if in doubt. If it were qtwebkit or qtwebengine it may be worth doing the manual adjustment since they take so long to build, but at least designer isn't too bad (don't know about assistant; don't have it merged).
I have the following trouble right now:
(dev-qt/qtpositioning-5.9.2:5/5.9::gentoo, ebuild scheduled for merge) pulled in by
~dev-qt/qtpositioning-5.9.2 required by (dev-qt/qtwebengine-5.9.2:5/5.9::gentoo, ebuild scheduled for merge)
(dev-qt/qtpositioning-5.9.1:5/5.9::qt, installed) pulled in by
~dev-qt/qtpositioning-5.9.1 required by (dev-qt/qtwebkit-5.9.1:5/5.9::qt, installed)
A lot of packages (not just qtpositioning, but a lot from qt version 5.9.2) conflict with qtwebkit-5.9.1, they probably require qtwebkit-5.9.2, but there is no such package.
Could you resolve it somehow?
(In reply to Pavel Kozlov from comment #11)
> I have the following trouble right now:
> (dev-qt/qtpositioning-5.9.2:5/5.9::gentoo, ebuild scheduled for merge)
> pulled in by
> ~dev-qt/qtpositioning-5.9.2 required by
> (dev-qt/qtwebengine-5.9.2:5/5.9::gentoo, ebuild scheduled for merge)
> ^ ^^^^^
> (dev-qt/qtpositioning-5.9.1:5/5.9::qt, installed) pulled in by
> ~dev-qt/qtpositioning-5.9.1 required by
> (dev-qt/qtwebkit-5.9.1:5/5.9::qt, installed)
> ^ ^^^^^
> A lot of packages (not just qtpositioning, but a lot from qt version 5.9.2)
> conflict with qtwebkit-5.9.1, they probably require qtwebkit-5.9.2, but
> there is no such package.
> Could you resolve it somehow?
This is caused because your installed qtwebkit is an old revision from qt overlay. Since you emerged it, there was some changes made and it's been moved to the main tree. The fix would be to rebuild it ensuring you're using the ::gentoo version.
Yes, I think the emerge option --newrepo should here help.