[14:09] * mitya57 retries pivy autopkgtests which are blocking pyside2 migration [14:10] update_output.txt mostly complains about pyside2 now, so maybe we'll get one more step closer to Qt migration if they pass [19:17] seemed to work [19:21] Now it complains about: [19:21] kalgebra, kalgebra-common, kalgebramobile, kde-full, kdeedu, libanalitza-dev, libqgis-3d3.4.13, libqgis-analysis3.4.13, libqgis-app3.4.13, libqgis-core3.4.13, libqgis-customwidgets, libqgis-dev, libqgis-gui3.4.13, libqgis-server3.4.13, libqgisgrass7-3.4.13, libqgispython3.4.13, openorienteering-mapper, pyotherside, pyotherside-tests, [19:21] python3-qgis, python3-qgis-common, qgis, qgis-plugin-grass, qgis-provider-grass, qgis-providers, qgis-server, qml-module-io-thp-pyotherside, qml-module-org-kde-analitza, qml-module-qtav, qtav-players [19:21] Still a lot of stuff :( [19:22] Ok, most of this is qgis but I don't understand what's wrong with it yet. [19:31] qgis depends on proj, so can olnly migrate if that does. sadly multiple things with failing tests in proposed depend on the libproj13 -> libproj15 transition, so that blocks proj even if it says it is a valid candidate. rbase + r-cran packages are linked in to that [19:31] It is a bit of a mess [19:31] yikes [19:32] Hnece I asked this last night: … [04:45] vorlon: might you consider removing the release versions of qgis and openorienteering-mapper for now to move the Qt transition along? 1st only has reverse recommends while the 2nd nothing … [04:46] I think the proj/rbase brokenness might take some time [19:34] Ah, thanks for digging this :) [19:36] I am not sure why britney does not want to group analitza and pyotherside with the 'trying' group yet. I think that is just britney oddness and perhaps hintable if the other things are cleared out of the way. It does not make sense dep-wise to me.