/srv/irclogs.ubuntu.com/2024/10/18/#kubuntu-devel.txt

IrcsomeBot<RikMills> So far on Qt6 transition I did:09:46
IrcsomeBot<RikMills> * Started preparing in a ci-train PPA. Why? These PPAs originally used with ci/biletto builds are configured to build as the main archive does so are ok to binary copy from straight to the proposed pocket. They also have a much higher basic build score than normal PPAs. Con is that you need to be in the Ubuntu landing PPA team to upload to them.09:46
IrcsomeBot<RikMills> *  Built Qt 6.7.2 for oracular when plucky was not a thing yet,started building Qt 6.7.2 by bootstrapping the docs. i.e. building up to qt6-tools with docs disabled, then rebuilding again with docs enabled. Reason being that qt6-tools is needed to build the docs. Note that all builds done with a ~ubuntu24.10~ppax suffix so that we won't supersede real uploads/syncs.09:46
IrcsomeBot<RikMills> *  Built the rest of Qt 6.7.209:46
IrcsomeBot<RikMills> *  Rebuilds of other packages in the transition as dictated by the tracker and some manual checking. Fixing build issues against new Qt or toolchain (patches/config etc)09:46
IrcsomeBot<RikMills> * Once done, tested upgrades in oracular in a VM.09:46
IrcsomeBot<RikMills> * When plucky PPA builds became possible, used kopypackage2 to copy oracular builds to plucky. That means don't have to bootstrap or rebuild the stack from scratch.09:46
IrcsomeBot<RikMills> * Rebuilt Qt 6.7.2 for plucky in the PPA, then rebuild the other packages. This time using ./copy-package from ubuntu-archive-tools to copy the real Qt 6.7.2 from sid/unstable. Other uploads versioned also without a PPA suffix so, when all built can be copied to plucky proposed with ./copy-package09:46
IrcsomeBot<RikMills> @sgmoore ^^09:46
IrcsomeBot<RikMills> So far on Qt6 transition I did:09:48
IrcsomeBot<RikMills> * Started preparing in a ci-train PPA. Why? These PPAs originally used with ci/biletto builds are configured to build as the main archive does so are ok to binary copy from them straight to the proposed pocket. They also have a much higher basic build score than normal PPAs. Con is that you need to be in the Ubuntu landing PPA team to upload to them.09:48
IrcsomeBot<RikMills> *  Built Qt 6.7.2 for oracular when plucky was not a thing yet,started building Qt 6.7.2 by bootstrapping the docs. i.e. building up to qt6-tools with docs disabled, then rebuilding again with docs enabled. Reason being that qt6-tools is needed to build the docs. Note that all builds done with a ~ubuntu24.10~ppax suffix so that we won't supersede real uploads/syncs.09:48
IrcsomeBot<RikMills> *  Built the rest of Qt 6.7.209:48
IrcsomeBot<RikMills> *  Rebuilds of other packages in the transition as dictated by the tracker and some manual checking. Fixing build issues against new Qt or toolchain (patches/config etc)09:48
IrcsomeBot<RikMills> * Once done, tested upgrades in oracular in a VM.09:48
IrcsomeBot<RikMills> * When plucky PPA builds became possible, used kopypackage2 to copy oracular builds to plucky. That means don't have to bootstrap or rebuild the stack from scratch.09:48
IrcsomeBot<RikMills> * Rebuilt Qt 6.7.2 for plucky in the PPA, then rebuild the other packages. This time using ./copy-package from ubuntu-archive-tools to copy the real Qt 6.7.2 from sid/unstable. Other uploads versioned also without a PPA suffix, so when all built can be copied to plucky proposed with ./copy-package09:48
IrcsomeBot<RikMills> One package will need core-dev to copy09:48
IrcsomeBot<RikMills> Ubuntu archive tools: https://code.launchpad.net/~ubuntu-archive/ubuntu-archive-tools/+git/ubuntu-archive-tools09:51
IrcsomeBot<RikMills> Transition tracker configs: https://code.launchpad.net/~ubuntu-transition-trackers/ubuntu-transition-tracker/configs09:51
IrcsomeBot<RikMills> Left to do:09:53
IrcsomeBot<RikMills> * copy to plucky-proposed when that is possible09:53
IrcsomeBot<RikMills> * firefight any autopkgtest fails/issues09:53
IrcsomeBot<RikMills> * If required, formulate britney hint for the transition if britney cannot figure how to migrate it all itself09:53
mamarleyRikMills: You've been busy. :)  Thanks for all of your work.11:07
IrcsomeBot<sgmoore> @RikMills Thank you!11:23
IrcsomeBot<RikMills> yw11:25
BluesKajHi all12:00
IrcsomeBot<myfenris> Tq too entertaining my issues and building all the 6.x packages 📦12:52
IrcsomeBot<RikMills> np. I have frameworks and plasma 6.2 also ready for when the Qt 6.7.2 transition in done13:57
IrcsomeBot<sgmoore> wow, thats awesome!13:58
IrcsomeBot<RikMills> np. I have frameworks 6.7.0 and plasma 6.2 also ready for when the Qt 6.7.2 transition in done13:58
IrcsomeBot<RikMills> I told you I wanted to get off to a good start ;)13:58
IrcsomeBot<RikMills> plus I have the spare time right now. that may not be the case in a few weeks time13:59
IrcsomeBot<sgmoore> You weren't kidding!13:59
IrcsomeBot<sgmoore> I hear yah. Thank you!!13:59
RikMillstsimonq2: libksane now accepted in experimental14:16
RikMillsthough I guess not not crucial14:17
tsimonq2RikMills: Awesome!14:17

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!