[00:31] > <@arraybolt3:matrix.org> Simon Quigley:... (full message at ) [00:31] Read both of those messages at about the same time and I concur with Dan [00:32] kc2bez[m]: Hmm... how can you tell that the Ubuntu version was released before the Debian version? Looking at the changelog dates, I don't see that. [00:32] Yes, the changelog dates. [00:32] OH I get it. 0.11.0 vs 0.12.0. [00:32] That too [00:33] I read that as 0.12.0-2 followed by 0.12.0-0ubuntu1. That's how I got mixed up. [00:33] kc2bez[m]: This isn't *always* the case... ;) [00:33] https://metadata.ftp-master.debian.org/changelogs//main/l/lxqt-build-tools/lxqt-build-tools_0.12.0-1_changelog [00:34] tsimonq2: True. [00:34] Alright, so my brain made a typo internally. OK, thanks for clearing that up for me! [01:20] Just to be sure, if I set a Wiki page as being editible by no one and visible to no one in Phab, will I still be able to edit and view it? I'm making a draft for the Lubuntu Developer application and don't want it to be visible until it's actually ready for submission. [01:25] Phab's permissions have usually been pretty stable. Go for it [01:25] (I guess I don't need it to be hidden, it will be clear when I'm actually submitting it, I just don't want "Oh hey look he filed an application let's gooooo" and me to be like "WAIT hold up that's not quite done yet" :P) === guiverc2 is now known as guiverc [13:21] Simon Quigley: I noticed (ok, was way earlier shown by Andrew Lee) that if we have all of the package dependency version numbers normal, it may interfere with test builds (0.12.0 is greater than 0.12.0-ppa1). Andrew solved this problem by having LXQt package dependencies use version numbers like "0.12.0~" instead. Is it OK if I make Lubuntu do the same, or is that considered unnecessary in Lubuntu? [13:26] (Plus if we do it this way now, that will be one less thing to have to fight Debian LXQt about, and one less thing in the Ubuntu delta.) [14:17] @teward001: Hey, I have a spare laptop over here that I could be poking around in openQA-land with, would that be helpful or would my time be better spent elsewhere? [14:20] Perhaps I can tackle it from the openSUSE end while you're working on the Ubuntu end? [16:08] In the absence of further input on this topic, and while I'm stalled on other fronts, openSUSE openQA, here I come! [16:09] If nothing else, this will give me a great environment in which I can break things freely. [16:12] Great, now I have the awesome case where there's three SD card readers that only go missing when I could use them... (ok not really but wow, three missing ones? I only need one!) [16:23] [telegram] arraybolt3: i don't think there's anything you can do on the OPenQA end to assist me [16:23] [telegram] the first step is getting the central UI set up and working [16:23] [telegram] once THAT'S done we'll tackle workers being installed and connected to the system to receive tasking [16:24] [telegram] so the answer remains the same: there's nothing you can do yet [16:24] Nice. In the mean time I can learn what I'm doing with making workers and what not. [16:24] [telegram] i'll poke you and Simon when i'm anywhere *near* testing [16:24] [telegram] and i'm working $DAYJOB [16:24] +1 [16:24] [telegram] and trying NOT to commit crimes against the renovations being done in the vacant apartment below me so... [16:24] [telegram] *hisses angrily at the renovations downstairs* [16:27] [telegram] well my irccloud died (figures) [16:27] [telegram] oh well i'll get it back once payday happens [16:48] :( [17:14] "Simon Quigley: I noticed (ok..." <- It's unnecessary :) [17:15] "(Plus if we do it this way now..." <- Not worth carrying a delta, I'd also argue it's unnecessary [17:15] K, will omit it for now and if/when we eventually sync from Debian I won't worry about it coming over. [17:15] * tsimonq2 joins teward in hissing angrily at renovations [17:15] * tsimonq2 coffee [17:16] Sigh, I really should get some of that. [17:16] (I don't want to stop working and make time to make coffee :P) [19:36] Simon Quigley send coffee pls [19:37] * arraybolt3[m] unsticks teward's tab key and then sends in an entire battleship full of coffee [19:37] * genii twitches [19:37] *consumes the coffee, then sticks arraybolt3's keyboard in the acid tank* [19:37] * arraybolt3[m] attaches the spare keyboard [19:46] * tsimonq2 throws teward a gallon of coffee from Kwik Trip [19:48] > * <@genii:libera.chat> twitches [19:48] time to go brew more coffee :P [19:48] especially when you make your presence known >:D [19:53] teward[m]: As you may know I have "coffee" on my highlight list LOL [19:53] yes i know ;) [19:53] * genii gets the Aeropress going [20:14] The first thing on my list is actually publishing Backports... it's been quite a weekend. [20:15] I'm putting it through a battle test in a virtual machine right now, I'm thinking I'll need another NCR for qps, but let's see what ends up uninstallable... [20:15] I'm doing the package audits, and also fighting with a random Matrix user who decided they didn't like me and thought harassment was a good idea... [20:16] That being said, I really don't want to do this again manually without ppa-britney. I'd probably set the 7 day aging requirement and let it handle automated migration. This isn't absolute best practice, using Britney is :/ [20:16] (More like gathering evidence and then sending an abuse report) [20:16] arraybolt3[m]: I really dislike those types of arguments, harassment is never a good thing :/ [20:17] Eh, they're just an average troll but with some technical knowledge behind them. No big deal. [20:18] Heh, fair enough :) [20:18] [telegram] who's a troll that i have to squish? [20:19] [telegram] or are you talking about yourselves ;) [20:19] * tsimonq2 throws @teward001 into the abyss [20:19] [telegram] too late i'm already there [20:19] @teward001: Some random person from Matrix HQ who came in with a Matrix CoC breaking profile picture and then got really mad when I told them that it wasn't OK... [20:20] [telegram] came in where? here in devel? [20:20] @teward001: No, in the #matrix:matrix.org room. [20:20] [telegram] ah [20:20] [telegram] unless you're a moderator/god you should instead tell mods that ;) [20:20] [telegram] rather than confront people directly. because people get pissy when people backseat mod [20:21] (I use Matrix for more than just Lubuntu development - I help moderate #ubuntu:matrix.org and most of the craziness happens in #matrix:matrix.org so I hang out there to help people who need it and ban people who need it. [20:21] lubot: I figure better to tell someone who's clueless that something's wrong and have them fix it than to just get their entire user account banned. [20:22] [telegram] think you meant to ping teward001 ;) [20:22] [telegram] not the bot 😔 [20:22] [telegram] :P * [20:22] I used the Matrix reply feature. [20:22] * arraybolt3[m] kicks Telegram [20:22] Yeah, that's a bit wonky sometimes. [20:24] Okay, I'm publishing Backports... waiting 30-60 minutes to make it public, because the Launchpad publisher just got hammered and I'm about to hammer it even more :P [20:31] i would suggest waiting 6 hours then :P [20:31] because stuff's fubar xD [20:32] publishing an entire archive snapshot to all mirrors used to take 2 hours or so, back in the day [20:32] I'm inclined to believe that even with publishing of 400+ packages in proposed, 6 hours is more dinstall speed :P [20:32] given the slow speed of the s390x and riscv builders i would make 2 hours a 4 hours estimate [20:32] at least, nowadays [20:32] I copied binaries, I didn't rebuild them [20:32] so no builders needed [20:32] ah well that's easy [20:32] assuming Backports and your staging location are identical sources, etc. [20:33] for obvious reasons :P [20:33] yeah identical sources identical binaries :P [20:33] here, I'll set everything to publish at 3 PM today, because I'm feeling lucky :P [20:33] (Central US) [20:34] heh [20:34] * arraybolt3[m] watches Simon tell the publisher to start working yesterday and it somehow actually does so [20:34] you have direct msgs via matrix btw simon [20:49] > * <@arraybolt3:matrix.org> watches Simon tell the publisher to start working yesterday and it somehow actually does so [20:49] hahahaha [20:49] https://lubuntu.me/jammy-backports-22-04-1-lxqt-1-2/ will be the link, should publish at 3 PM [20:51] I took care of scheduling a tweet, Telegram announcement message, and a Reddit post [20:51] [telegram] *schedules tsimonq2 for mandatory indoctrination sessions* [20:51] oh no my table it's broken [21:25] Simon Quigley: So far I've done a few tweaks to lxqt-build-tools, libqtxdg, and liblxqt. Should I be letting you know as these changes are made so you can sponsor them, or should I wait until a big chunk is done or until you ask for them? [21:28] Simon Quigley: Also wasn't there a Qt problem that could cause upgrade-related issues if you upgraded from 22.04+Backports to 22.10? If so, that might be worth mentioning in the blog post. [21:49] One last thing - it looks like libsysstat got entirely overlooked for the latest stack update, and has been overlooked since Impish. The only reverse depends I see is lxqt-panel (which by the way isn't in the build dep graph, so we may want to fix that). Is that safe for me to turn into a new upstream release? [21:50] (Er, I mean the dependency that lxqt-panel has on libsysstat isn't in the graph.) [21:50] "Simon Quigley: So far I've..." <- Let me know a few at a time, I'll start by reviewing those three [21:50] "Simon Quigley: Also wasn't there..." <- You're right, but I think that needs to be a wider fix. What text would you suggest putting in the blog post to say as such? [21:51] arraybolt3[m]: That's because it hasn't had an upstream release since Impish :P we may want to do a packaging update... [21:51] Ah, so it is time for me to do a new upstream release packaging update. 👍️ [21:53] tsimonq2: I dunno, something to the effect of "You should only use this if you intend to only upgrade to the latest LTS when it is released. Upgrades from 22.04 to an interim release are not supported if you use this PPA. Attempting to upgrade to an interim release will likely cause trouble if you have this PPA enabled." [21:53] (By the time 24.04 is out we'll hopefully have something a lot newer than LXQt 1.2.0 in the repos, along with newer Qt and all that jazz.) [21:53] Let me modify the blog post really quick, and I'll report back. Thanks for the reminder :) [21:58] arraybolt3: Should be done. As long as we have a standing list, I'm okay with you continuing to work on it :) [21:58] * tsimonq2 has quite a list today [21:58] Ping me for fires, otherwise I'm digging in lol [21:59] You got it! [22:17] * kc2bez[m] pings fire at Simon Quigley 😏 [22:17] everyone run!!!!!! [22:17] XD [22:17] Thanks for your work on the backports! [22:17] No worries :) [22:27] Simon Quigley: Actually, just hit a fire.... (full message at ) [22:28] done [22:29] Success, thank you! [22:30] * arraybolt3[m] is exhausted and needs a break