[14:09]  * mitya57 retries pivy autopkgtests which are blocking pyside2 migration
[14:10] <mitya57> update_output.txt mostly complains about pyside2 now, so maybe we'll get one more step closer to Qt migration if they pass
 seemed to work
 Now it complains about:
 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,
 Still a lot of stuff :(
 Ok, most of this is qgis but I don't understand what's wrong with it yet.
 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
 It is a bit of a mess
[19:31] <blaze> yikes
 Hnece I asked this last night: … [04:45] <RikMills> 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] <RikMills> I think the proj/rbase brokenness might take some time
 Ah, thanks for digging this :)
 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.