[02:37] -lugito:#lubuntu-devel- [T58: consider minimal install] kc2bez (Dan Simmons) commented on the task: https://phab.lubuntu.me/T58#4080 [02:47] kc2bez ack on the changes. I think I missed that misc:deps part. And wxl confused me about the version number. 😛 [02:48] Didn't you say wxl we should use 0ubuntu1 if we aren't modifying the package that comes from Debian. [04:00] unless i'm remembering something/thinking about something wrong [04:01] or at least it's based on logical consistency given that the similar thing in debian is -1 [04:04] looking at the wiki @kc2bez referenced, i'm not seeing anything that suggests one way or another [04:09] here's the "packaging new software" section of the ever-crusty ubuntu packaging guide and you'll note that they give it a 0ubuntu1 version, meaning it's never been in debian and it first appeared in ubuntu https://packaging.ubuntu.com/html/packaging-new-software.html#building-the-package [04:10] er well that doesn't mean that it hasn't been in debian, but it hasn't been patched in debian [04:12] er, i don't know. X'D [04:12] if i look at lxqt-config, it looks like alf never had an upstream-version-0 or upstream-version. always upstream-version-1 or more [04:22] look at dolphin and you'll see there's a 4:20.04.3-0ubuntu1, followed by -1, followed by 1ubuntu1. so we packaged it first, then debian did, then we merged the two. [04:22] so the minimum version for a new ubuntu package is 0ubuntu1. there, done. dang. i'm writing that into the wiki XD [04:24] i find it odd that debian version numbers for linux packages don't have a -1 [04:34] [telegram] legacy explosions? [04:34] [telegram] :P [04:34] aroooo? [04:35] [telegram] *yawns* [07:10] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_screengrab just succeeded after failing: https://ci.lubuntu.me/job/groovy_stable_screengrab/330/ [07:15] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_screengrab just succeeded after failing: https://ci.lubuntu.me/job/groovy_stable_screengrab/330/ [07:22] wxl: so the version number I wrote is correct then? [07:24] it is as far as I understand. [07:25] also, just noticed the d/control file. It had debhelper-compat set to 12. Should be 13 right? [07:26] oh wait so they versioned it 0.8.1-1 in debian [07:27] so ours should be 0.8.1-1ubuntu1 right? [07:27] ughhh!! sooo much confusion! [07:27] * The_LoudSpeaker leaves [07:27] * The_LoudSpeaker goes to have some food. [09:33] That's it The_LoudSpeaker you got it now. [09:34] Approve it then. I will push rn. [09:35] [telegram] sure, I will give it a look. [09:35] Also, is there a better way to handle merges? [09:36] Fixing 10s of these in every translation file for a merge is not fun. [09:36] https://imgur.com/a/13ordVj [09:37] I'd rather clone from upstream debian, edit the debian/ folder as needed and push. [09:37] Would be faster. [09:40] Or can we improve merge o matic to provide some way for packager to select which side changes to keep, per file. So we don't have to manually keep pressing backspace tons of times in translation files? [09:44] [telegram] When we met with Simon he said he doesn't even use that. He just grabs the Debian source and Ubuntu source and merges the diffs together. [09:44] Doing that only rn. [10:27] thank you @Leokolb & KGIII for your continued testing :) [11:04] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lxqt-session just failed after succeeding: https://ci.lubuntu.me/job/groovy_stable_lxqt-session/324/ [11:04] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lxqt-session just failed after succeeding: https://ci.lubuntu.me/job/groovy_stable_lxqt-session/324/ [11:35] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_pcmanfm-qt just failed after succeeding: https://ci.lubuntu.me/job/hirsute_stable_pcmanfm-qt/84/ [11:35] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_pcmanfm-qt just failed after succeeding: https://ci.lubuntu.me/job/hirsute_stable_pcmanfm-qt/84/ [12:56] kc2bez: debhelper-compat is still 12? [12:56] Saw it as 13 in micro [12:58] 13 is the current version but the upstream Debian package is still at 12. You can bump it to 13 but you need to mention it in the changelog that you did so. [13:00] https://salsa.debian.org/lxqt-team/lxqt-build-tools/-/blob/debian/0.8.0-1/debian/control [13:00] That is the debian control file from Debian ^ [14:18] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_libfm-qt FAILURE: https://ci.lubuntu.me/job/hirsute_stable_libfm-qt/156/ [14:18] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_libfm-qt FAILURE: https://ci.lubuntu.me/job/groovy_stable_libfm-qt/498/ [14:18] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_libfm-qt FAILURE: https://ci.lubuntu.me/job/groovy_stable_libfm-qt/498/ [14:19] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_libfm-qt FAILURE: https://ci.lubuntu.me/job/hirsute_stable_libfm-qt/157/ [15:04] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lxqt-archiver FAILURE: https://ci.lubuntu.me/job/groovy_stable_lxqt-archiver/508/ [15:15] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-archiver just became unstable after failing: https://ci.lubuntu.me/job/focal_stable_lxqt-archiver/337/ [15:30] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-archiver FAILURE: https://ci.lubuntu.me/job/hirsute_stable_lxqt-archiver/159/ [15:31] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-archiver FAILURE: https://ci.lubuntu.me/job/hirsute_stable_lxqt-archiver/160/ [15:47] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-archiver UNSTABLE: https://ci.lubuntu.me/job/focal_stable_lxqt-archiver/338/ === tomreyn_ is now known as tomreyn [16:01] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lxqt-archiver FAILURE: https://ci.lubuntu.me/job/groovy_stable_lxqt-archiver/508/ [16:41] hmmm, focal daily failed to build today. [16:41] [telegram] kc2bez: do you ahve council list mod access? not sure if you released my msg or if wxl was going to [16:42] [telegram] and where's the build logs im' curious [16:42] [telegram] or was this on CI and I need to stab it? [16:42] Nah, it is the daily iso. [16:42] that kind of sucks with the next point release due in feb [16:43] a little late for breaking changes i'd think [16:43] agree [16:45] wonder if this is related [16:45] /usr/lib/python3/dist-packages/pylxd/models/_model.py:116: UserWarning: Attempted to set unknown attribute "location" on instance of "Container" key, self.__class__.__name__ [16:45] probably not [16:45] The following packages have unmet dependencies: linux-generic : Depends: linux-image-generic (= 5.4.0.65.68) but it is not going to be installed [16:45] yup [16:45] tl;dr it should be breaking everything [16:45] just got there. [18:09] *smacks wxl upside the head* [18:10] oh shush [18:10] wxl: any change to the libx stack will result in basically a whole new devcycle of testing, etc [18:10] for each release [18:10] for all flavors [18:11] gosh you are really good at repeating yourself, aren't you? XD [18:11] I'm not taking that one up to the dev team, you can if you want (i expect you'll be smacked a lot harder) [18:12] i honestly hadn't considered it from that perspective, but that pretty much kills it [18:12] however, i will mention libx11 has had SRUs before [18:13] wxl: but were those SRUs cherrypicked revs or full backports? [18:13] if they're cherrypicked revs that's one thing [18:13] if it's a full backport then that's a whole different thing [18:13] if you were to ask me for a knee jerk reaction, i consider it a total waste of time [18:13] if you have a cherrypicked rev to fix the bug I'd have a different mindset [18:13] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-policykit just succeeded after failing: https://ci.lubuntu.me/job/hirsute_stable_lxqt-policykit/81/ [18:13] but a straight backport? Nope. [18:13] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-powermanagement just succeeded after failing: https://ci.lubuntu.me/job/focal_stable_lxqt-powermanagement/565/ [18:13] or if they're Security patches, in which case that's Security Team stuff and tests [18:14] yeah looks like cherry picks [18:14] it's quite possible the required change could be picked out, but i think it's unlikely [18:17] in precise did have 2:1.4.4-2ubuntu1, 2:1.4.4-4, and then 2.1.4.*99.1*-0ubuntu1. weird versioning but apparently it was a new upstream release [18:18] [telegram] well that's Precise - a dead OS from our perspective now. [18:18] [telegram] (the community perspective) [18:18] [telegram] we DO have to be careful when doing anything X-stack related [18:18] [telegram] esp. when it pulls in nVidia binaries :P [18:18] still, even if this is doable/reasonable, with only 3 months of lubuntu support, and the fact that it affects a much wider world than just lubuntu, i think it's best to leave it to others to consider [18:18] [telegram] since those're specially handled [18:18] [telegram] i agree. [18:18] [telegram] with only 3 months of support from the Lubuntu project for the release, it's not something the Lubuntu Team should focus on [18:19] I don't know why I bothered with virtman; just installed VirtualBox this afternoon and everything was smooth sailing, whereas virtman still isn't working. VirtualBox even has KVM virtualization 🤗 [18:19] [telegram] esp. since the far-reaching ramifications of updating the base X stack libs can cause some hell if someone tries to upload it [18:19] And that is why open source won't win for now. [18:19] if it were my choice, i would have dropped lxde sooner. the gtk2 depends alone are enough to make a person mad. if people want to use old crap, there's always freebsd or centos or something XD [18:20] [telegram] heh [18:21] i will give lxde credit: they have kind of started developing more. but the activity is still way, way low [18:23] It isn't as polished as the competition. I even **wanted** to use the open source option, but like I said it isn't as polished as the (closed) competition. [18:24] um, virtualbox is open source [18:25] @guiverc: thank you @Leokolb & KGIII for your continued testing -- No problem. [18:26] [telegram] wxl: https://gitlab.freedesktop.org/xorg/lib/libx11/-/commit/dbb55e1a5e82870466b095097d9e46046680ec25 might be the solution to that 'bug' but that's not my call. See the Ubuntu Bug 1782984 [18:26] [telegram] np (re @lubuntu_bot: (irc) thank you @Leokolb & KGIII for your continued testing :)) [18:26] [telegram] https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/1782984 [18:29] @teward001 yeah that's what i was saying. we *might* be able to cherry pick it. it's a small patch for that one fix. but who knows what other architectural fixes preceeded that that allows for that in 1.7 but not 1.6? [18:29] still, my thinking is that if someone wants to bother with that, it should be ubuntu, not lubuntu [18:31] They are? 😱 [18:31] [telegram] wxl: well it's been seen there for some time yes [18:31] [telegram] Ryu: yes, but owned by Oracle [18:31] vbox is open source except for the ext packs, and even then it's technically "open source" but it's just a non-free license [18:31] [telegram] vbox has two variants, the Open Source variant that we get to package, and an Enterprise version that's expensive as heck [18:31] [telegram] yep [18:32] [telegram] wxl: it's been known for some time but if you want to suggest to the dev team to push the cherrypick, I'd suggest you email ubuntu-devel or ubuntu-devel-discuss for that [18:32] [telegram] since that's where the Ubuntu stuff sits :P [18:34] maybe recommend that to the OP [18:35] [telegram] *gives wxl more work* [18:35] [telegram] you can tell em ;) [18:35] sigh [18:36] [telegram] i'm on a teleconference so I can't [18:36] [telegram] :P [18:36] love you bye [19:04] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-panel just failed after succeeding: https://ci.lubuntu.me/job/hirsute_stable_lxqt-panel/80/ [19:05] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lxqt-panel just failed after succeeding: https://ci.lubuntu.me/job/groovy_stable_lxqt-panel/336/ [19:30] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-panel just failed after succeeding: https://ci.lubuntu.me/job/hirsute_stable_lxqt-panel/80/ [20:17] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-sudo just failed after succeeding: https://ci.lubuntu.me/job/focal_stable_lxqt-sudo/565/ [20:26] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-sudo just failed after succeeding: https://ci.lubuntu.me/job/focal_stable_lxqt-sudo/565/ [20:58] Discourse is throwing a 502 error, by the way. [20:58] [telegram] that's because it's mid-update [20:58] Ah, that explains it. [20:58] [telegram] it'll resolve itself in a bit [20:58] [telegram] i don't announce the update cycles ;) [20:59] [telegram] but it won't let me look at the update manager to update plugins, etc. without running the rebuild step and getting us on latest Image so [20:59] LOL I use WordPress a lot and let it update itself. It too tosses errors when it's updating certain aspects. [21:00] [telegram] yep well this is a heavy Ruby app [21:00] [telegram] so :P [21:00] [telegram] should be up again [21:00] [telegram] ... or not. (another update) [21:01] Yeah, I've taken a look at their github page. [21:02] For forums, I'm an old-school SMF fan. It makes me feel pleasantly nostalgic. [21:02] [telegram] lol [21:02] [telegram] i do the updates to Discourse about once a month [21:02] [telegram] this is a month since the last update cycle so [21:02] i LOOOOOOOOOOOOOOOOOOATHE forums. discourse is the exception. and even then, it's weird. [21:03] Any great new features to look forward to? [21:03] [telegram] wxl hates all methods of technical support forums even askubuntu [21:03] well see there again i kind of like askubuntu [21:03] [telegram] you're only saying that since i'm a diamond mod there :P [21:03] i hate to say it but i think i like jeff atwood's work [21:03] I like the whole SE network of sites. There's a plugin to turn WordPress into a similar site. I have been meaning to play with it. [21:11] [telegram] /me throws gems at @teward001 (re @teward001: yep well this is a heavy Ruby app) [21:12] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_obconf-qt just failed after succeeding: https://ci.lubuntu.me/job/hirsute_stable_obconf-qt/80/ [21:13] [telegram] *absorbs the gems and redirects them to /dev/null* [22:33] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_pavucontrol-qt just failed after succeeding: https://ci.lubuntu.me/job/groovy_stable_pavucontrol-qt/326/ [22:49] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_sddm UNSTABLE: https://ci.lubuntu.me/job/focal_stable_sddm/605/ [22:49] Ah, so it is open but not libre? Too bad, but at least it is plug-n-play vs virtman 🙃 [22:49] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_sddm UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_sddm/110/ [22:49] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_sddm UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_sddm/362/ [22:51] [telegram] I don't remember doing a bunch to get virt-manager working but it was a while ago. [22:51] me either, to be honest [22:51] i'm just used to vbox [23:04] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_qtermwidget just failed after succeeding: https://ci.lubuntu.me/job/hirsute_stable_qtermwidget/77/ [23:15] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_sddm UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_sddm/363/ [23:16] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_sddm UNSTABLE: https://ci.lubuntu.me/job/focal_stable_sddm/606/ [23:16] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_sddm UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_sddm/111/ [23:35] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lxqt-session just succeeded after failing: https://ci.lubuntu.me/job/groovy_stable_lxqt-session/325/ [23:40] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_libfm-qt FAILURE: https://ci.lubuntu.me/job/hirsute_stable_libfm-qt/158/ [23:42] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_libfm-qt FAILURE: https://ci.lubuntu.me/job/groovy_stable_libfm-qt/499/