[01:07] [matrix] i think i lost the context here. what's the question? [01:13] [matrix] I think we were asking about UX for keyboard layouts [01:13] Squish website, website gets squished [01:15] i'm not sure why i would be the person to decide on that [01:17] * arraybolt3 didn't realize this was w.r.t. a couple days ago, nvm [01:28] [matrix] I think we just trust your sage wisdom and experience. :P [01:28] ^^^^^^ [01:28] that's nice, but i have like zero experience with different keyboard layouts except i know some people use them XD [01:30] wxl: I thought you used DVORAK + foot pedal XD [01:34] * tsimonq2 soft-EODs o/ [07:31] lubuntu's minimal install can't ubuntu-bug complete; inability to xdg-open and open (null; no-browser)... that will at least (maybe) need to be documented (come release) [09:30] [matrix] Can you file a bug with a text based browser? [09:30] * lubot [matrix] doubts LP will like that, but it would be cool if it worked [09:31] [matrix] That's what I was thinking. I figured it would bomb out on the authentication. [09:33] [matrix] Also, https://github.com/calamares/calamares/releases/tag/v3.3.0 [09:33] [matrix] Not alpha ^ [09:33] you used to be able to file bugs using lynx.. not sure I've done it in a few cycles though [09:34] [matrix] You might be able to hack it into working? [09:34] [matrix] Auth with FF, transfer cookie to Lynx, call it a day? [09:35] [matrix] Not exactly a good workaround but if one could keep the cookie on a flash drive or something, might work. [09:36] [matrix] Well I was thinking we could ship lynx in minimal so FF wouldn't be available. [09:39] [matrix] What would be really cool is a reportbug-like interface to LP that was CLI/TUI based, with no browser at all. [09:40] [matrix] Not enough time to try and make one at this point, maybe next cycle. [09:40] [matrix] As long as we don't resort to the Debian method of sending email directly from the box. Most ISPs block that. [09:40] I suspect canonical (legal) will require browser for legal reasons relating to EU privacy (but just suspicion) [09:41] [matrix] I think the biggest thing is the OAUTH token. [09:42] arraybolt3: there used to be python-launchpadlib-toolkit which had the lp-file-bug command [09:42] [matrix] I don't think LP lets you file a bug via email anyway. If it did though, all one would need is an external SMTP server, which Debian conveniently provides. [09:42] [matrix] perfect [09:43] [matrix] Dead since Bionic :( [09:43] [matrix] or at least since before focal [09:43] [matrix] https://launchpad.net/ubuntu/+source/python-launchpadlib-toolkit [09:44] [matrix] Oh wait, it's not dead? [09:45] [matrix] It's in Bazaar, code activity present in 2023 [09:45] I did say used to be [09:45] https://bugs.launchpad.net/ubuntu/+source/python-launchpadlib-toolkit/+bug/1854972 [09:45] -ubottu:#lubuntu-devel- Launchpad bug 1854972 in python-launchpadlib-toolkit (Ubuntu) "RM: python-launchpadlib-toolkit: python2-only, Ubuntu-specific, depends on removed python-launchpadlib, no other reverse-dependencies" [Undecided, Fix Released] [09:45] [matrix] Looks like bdmurray may have tried to resurrect it in August, after it has been stagnant since 2013. [09:46] ooh [09:49] [matrix] The last time I used that I had to authenticate using Firefox :D [09:49] Just pinged him to see what's happening there. [09:49] The commit message looked very hopeful. [09:49] [matrix] https://bazaar.launchpad.net/~arsenal-devel/lpltk/2.x/revision/202 [09:50] * arraybolt3 switches chat clients on the same machine over and over for no good reason :P [09:50] [telegram] easy to do [09:50] [telegram] ;) [09:53] [matrix] For context I was using the lp-election-helper which uses the python libs https://discourse.ubuntu.com/t/how-to-create-an-election/1387 [13:51] $ dpkg --compare-versions 3.3.0-0ubuntu1 gt 3.3.0-alpha6-0ubuntu2 && echo "Condition met" || echo "Condition not met" [13:51] Condition not met [13:51] $ dpkg --compare-versions 3.3.0.0-0ubuntu1 gt 3.3.0-alpha6-0ubuntu2 && echo "Condition met" || echo "Condition not met" [13:51] Condition met [13:51] "gt" = "greater than" [14:01] W: calamares source: superfluous-file-pattern 3rdparty/kdsingleapplicationguard/* [debian/copyright:232] [14:01] W: calamares source: superfluous-file-pattern lang/calamares_i18n.qrc.in [debian/copyright:60] [14:01] W: calamares source: superfluous-file-pattern src/modules/localeq/img/chevron-left-solid.svg [debian/copyright:268] [14:01] bah [14:02] [telegram] <Люнесса> Ребят, привет!❤️ Хочу от себя порекомендовать отличный вид деятельности (P2P-трейдинг). Сфера новая и прибыльная. Вот мой наставник (https://t.me/GeorgiycrptoB), он отлично всё объясняет и помогает выйти на доход уже на обучении. Я пришла к нему с 0-в [14:02] [telegram] <Люнесса> Он тебя тоже всему научит и поможет заработать. Его интерес — это % от прибыли. [14:02] [telegram] <Люнесса> Вот ещё его канал (https://t.me/crypto_vers_gr) , там всё тоже подробно рассказывается о механике [14:03] [telegram] ta [14:03] [telegram] np [14:03] QA testers be aware: https://launchpad.net/ubuntu/+source/calamares/3.3.0.0-0ubuntu1 [14:04] I'll wait for that to build/publish in proposed, but I have a cala-settings-ubuntu upload following which changes the icon to our own Special Fancy one (as announced). [14:05] I'm unclear on whether we need to no-change rebuild cala-settings-ubuntu every time we do a major Calamares upload. We should eventually figure that out. :P [14:07] TBH... QML is really nice, but it should probably be moved to a dedicated .ui file... [14:07] Would make the Customize menu scale better. If y'all take a look at the 9to5Linux screenshot, there's a loooooooooooooot of empty whitespace. [14:07] That being said, on my VM, it looks fine, heh. [14:37] #debian-qt-kde on OFTC is a pretttty good channel to be in. [14:37] Specifically: https://salsa.debian.org/qt-kde-team/kde-6-planning/-/issues/2 [14:37] -ubottu:#lubuntu-devel- Issue 2 in qt-kde-team/kde-6-planning "KF6 source package names" [Opened] [14:37] And: https://salsa.debian.org/qt-kde-team/kde-6-planning/-/issues/1 [14:37] -ubottu:#lubuntu-devel- Issue 1 in qt-kde-team/kde-6-planning "Gitlab repo structure" [Opened] [14:37] Which we'll need for 24.10 Qt 6 stuff. [14:38] I completely agree with RikMills in this: we need to follow the same package naming scheme as Debian, to prevent future conflicts, even *IF!!!!!!!!* that means we have to go ahead of Debian. [14:38] And that's a huge "if." [14:39] Anyway, arraybolt3, kc2bez, @wxl, Eickmeyer I'm specifically interested in your feedback on the above, if you have any. [14:46] [telegram] I would say essential to be honest. I can't count the number of times it has been helpful to be there (re @lubuntu_bot: (irc) #debian-qt-kde on OFTC is a pretttty good channel to be in.) [14:46] ^^^^^^ [14:46] The Debian Qt KDE Team is awesome. [14:47] Also, unlike Libera.Chat, OFTC still has full Matrix bridging :P [15:30] tsimonq2: Agreed. [18:39] Anyone know of a way to pin every single binary package built from a certain source package? Ideally I'd like to pin the entire gcc-13 package to an older version in /etc/apt/preferences.d. (Trying to see if a new compiler broke things.) [18:40] FYI for QA testers: 20231212 does *not* have the new Calamares, I just kicked off a new respin. In 20231212.1 you should expect a Calamares version change. [18:41] 39 16 * * *for-project lubuntu cron.daily-live --live [18:41] I guess an apt hold might work in a pinch [18:41] [ ]noble-desktop-amd64.iso2023-12-12 16:54 [18:41] 54-39 is what, 15 minutes between start and finish? [18:42] The cronjob which grabs the retry requests runs every 5 minutes - so let's assume 15-20 minutes for a new ISO, as an absolute minimum. [18:43] arraybolt3: Not 100% sure, but you could either pin a core package that pulls in all the others, or bisect apt list --installed and the list of binary packages. [18:43] #ubuntu probably has a better answer on that *specific* one [20:03] arraybolt3: If you ever get bored and want to context switch: https://salsa.debian.org/qt-kde-team/issue-tracker/-/issues/70 [20:03] Eickmeyer: ^^^^ [20:04] 404 Page not found [20:04] waaaaaaaaaaat [20:04] hm [20:04] Are you logged into Salsa? [20:04] No [20:04] That'll ptobably do it heh [20:05] (Also my day is packed - satpy merge and fix, qtilitools and picom-conf Debian work, I need to reinstall a desktop and get a ZFS backup system working again, and stuff like that.) [20:06] and openMSX, forgot about that one [20:07] and the ciso maintainer in Debian wants to know if I'd like to be a comaintainer, don't know how to answer that :P [20:07] Sounds like your hands certainly are full :) [20:08] arraybolt3: I'd say yes lol [20:08] hah [20:15] arraybolt3: Anyway, I'm grabbing a package or two from the Qt 6 list. [20:15] +1 [20:16] You would hate me if I ever asked you to do copyright on *any* Qt 6 source. :P [20:21] [telegram] running @tsimonq2 install with new calamares.. [20:21] [telegram] running: tactical strike on Discourse server. (Reboot in progress!) [20:22] [telegram] /me installs @teward001 into /dev/null [20:22] * arraybolt3 enables shields on discourse.lubuntu.me [20:22] [telegram] error: missing universe: discourse_host_system [20:22] [telegram] First install new cala finished and looks ok so far [20:22] virsh gen-universe discourse_host_system [20:23] [telegram] Execution error: Input/Output error (re @lubuntu_bot: (irc) virsh gen-universe discourse_host_system) [20:23] sudo rm /var/output-blocker [20:23] [telegram] no seriously though i'm rebooting the baremetal system I have Discourse on because i'm trying to unfudge some Bridge tom-foolery right now to make it work proper with KVM stuff [20:23] [telegram] so either it works, or it breaks and I revert the networking [20:23] Sounds good, you know what you're doing :) [20:24] * arraybolt3 fiddles with Ubuntu Server trying to make a VM that can run Wine that can be SSH'd into with X forwarding so I can run theWord on a severely underpowered Chromebook by running it on my powerful laptop [20:39] Okay, qt6-sensors uploaded to Experimental. I might do one or two a day to start, just to get my Qt packaging skills back to par. [20:40] * tsimonq2 works on $dayjob but is around to answer pings [20:59] tsimonq2: I logged into salsa, 404 [21:00] (I'm not on the qt-kde-team, might be why) [21:00] I'm strictly on the multimedia-team [21:14] 404 viewing what? [21:15] [telegram] 404 viewing what? If you aren't given access to a repo and it's private/delegated/etc. then you have to be given access (re @lubuntu_bot: (irc) tsimonq2: I logged into salsa, 404) [21:15] [telegram] I know. @tsimonq2 wanted me to look at https://salsa.debian.org/qt-kde-team/issue-tracker/-/issues/70 (re @teward001: 404 viewing what? If you aren't given access to a repo and it's private/delegated/etc. then you have to be given access) [21:16] [telegram] ye it's locked out [21:16] [telegram] I was merely reporting that I don't have access. [21:16] [telegram] so @tsimonq2 you have failed [21:16] [telegram] :P [21:16] [telegram] RikMills ^ [21:18] [telegram] I know. Was asking which issue, as some mentioned earlier are definitely public (re @teward001: 404 viewing what? If you aren't given access to a repo and it's private/delegated/etc. then you have to be given access) [21:18] [telegram] https://salsa.debian.org/qt-kde-team/issue-tracker/-/issues/70 (re @RikMills: I know. Was asking which issue, as some mentioned earlier are definitely public) [21:20] [telegram] Yeah, I can see that, but not if logged out [21:21] [telegram] I can't see it even if logged-in, so it likely requires team membership. [21:23] [telegram] Yeah, I was added as a member some while back [21:30] [telegram] I guess you have to be the owner of the issue to change perms