[03:18] apparently KDE is aware of RFC 7168 https://apps.kde.org/kteatime/ [03:40] [matrix] https://matterbridge.lubuntu.me/434983b3/screen.png [03:41] [matrix] how does that look for a preview image in lxqt-config-appearance for Lubuntu Arc? [03:41] [matrix] even though we don't add the spacer by default i followed [LXQt's example](https://github.com/lxqt/lxqt-themes/pull/70) [03:41] -ubottu:#lubuntu-devel- Pull 70 in lxqt/lxqt-themes "Consistent preview images for themes" [Merged] [03:42] despite this, clearlooks and leech both seem to lack it but i dunno https://github.com/lxqt/lxqt-themes/commit/2555627249b64c0dff9240af8a6aca341f33fac4 [03:42] -ubottu:#lubuntu-devel- Commit 2555627 in lxqt/lxqt-themes "Consistent preview images for themes (#70)" [06:58] [telegram] That would look way better [12:20] I agree, honestly. [12:23] [matrix] Yes, it certainly looks clearer. [14:52] We're at about 6 packages having autopkgtest failures against glibc, which blocks the rest of LXQt. [14:52] Bug 2031912 is a good reference to track. [14:52] -ubottu:#lubuntu-devel- Bug 2031912 in h5py (Ubuntu) "glibc 2.38 causes hangs on some openMPI-using packages" [Critical, New] https://launchpad.net/bugs/2031912 [16:09] [matrix] https://matterbridge.lubuntu.me/5baea610/image.png [16:09] [matrix] oh here's it in context [16:10] [matrix] i don't know why there are svg preview images. they're not upstream and they're unnecessary from what i can tell [16:14] [matrix] ah, it's only Lubuntu Arc that has the svg preview. i'm gonna can that in this process. it will be less confusing. [16:33] [matrix] so i guess i should create the mantic branch for artwork. and i should probably change the * copyright to me [16:57] [matrix] someone check my work; it's been a while https://git.lubuntu.me/Lubuntu/artwork/commit/a431e1a57c707c7e5b214d61fc6f212d39a0375d [16:57] -ubottu:#lubuntu-devel- Commit a431e1a in Lubuntu/artwork "update Lubuntu Arc LXQt theme preview" [17:05] [telegram] wxl: grr use self contained commits [17:05] [telegram] UTC+0 for TZ? [17:08] @tsimonq2 you're asking for one commit per change? [17:08] as for the tz i blame teward [17:09] [telegram] At least it's committed, just future reference on that, yeah [17:10] [telegram] I won't go full debian-qt-kde and say there needs to be one for creating the changelog entry with the team name, one with each individual change, one for releasing it ... just be reasonable, try not to throw it all in one commit [17:10] [telegram] idrc if you force push you know what you're doing wxl XD [17:13] well @tsimonq2 i *DID* know what i'm doing which is why i'm asking for another pair of eyes [17:17] [telegram] we've all been guilty of piling in some changes, then thinking "damn, that is too much for one commit but I have better things to now to separate it out" ;) [17:19] i see two possible commits from my one: an upload to mantic commit and a change the image commit. that's about it. but if what i'm hearing is every file change needs its own commit, ok. [17:32] [telegram] if changes to multiple files serve one narrow enough purpose that can be given in one changelog line, then I wouldn't say that [17:34] well again in my example the upload to mantic is almost like necessary maintainence, so i kind of considered it something i could shove in with the rest of the commit. but i'm hearing simon likes per file changes. [17:35] [telegram] me and simon may differ there :P [17:35] [telegram] as I am not officially anything lubuntu, I will leave that there [17:36] well me and him too but i'm not necessarily trying to argue one way or another [17:36] [telegram] one thing I think of is what if I had to revert the commit because of a problem [17:37] yes. don't want a bunch of unrelated stuff intertwined [17:37] [telegram] trying to do too much in a commit makes that a pain [17:37] i think we all agree in self-contained commits, just different definitions of it XD [17:38] [telegram] indeed [18:27] ok well i uploaded and i can't find the package anywhere? [18:29] [telegram] Was it accepted? [18:30] the upload was accepted but i mean i don't even see it in the queue [18:32] [telegram] This is for lubuntu-artwork right? Latest upload shows 22.04.3 in LP https://launchpad.net/ubuntu/+source/lubuntu%2Dartwork [18:32] right and uploaded 23.10.1 [18:32] ^ i [18:33] [telegram] 🤔 [18:33] [telegram] Hmm [18:37] and i can't dput again because it says it's already been uploaded. uhhhhh [18:37] [telegram] remove the file that indicates it was uploaded [18:38] [telegram] its just a file in the folder with the changes file [18:39] oh heh i never knew that [18:40] i think the problem might have been that i didn't have my key trusted but it if so the fail was kind of silent (it gave an error but the upload was successful) [18:42] well that went without a hitch but still can't find it [18:44] [telegram] You should get an email [18:45] oh right fair point [18:47] ah ha i have no upload rights [18:47] anyone want to fix that? :) [18:48] [telegram] #blamesimon [18:49] indeed [18:49] [telegram] I just have my phone with me at the moment. [18:50] ^ @tsimonq2 fix it [18:52] oh heh i might be able to fix this myself [18:56] https://launchpad.net/ubuntu/mantic/+queue?queue_state=3&queue_text=lubuntu-artwork horray [19:29] so have we decided about seeding krita? what about dropping libreoffice-draw (and with it -impress)? [19:40] [telegram] I think we need to keep impress [19:42] i understand that thinking, but it will force us to keep draw as it is a depend [19:58] [telegram] That is unfortunate, it would be nice if they weren't attached quite so tightly. [19:58] [telegram] I am OK with adding krita [19:58] true but i understand why: drawing features are part of impress [19:59] maybe i should bring this up on the forum for discussion? [20:00] [telegram] I am good with that too [22:08] [matrix] Looks like artwork made it to the release pocket. [22:14] [matrix] sure does yay [23:13] [telegram] @teward001 to be clear, you added wxl back to ~lubuntu-dev right? [23:14] [matrix] I did, see above [23:14] [telegram] I'm officially +1, @kc2bez guiverc? :) [23:15] [telegram] if a member of the DMB is grumpy they'd tell us we're breaking policy [23:15] [telegram] I'll go take responsibility for that [23:15] [telegram] You're obviously a notable exception [23:16] [matrix] Sowwy [23:17] [telegram] Bah I'm not worried about it [23:17] [telegram] Two issues - if @teward001 used his executive power technically we just need to ratify it. DMB is their own policy [23:17] [telegram] Again, I have your back here [23:18] [matrix] Thank you [23:18] I'm +1 with wxl being on lubuntu-dev (I assumed he was there already) [23:18] * guiverc hadn't looked sorry [23:18] [matrix] I was a former member yes [23:21] tsimonq2: keyring updates arent instant fyi [23:22] and if lubuntu-dev is not upload-rights for a package yet wxl cant upload it [23:24] [telegram] teward: Debian keyring updates take a month or two, with Ubuntu it's simply an acl edit [23:24] [telegram] lubuntu should obviously have upload access to our artwork [23:24] but i have no objections. lubuntu-dev is a delegated team so. [23:24] [telegram] (I know 'cause I set up a local Soyuz the other day) [23:48] [telegram] What Simon said. (re @tsimonq2: I'm officially +1, @kc2bez guiverc? :)) [23:48] [telegram] So, it's unanimous :) [23:49] [telegram] \o/ [23:49] :)