[00:03] yes i noticed that guiverc [00:04] i mentioned to @hmollercl how to make it be nm-connection-editor by default. hopefully that will happen soon (let me know if you need me to do it hans) [00:10] alternately, we can't specialize a default size for qterminal unless we pull this in https://github.com/lxqt/qterminal/commit/c8c06489ec87431b33112e5ee46f8d54410c7cc3 [00:11] even still i'm not sure that would solve the problem in all cases [05:37] @RikMills [], I am still not understanding, which two versions did you use to create this debdiff? [06:40] -lugito:#lubuntu-devel- [rMANUAL338a75079e6e: Fix styling] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL338a75079e6e [06:44] -lugito:#lubuntu-devel- [rMANUAL01c4aced619c: Add Image quality slider] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL01c4aced619c [06:49] -lugito:#lubuntu-devel- [rMANUAL419f56e73d15: Add note that template does not always show] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL419f56e73d15 [06:52] -lugito:#lubuntu-devel- [rMANUAL0b861a32a040: Add Save first screenshot showing in autosave note] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL0b861a32a040 [06:55] -lugito:#lubuntu-devel- [rMANUAL5b71355bca96: Make text match] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL5b71355bca96 [08:11] @The_LoudSpeaker [I am still not understanding, which two versions did you use to create this debd …], It is the diff between 0.14.1-1 and 0.14.1-1ubuntu1 [08:20] The one I did was between 0.14.1-0ubuntu1 and 0.14.1-1ubuntu1 [08:21] When 0.14.1-0ubuntu1 was created, at that time the debdiff you made must have been done na? [08:26] I think I have said this more than once already, but to be very clear. [08:28] In a debian merge, the debian/changelog merge entry MUST document the difference between the DEBIAN version and the RESULT OF YOUR MERGE [08:28] NOT the difference between the last Ubuntu version and the new Ubuntu version [16:35] so debian/compat is no longer used? [16:35] isntead Build-Depends: debhelper-compat (= 12) [16:58] @HMollerCl [so debian/compat is no longer used?], as @tsimonq2 posted https://lists.debian.org/debian-devel-announce/2020/02/msg00000.html [16:58] * The "debhelper-compat (= 12)" build-dependency to replace … "Build-Depends: debhelper (>= 12~)" and "echo 12 > debian/compat". [17:05] That means that all packages should be upgraded? Or only the ones that will be "touched" anyway? [17:06] I would say only those that get touched, or have an issue with 11 [17:07] @tsimonq2 ^ [17:08] though my opinion is coloured by having to curate kde stuff, which is over 300 packages... 😆 [17:45] @RikMills [though my opinion is coloured by having to curate kde stuff, which is over 300 p …], Yeah, in our case go ahead and refresh them all [17:45] Do a thorough look at all of them [17:46] Standards version, debhelper compat, evil and pedantic Lintian, the works [17:46] And we removed the 2222 from VCS [17:46] So go ahead and remove that [17:51] Is there a special version for Raspberry Pi … If not, can I test Lubuntu on it … Has anyone done it( @The_LoudSpeaker) [17:59] @tsimonq2 [Do a thorough look at all of them], I would love to be able to do that in Kubuntu, but ENOTIME! [18:40] @tsimonq2 @HMollerCl @RikMills Is debian/compat even needed? [18:45] @Rutvikm [Is there a special version for Raspberry Pi? … If not, can I test Lubuntu on it? …], There isn't as of now. You can install lubuntu-desktop and sddm on ubuntu-server on Pi [19:16] @ItzSwirlz [@tsimonq2 @HMollerCl @RikMills Is debian/compat even needed?], Not anymore [21:46] @apt-ghetto do you know enough about thsi subject that you could put together a solution as a shellprocess? https://github.com/calamares/calamares/issues/1203 [21:46] Issue 1203 in calamares/calamares "Encryption does not work well with non-QWERTY keyboards" [Open] [22:08] @kc2bez @tsimonq2 @hmollercl @The_LoudSpeaker what do you think about creating a shellprocess to alert the user that they have mounts that could prevent erase disk as an option and optionally allow them to unmount/swapoff? re: https://github.com/calamares/calamares/issues/860 [22:08] Issue 860 in calamares/calamares "re-think handling of (auto-)mounted partitions" [Open] [22:11] I have been pondering this for a bit. [22:11] I hadn't thought of an interactive approach until you mentioned it. [22:12] I was more or less just thinking of swap too. [22:12] My thought process was a little narrow. [22:15] there's a couple ways we could do it [22:15] we could do qt, pyqt, or my favorite kdialog [22:16] i would REALLY be inclined towards the latter because it adds one really small depend but it's super practical and crazy easy to use in shell scripts [22:16] we use it at work quite a bit [22:44] @wxl [ @apt-ghetto do you know enough about thsi subject that you could put toget …], I guess you mean creating a core.img with a shellprocess? No, I don't know enough about it. But I don't think, that this is a good solution. It should be handled by Calamares. … If a newer Grub is installed, the core.img is replaced. And how c [22:44] an we sign the custom Grub core.img without a valid private key of Canonical for Secure Boot?