On Thu, 2017-10-26 at 13:27 +0300, Mykola Krachkovsky wrote:
середа, 25 жовтня 2017 р. 15:15:34 EEST Dominique Leuenberger написано:
libqt5-qtbase (5.9.1 -> 5.9.2) libqt5-qtconnectivity (5.9.1 -> 5.9.2) libqt5-qtdeclarative (5.9.1 -> 5.9.2) libqt5-qtgraphicaleffects (5.9.1 -> 5.9.2) libqt5-qtimageformats (5.9.1 -> 5.9.2) libqt5-qtlocation (5.9.1 -> 5.9.2) libqt5-qtmultimedia (5.9.1 -> 5.9.2) libqt5-qtquickcontrols (5.9.1 -> 5.9.2) libqt5-qtquickcontrols2 (5.9.1 -> 5.9.2) libqt5-qtscript (5.9.1 -> 5.9.2) libqt5-qtsensors (5.9.1 -> 5.9.2) libqt5-qtserialport (5.9.1 -> 5.9.2) libqt5-qtsvg (5.9.1 -> 5.9.2) libqt5-qttools (5.9.1 -> 5.9.2) libqt5-qtwebchannel (5.9.1 -> 5.9.2) libqt5-qtwebengine (5.9.1 -> 5.9.2) libqt5-qtwebsockets (5.9.1 -> 5.9.2) libqt5-qtx11extras (5.9.1 -> 5.9.2) libqt5-qtxmlpatterns (5.9.1 -> 5.9.2)
This release and some earlier when main Qt5 modules libraries are updated but some are not: libQt53D*/libqt5-qt3d*, libQt5DataVisualization/libqt5- qtdatavis3d, libqt5-virtualkeyboard, libQt5SerialBus/libqt5- qtserialbus are still 5.9.1 in main repository and conflicts with update of main libraries to 5.9.2.
Why this happens?
some are 'ring packages' (essential to the system) and guaranteed to not break. Those are usually updated in a first step. The 2nd batch can't pass its build and install tests, as they build against 'what is currently in openSUSE:Factory' - which means they are unresolvable before the first batch has been checked in. The result is this two-phase update for Qt libs (Max is working on a possible solution to 'link' non-ring stagings to ring package updates, but there is no promise yet as to when / if this ever works as intended) cheers Dominique