[00:05] <arraybolt3> Fixing up some IMO critical issues currently, I still hadn't added a way to enforce only one instance being running at a time, nor had I enabled displaying the window in a way other than by clicking a systray icon.
[03:03] <arraybolt3> well everyone's going to hate me for my commit message's verbosity (or lack thereof), but I had to change so many tiny things everywhere that I didn't feel a bunch of individual commits were worth the effort (especially not this early in Lubuntu Update's development history).
[03:03] <arraybolt3> so... pushing "A bunch of improvements" :P
[03:03] <tsimonq2> bah LGTM *rubber stamp*
[03:05] <arraybolt3> Will try to test it a bit more tomorrow and package it. (I didn't get to do a final "does this still update things properly?" test so I'm leery of calling this alpha-quality yet.)
[03:05] <arraybolt3> but by tomorrow there'll probably be new updates to install :D
[03:13] <tsimonq2> Sounds good!
[03:31] <tsimonq2> https://ubuntu-archive-team.ubuntu.com/transitions/html/html/qt-5.15.12.html
[04:13] <arraybolt3> tsimonq2: currently attempting to supplant lubuntu-update-notifier with Lubuntu Update, and I have a question.
[04:14] <arraybolt3> I think the systemd-timer thing isn't necessarily a great idea, since it may attempt to run the updater before the user has even logged in.
[04:14] <arraybolt3> (I could be mistaken there but that's what it looks like to me.)
[04:15] <arraybolt3> Do you mind horribly if I just revert back to the autostart way we used to always do this?
[04:16] <arraybolt3> (also repeatedly executing the new updater will not have the intended effect - it is designed to run as a persistent background process. Re-launching it is how you force the window to appear.)
[04:26] <lubot> [telegram] <tsimonq2> Are systemd timers both executed once on login and then again when scheduled, or just when scheduled?
[04:26] <lubot> [telegram] <tsimonq2> I'm really not a fan of any kind of persistent background service unless it's a completely separated daemon
[04:27] <lubot> [telegram] <tsimonq2> Remember those issues we were having where the LXQt processes are still left hanging with the update notifier?
[04:27] <lubot> [telegram] <lynorian> I mean having a background storage running for the updater when not logged into lxqt would use resources if you logged into another desktop enviorment as well right
[04:28] <arraybolt3> umm, Lintian is b0rked
[04:28] <lubot> [telegram] <tsimonq2> That's the way it currently works/that's the bug but it's not by design
[04:28] <lubot> [telegram] <tsimonq2> yeah :(
[04:28] <lubot> [telegram] <tsimonq2> I didn't quite have time today to finish that up, but check the transition tracker
[04:28] <lubot> [telegram] <tsimonq2> May just be an NCR
[04:28] <arraybolt3> tsimonq2: yeah, I see what you're saying. I don't know how exactly systemd timers really work, I sort of assumed they just always executed when scheduled.
[04:30] <lubot> [telegram] <tsimonq2> *shrug* nah I get what you're saying, I dunno, those are just my thoughts, if you have something that works and is still resource efficient I'm game to hear it
[04:31] <lubot> [telegram] <tsimonq2> With Lintian... it's definitely broken on Sid right now but is Ubuntu broken too?
[04:31] <lubot> [telegram] <tsimonq2> What's happening arraybolt3?
[04:33] <arraybolt3> ahem:
[04:33] <arraybolt3> !ping
[04:33] <arraybolt3> gah
[04:33] <ubottu> pong!
[04:33] <arraybolt3_> tsimonq2: https://termbin.com/xugr
[04:33] <arraybolt3_> (sorry, my main IRC client went into hyper lag mode)
=== arraybolt3_ is now known as Guest4071
=== Guest4071 is now known as arraybolt3-kirc
[04:34] <arraybolt3-kirc> tsimonq2: https://termbin.com/xugr
[04:34] <arraybolt3-kirc> did that get through the first time?
[04:34] <arraybolt3-kirc> I can't hardly see what's happening :P
[04:35] <arraybolt3-kirc> looks like my bouncer went down
[04:38] <arraybolt3> oh there now it works
[04:51] <arraybolt3> tsimonq2: I think that since we have other persistent services of sorts in LXQt (namely the panel, PCManFM-Qt, etc.), I'd like to *try* doing this the easy way since it seems cleaner. Iff it causes issues, we can use your hard systemd-based way.
[04:51] <arraybolt3> s/iff/if/
[04:55] <lubot> [telegram] <tsimonq2> hahahahahaha looks like it's Perl NCR time
[04:56] <lubot> [telegram] <tsimonq2> *shrug* just test with loginctl and make sure that either SDDM or LXQt kills the session right :)
[05:08] <arraybolt3> yeah, that ought to work
[16:10] <lubot> [telegram] <Leokolb> Re Calamares @tsimonq2 selecting "about" on left hand side of installer has links to Calamares team etc but no internet set up until after reboot -
[16:42] <lubot> [telegram] <tsimonq2> If you happen to have the time could we please get a bug to track this? (re @Leokolb: Re Calamares @tsimonq2 selecting "about" on left hand side of installer has links to Calamares team etc but no internet set up until after reboot -)
[16:42] <lubot> [telegram] <Leokolb> Will do .. (re @tsimonq2: If you happen to have the time could we please get a bug to track this?)
[16:43] <lubot> [telegram] <tsimonq2> Thank you :)
[17:00] <lubot> [telegram] <Leokolb> Subbmitted bug 2049088 (thought that this might have been reported before - but found nothing..  :) (re @tsimonq2: Thank you :))
[17:00] -ubottu:#lubuntu-devel- Bug 2049088 in calamares (Ubuntu) "Calamares install has links to external site but no browser until after install" [Undecided, New] https://launchpad.net/bugs/2049088
[17:25] <tsimonq2> So, after further investigation, yes, the core issue for this has been reported before: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1981473 - that being said, this specific issue is not one that was in the scope of that bug report.
[17:25] -ubottu:#lubuntu-devel- Launchpad bug 1981473 in calamares (Ubuntu) "Calamares fails to open 'donate' or 'Lubuntu support'" [High, Confirmed]
[17:26] <tsimonq2> IMO both are useful :)
[18:55] <arraybolt3> Back to work today on Lubuntu Update - I forgot that it needed a patched lxqt-sudo, and Palo made some serious improvements to my original patch which I need to test.
[18:56] <arraybolt3> so anyway, currently tangled up with that, also $DAYJOB may interrupt at any time, but that's what I'm on currently.
[18:57] <arraybolt3> also tsimonq2: anything wrong with the version number "1.0.0~alpha1" for the lubuntu-update-notifier package containing Lubuntu Update?
[19:18] <arraybolt3> looking hopeful
[19:20] <arraybolt3> alrighty, it works!
[19:20] <arraybolt3> well enough anyway - it appears to try to display the notification about updates a *little* too early when first booting, but it does start upon login.
[19:20] <arraybolt3> now to see if I can cause pileup
[19:21] <arraybolt3> woohoo, the session pileup bug is gone too!!!
[19:21] <arraybolt3> and you can even show the window without clicking the tray icon.
[19:22] <arraybolt3> So I'm going to label this a success and do some uploads.
[19:24] <arraybolt3> Collaborative development at its best - submit a PR that gets a PR submitted against it that you review and merge so that it can be merged into main :D
[19:42] <arraybolt3> patched lxqt-sudo uploaded
[19:51] <arraybolt3> Lubuntu Update 1.0.0~alpha1 now uploaded.
[19:51] <arraybolt3> it's probably going to depwait but I think the archive is supposed to autoretry those.
[19:51] <arraybolt3> (I made it so that it depended on an equal or greater version of lxqt-sudo as the one I had just uploaded)
[20:07] <RikMills> sometimes it takes its time to retry
[20:08] <RikMills> 'ubuntu-build lubuntu-update-notifier noble-proposed retry' is a one liner to do it
[20:10] <tsimonq2> Sorry, just got back from lunch, walking into another meeting.
[20:10] <tsimonq2> +1 on what RikMills said - thanks for your help here arraybolt3!!!!!!!!!!!!!!!!!!
[20:11] <arraybolt3> Happy to! Everything is pushed to Git and uploaded to the archive.
[20:11] <arraybolt3> NOTE: lubuntu-update-notifier's repo *is untouched.*
[20:12] <arraybolt3> The new packaging and code is in the lubuntu-update repo.
[20:12] <arraybolt3> lubuntu-uodate-notifier's package on the other hand has been clobbered.
[20:13] <tsimonq2> roger roger :)
[20:14] <tsimonq2> Looks like the lxqt-sudo binaries will be published and good in the next hour, I'd set like a sleep 3200 or something :P