Eight months after the last heads-up, less than a third of then Qt5-based packages remain to be ported or treecleaned in ::gentoo:
https://qa-reports.gentoo.org/output/genrdeps/rindex/dev-qt/qtcore The upstream heads-up and cleanup effort has spawned multiple (sub-)trackers: https://bugs.gentoo.org/show_bug.cgi?id=qt5-removal https://bugs.gentoo.org/show_bug.cgi?id=pyqt5-removal https://bugs.gentoo.org/show_bug.cgi?id=qwt5-removal (almost done) https://bugs.gentoo.org/show_bug.cgi?id=kf5-removal https://bugs.gentoo.org/show_bug.cgi?id=qtscript-removal (pre-existing) https://bugs.gentoo.org/show_bug.cgi?id=qtwebengine5-removal (done) So there is plenty left to do, even if the trackers are still not completely filled. You can no longer count on me doing most of the work. The next step for Qt5 in Gentoo is entry into package.deprecated. - If you maintain a slow moving package that has Qt6 support only in upstream repository, cut a snapshot and put it in ~arch if it builds and runs. Bug them to do a release, but don't hesitate to stabilise a snapshot after the usual time or destabilise the package if it fails to meet criteria. - If you care about a package maintained by someone else, who has not yet reacted to a pending porting bug, don't hesitate to take over and do the necessary work, and push after a courtesy timeout. - If you consider your role as a package maintainer a passive one, to only bump whenever upstream publishes a release, be very aware that your package may be hitting a brick wall when we are hard masking Qt5 for removal at some point. Upstreams are still to this day surprised and thankful to learn that porting from Qt5 to Qt6 is indeed a necessity and maybe not as difficult as expected. Some will be looking at Qt6 porting docs for the first time after your notice. Failure to communicate now means we may lose more packages than necessary in the end, when there is not enough time to wait for porting anymore. Regards
signature.asc
Description: This is a digitally signed message part.
