Neon/QtUpdates

How to Update Qt in Neon

Testing phase

Testing phase is initial preparation stage of Qt updates, where new Qt version is prepared in the experimental repo, reasoning behind preparing it in experimental is sometime Qt updates can take days to prepare, preparing it in separate repo doesn't affect the production.

• For these Qt packages merge in order Neon/release into Neon/testing (USE nci/qt_merge_and_bumper.rb; IF IT DOENS'T WORK FIX IT)
• For these the Qt packages merge in order latest tagged release from master into Neon/testing
• If debian hasn't prepared the tag for the specific release, you would need to
• List of packages for qtdoc rebuilds
  • Drop the changelog delta with debian
  • Bump the Build-Depends and Build-Depends-Indep of the qt dependencies in debian/control to the Qt version being prepared
  • Add the changelog entry with the packaging version set to -0neon or +dfsg-0+neon, (i.e 5.12.1+dfsg-0+neon) it is used to avoid the merge conflicts with the debian merge.
  • git push all changes at once.
• Let them build, and fix the remaining errors. Once the qtdoc related packages are rebuilt, you need to build them again in same order to make sure they are green.
• After that follow procedure in previous step for rest of Qt packages
• Once all Qt packages are done, build the other kde related packages in experimental view.

If builds are completed, you can test them on user edition by enabling /release and /experimental repositories, and upgrading your system. You would also have to pin the packages in experimental repo.

   Package: *
   Pin: release l=KDE neon - Experimental Edition
   Pin-Priority: 1001

If everything looks good, you can proceed to landing them in Neon/release

Landing Qt

Landing Qt is also two step process,

Building Qt in release/unstable/stable

Generally speaking since this procedure freezes the unstable/stable and user editions for normal user, and important fixes and/or new developments can not be delivered to them in timely manner, it is recommended to do this process generally on Thu-Fri, and snapshot/un-divert next week on Monday/Tuesday.

• Run both stable and unstable divert mgmt jobs to make developer builds go to /tmp/dev/unstable instead of /dev/unstable. Do this for both current and future releases if moving to a new LTS.
• Change "repo_diversion" to true in nci.yaml and deploy with mgmt_tooling on both build.neon and xenon
• Notify other neon developers to NOT snapshot either Neon/release or Neon/release-lts.
• List of packages for qtdoc rebuilds
• For these packages:
  • Merge the Neon/testing branch to Neon/release.
  • Wait for builds to finish
  • Rebuild same packages again.

'jammy_[^_]+_[^_]+_(qtbase|qtdeclarative|qtlocation|qtsensors|qtwebsockets|qtwebchannel|qt5webkit|qttools)$'

• Merge Neon/testing branch into Neon/release for other Qt packages, and wait for them to finish building.
• Build stuff which deps on Qt-private-ABI in all editions.

'jammy_[^_]+_[^_]+_(elisa|gammaray|kmymoney|peruse|qml-box2d|skrooge|subtitlecomposer|verdigris|fcitx-qt5|qtkeychain|akonadi|frameworkintegration|kdeconnect|kguiaddons|ki18n|kiconthemes|kirigami|kitinerary|krfb|ktp-common-internals|kwayland|kwayland-integration|kwin|kxmlgui|layer-shell-qt|akonadi|kio-extras|pyqt5|python-qt4|sip4|kdeclarative|kwayland|kwayland-integration|plasma-framework|breeze|kwin|plasma-integration|skrooge|qqc2-desktop-style|gammaray|sddm)$'

• Create a new kf5-qt content Snap and build it

Making it available to users

Never land Qt after Wednesday unless it is absolutely required for some bug fixes or something. Landing Qt after Wednesday doesn't leave enough time for bug-fixes or stuff before weekend.

• Test both user edition with /release repo enabled, and dev unstable edition at least with archive link changed to /tmp/unstable instead of /unstable.
• Once at least 2 days of testing is done, snapshot user and user-lts
• Change "repo_diversion" to false in nci.yaml
• Make sure mgmt_tooling deployed on both neon and xenon
• Undivert the dev unstable and dev stable repos with the mgmt jobs

Process improvements

• Document release/lts wrt Qt.
• FIXME openQA checks?
• Build arm for experimental editions?