On Thu, Nov 5, 2020 at 10:26 PM Sandro Mani manisandro@gmail.com wrote:
On 05.11.20 20:27, Sandro Mani wrote:
On 05.11.20 12:36, Tom Hughes wrote:
On 05/11/2020 11:24, Sandro Mani wrote:
I'll be building proj-7.2.0 together with gdal-3.2.0 in rawhide shortly. I'll do a round of test builds in this copr [1], and then build everything (and rebuild dependent packages) in a rawhide side-tag and then merge it.
That's definitely going to cause some breakage as I believe proj 7 has finally removed the old legacy API which at least some other things like mapnik are still using.
I believe there is an upstream patch for mapnik now but I'll have to see if it can be backported to the release version...
Yes indeed - I'll go through the breakages, see if newer upstream versions fix the problem, and then will post a list of packages which need to be updated and contact the respective maintainers.
Soo, this opened a bit a can of worms, as qt-mobility (clearly being of the qt4 era dead upstream) is not going to support proj7. Only package requiring qt-mobility is qtwebkit, which in turn has a bit more users:
amarok-0:2.9.0-9.fc33.x86_64 arora-0:0.11.0-23.fc33.x86_64 brewtarget-0:2.1.0-16.fc33.x86_64 gambas3-gb-qt4-webkit-0:3.15.2-1.fc34.x86_64 kde-runtime-libs-0:17.08.3-15.fc33.i686 kde-runtime-libs-0:17.08.3-15.fc33.x86_64 kdelibs-6:4.14.38-23.fc34.i686 kdelibs-6:4.14.38-23.fc34.x86_64 kdelibs-webkit-6:4.14.38-23.fc34.i686 kdelibs-webkit-6:4.14.38-23.fc34.x86_64 knode-libs-0:4.14.10-44.fc33.i686 knode-libs-0:4.14.10-44.fc33.x86_64 krecipes-0:2.1.0-12.fc33.x86_64 ksysguard-libs-1:4.11.22-28.fc33.i686 ksysguard-libs-1:4.11.22-28.fc33.x86_64 libkfbapi-0:1.0-16.fc32.i686 libkfbapi-0:1.0-16.fc32.x86_64 python3-PyQt4-webkit-0:4.12.3-13.fc33.x86_64 qlandkartegt-0:1.8.1-28.fc33.x86_64 qmc2-0:0.195-14.fc34.x86_64 qt-assistant-1:4.8.7-57.fc34.x86_64 qt-demos-1:4.8.7-57.fc34.x86_64 qt-designer-plugin-webkit-1:4.8.7-57.fc34.i686 qt-designer-plugin-webkit-1:4.8.7-57.fc34.x86_64 qt-examples-1:4.8.7-57.fc34.i686 qt-examples-1:4.8.7-57.fc34.x86_64 qt4pas-0:2.5-21.fc33.i686 qt4pas-0:2.5-21.fc33.x86_64 qtscriptbindings-0:0.2.0-23.fc33.i686 qtscriptbindings-0:0.2.0-23.fc33.x86_64 qtwebkit-devel-0:2.3.4-32.fc34.i686 qtwebkit-devel-0:2.3.4-32.fc34.x86_64 rekonq-0:2.4.2-17.fc33.x86_64 timetablemate-0:0.10-0.24.20111204git.fc32.x86_64
So among this list, I see as end-user applications:
amarok - dead upstream music player arora, rekonq: dead upstream browers, hardly a good idea to use them brewtarget: has newer 2.3.0 release which supports Qt5 gambas3-gb-qt4-webkit: qt4 subpackages could just be dropped krecipes: dead upstream qlandkartegt: dead upstream qmc2: latest trunk seems to support qt5 timetablemate -> kde-plasma-publictransport: Plasma 5 applet, with last update in 2013 apparently
Sooo, how about taking this as a pretext to just kick out all the qt4 stuff? Debian has completed the move in March this year [1].
Opinions?
I, for one, would welcome getting rid of all that old cruft ... especially if debian already has beaten us to the punch. Could you pour your research into the Change Proposal wiki template and propose this for F34? :)
Fabio