 Could you help me figure out what's going on?
 I'll be at the office in about 10 minutes to start git bisecting
[00:03] <arraybolt3> Sure thing :)
[00:03] <arraybolt3> Also I just uploaded my Calamares fix to the archive :D
[00:04] <arraybolt3> (I made one change I'm not sure about with the build dependencies, but it still builds so I *think* it will work right, plus it's something lintian directly told me I should do and how to do.)
[00:05] <arraybolt3> Also upstream didn't like my coding style for the patch so we'll probably end up swapping it out later on down the road, but this upload fixed some other packaging issues so it was worth it.
[00:05] <arraybolt3> tsimonq2: So how would I start helping? What do I need to do?
[00:06] <arraybolt3> I have a perfectly primed VM ready to be destroyed however we need.
 Well, we just simply need to figure out *why* this darn thing keeps crashing.
 We could break out gdb, git bisect, or something. That being said, this is our #1 priority right now, because it's a regression in Backports.
 Even if it only takes one person, someone to bounce ideas off of would be great.
 Anyway, I just got to the office, I'll start reviewing
[00:09] <arraybolt3> kk
[00:13] <arraybolt3> "The X11 connection broke: Unsupported extension used (code 2)" is the error I get trying to launch lxqt-powermanagement manually.
[00:13] <arraybolt3> I get the feeling something went awry in our reverting of KWindowSystem things maybe?
[00:14] <tsimonq2> https://git.lubuntu.me/Lubuntu/lxqt-powermanagement-packaging/src/branch/backports/jammy/debian/patches/revert-kwindowsystem-port.patch
[00:14] <arraybolt3> Everything LXQt except lxqt-menu-data is migrated in Noble, lemme do a thing...
[00:14] <tsimonq2> https://github.com/lxqt/lxqt-powermanagement/commit/aca58172f611e2545c3cfcb8310725b3cf5fa715
[00:14] -ubottu:#lubuntu-devel- Commit aca5817 in lxqt/lxqt-powermanagement "Port deprecated KWindowSystem"
[00:14] <arraybolt3> I'mma do a Noble install and upgrade and see if powermanagement is crashy there too
[00:15] <tsimonq2> Sweet.
[00:15] <tsimonq2> Just remember to get everything, especially qterminal.
[00:15] <arraybolt3> +1
[00:15] <arraybolt3> hmm, your port seems rather minimal, so...
[00:16] <arraybolt3> what commit did that revert?
[00:16] <tsimonq2> Uh I just linked it :)
[00:16] <arraybolt3> lol sorry
[00:17] <tsimonq2> Respinning the daily to catch all the new packages.
[00:17] <arraybolt3> find_package(XCB REQUIRED COMPONENTS xcb-dpms xcb-screensaver)
[00:17] <arraybolt3> that's interesting, because...
[00:17] <tsimonq2> That can sometimes take up to an hour. It missed the migration of all the packages, by about an hour. :/
[00:17] <arraybolt3> https://bbs.archlinux.org/viewtopic.php?id=240025
[00:17] <arraybolt3> almost the exact same error, and it was dpms-related
[00:19] <arraybolt3> Upgrading Noble box...
[00:19] <tsimonq2> https://github.com/lxqt/lxqt-powermanagement/compare/1.3.0...1.4.0
[00:19] <tsimonq2> Starting a Git bisect on my VM.
[00:20] <arraybolt3> aha!
[00:20] <arraybolt3> found something that retrieves DPMS timeouts
[00:20] <arraybolt3> https://github.com/lxqt/lxqt-powermanagement/compare/1.3.0...1.4.0#diff-3e43746a2bbdfcc54fbccb46458ab37c1e4328a62fd82fc5adfb2218e9ad563c
[00:22] <arraybolt3> While you do that, I'm going to try reverting the DPMS-related commit and see what happens.
[00:23] <tsimonq2> We'll both probably end up with a conclusion at about the same time. :)
[00:24] <arraybolt3> heh, you're not wrong
[00:24] <arraybolt3> you probably have faster Internet too which will make things move forward sooner
[00:24] <arraybolt3> anyway if the bad commit turns out to be 74ec93212e614f53e5c9990c1ec5bd35c2bb5990 don't be surprised :P
[00:32] <arraybolt3> sbuilding patch
[00:32] <arraybolt3> (I just commented out everything DPMS-related rather than doing a full-scale commit revert since the commit looked a tad messy)
[00:37] <arraybolt3> Rebooting with hopefully fixed power manager...
[00:37] <arraybolt3> And no crashy :)
[00:37] <arraybolt3> tsimonq2: Fixed it, it is indeed the DPMS stuff.
[00:38] <tsimonq2> $ git bisect good
[00:38] <tsimonq2> 74ec93212e614f53e5c9990c1ec5bd35c2bb5990 is the first bad commit
[00:38] <arraybolt3> :P same time
[00:38] <arraybolt3> Now the question is, do we just barbarically patch that out, or do we figure out why DPMS isn't available and fix it?
[00:38] <tsimonq2> arraybolt3: Basically the same time. That's technical confirmation that we should just hard push this through I think ;)
[00:39] <tsimonq2> Barbarically patch it out.
[00:39] <arraybolt3> okeydokey
[00:39] <arraybolt3> want my patch?
[00:39] <tsimonq2> Please upload to Backports Staging with a "proper" version, I trust you. :)
[00:39] <tsimonq2> Oh and by the way...
[00:39] <arraybolt3> kk, one sec
[00:39] <arraybolt3> yeah?
[00:40] <tsimonq2> You can re-enable my power management UX patch, too. That wasn't the cause of it.
[00:40] <tsimonq2> (Not sure which iteration you're working with. :) )
[00:40] <tsimonq2> Anyway, thanks for the teamwork on this :D
[00:40] <arraybolt3> sure thing
[00:40] <arraybolt3> and I will re-enable the patch
[00:40] <tsimonq2> Thank you very much!
[00:41] <tsimonq2> If you find the time/it isn't too much of a hassle, please do push to the Git repo as well.
[00:44] <arraybolt3> gah, all I'm actually doing it turns out is a full-scale revert, so I'm just gonna full-scale revert and be happy
[00:44] <arraybolt3> it looked messy right up until I looked closer
[00:45] <tsimonq2> Kay, cool.
[00:48] <tsimonq2> Oh wow, the ISO is already done.
[00:49] <tsimonq2> WOW, that was like 20 minutes. IMPRESSIVE.
[00:49] <tsimonq2> Suspiciously impressive...
[00:51] <tsimonq2> Er... yeah. Three packages that migrated to release are not on the ISO yet...
[00:51] <tsimonq2> Let's see what the logs say, and what apt tries to tell me when I upgrade those.
[00:52] <arraybolt3> My Git skills stink sometimes...
[00:52] <tsimonq2> What happened? :P
[00:53] <arraybolt3> Oh, just forgot to add all the changes I wanted to commit and had to soft-reset.
[00:54] <arraybolt3> tsimonq2: I think you didn't push your changes to Git yet, so I'm wondering... do I just plow right over the top of your ppa0.3 upload (as in, no changelog entries, no nothing, just pick up from the head of backports/jammy and keep trucking)?
[00:55] <arraybolt3> it'll go straight from 0ubuntu1~ppa2 to 0ubuntu2~ppa1
[00:55] <arraybolt3> if not I have to do a messy import or you need to push some things
[00:56] <tsimonq2> arraybolt3: ubuntu2 should go to Noble, ubuntu2~ppa1 should go to Backports Staging.
[00:56] <arraybolt3> sooo... ok, need a bit more complexity then
[00:56] <tsimonq2> arraybolt3: Overwrite all you'd like.
[00:56] <tsimonq2> I'd say just make your commits where they are, and merge --ff / cherry-pick them around
[00:56] <arraybolt3> tsimonq2: I don't have any ubuntu2 code
[00:57] <tsimonq2> this *is* your ubuntu2 code :P
[00:57] <arraybolt3> ahhhhhh
[00:57] <arraybolt3> right, because...
[00:57] <arraybolt3> one sec
[00:57] <arraybolt3> OUCH
[00:57] <arraybolt3> houston, we have no leave menu at all on Noble
[00:57] <tsimonq2> yup also on the new daily no qterminal either
[00:57] <arraybolt3> but right, I need to patch out this stuff in Noble too, not just Jammy. Confirmed as of right now.
[00:58] <tsimonq2> Ctrl + Alt + T is *completely* broken and there is *no* working terminal on the current Noble daily. :P
[00:58] <arraybolt3> (since I forgot to finish my Noble check until just now)
[00:58] <arraybolt3> fun
[00:58] <arraybolt3> TTY to the rescue I guess
[00:58] <tsimonq2> And guess what qterminal is waiting on...
[00:58] <arraybolt3> lxqt-menu-data?
[00:58] <arraybolt3> no, that can't be right
[00:58] <arraybolt3> what then?
[00:58] <tsimonq2> A failing armhf apport test that's completely unrelated, and the retry is halfway down the 2500-item long armhf queue. :P
[00:59] <arraybolt3> ROFL
[00:59] <tsimonq2> We won't have a functional daily until the morning, unfortunately.
[00:59] <arraybolt3> So that's what happens when armhf decides to take an extended lunch break. Now we nkow.
[00:59] <tsimonq2> Yeeeeeeeeeeeeeeeeeeep.
[01:02] <arraybolt3> sigh. quilt is giving me way more of a hard time than it ought to.
[01:04] <arraybolt3> oh shoot I know why
[01:04] <arraybolt3> your UX patch is messing with my groove
[01:04] <tsimonq2> heh :)
[01:04] <tsimonq2> By the way, powermanagement works fine on Noble, so it's something to do with that library specifically.
[01:05] <tsimonq2> ...you got it, or do you want me to get it?
[01:06] <tsimonq2> whoops I was scrolling way up
[01:06] <tsimonq2> I thought you were asking me again if I wanted your patch, my bad XD
[01:06] <arraybolt3> for Unknown Reasons(TM) a simple-and-nice git diff patch is applying with fuzz when quilt gets to it
[01:07] <arraybolt3> oh wait. I know why
[01:07] <arraybolt3> because I'm too tired to realize that a git revert and a git diff aren't the same thing
[01:08] <tsimonq2> Oh no... look at how many other packages depend on that now...
[01:08] <tsimonq2> * lxqt-config [amd64 arm64 armhf ppc64el s390x]
[01:08] <tsimonq2> * lxqt-panel [amd64 arm64 armhf ppc64el s390x]
[01:08] <tsimonq2> * lxqt-powermanagement [amd64 arm64 armhf ppc64el s390x]
[01:09] <tsimonq2> We really should look at *where* that's implemented in lxqt-config and lxqt-panel.
[01:09] <tsimonq2> Perhaps their usage is more productive. I don't know yet, and that slightly scares me.
[01:10] <arraybolt3> depend on what?
[01:10] <tsimonq2> Anyway, the manifest is *wrong*. Everything LXQt is up-to-date in the ISO except for qterminal, to my knowledge.
[01:10] <arraybolt3> that one thing deep in the guts of the armhf queue
[01:10] <tsimonq2> Very good question. It's the source package that ships the DPMS package, and I just did a simple reverse-depends.
[01:11] <tsimonq2> Let me actually look at reverse depends *for that package*...
[01:11] <tsimonq2> Oh, okay, good. I was freaking out for nothinbg.
[01:11] <tsimonq2> LXQt Power Management is the only LXQt dep of that.
[01:11] <arraybolt3> YAY build is finally going
[01:11] <arraybolt3> took me like four tries before I figured it out
[01:12] <tsimonq2> And, because quite frankly I don't care about slightly spamming, here's the reverse-depends output:
[01:12] <tsimonq2> $ reverse-depends libxcb-dpms0
[01:12] <tsimonq2> Reverse-Depends
[01:12] <tsimonq2> [01:12] <tsimonq2> * cutefish-core [amd64 arm64 armhf ppc64el s390x]
[01:12] <tsimonq2> * libkf5screendpms8 [amd64 arm64 armhf ppc64el s390x]
[01:12] <tsimonq2> * libxcb-dpms0-dev
[01:12] <tsimonq2> * lxqt-powermanagement [amd64 arm64 armhf ppc64el s390x]
[01:12] <tsimonq2> Packages without architectures listed are reverse-dependencies in: amd64, arm64, armhf, i386, ppc64el, s390x
[01:12] <tsimonq2> Nice!
[01:12] <tsimonq2> Hmm, I wonder if reverse-depends supports riscv64 yet. Looking.
[01:14] <tsimonq2> Oh, okay. It does. Just weirdly not showing it. That's cool.
[01:14] <tsimonq2> Anyway, arraybolt3 keep me posted. :)
[01:14] <arraybolt3> Oh just fighting quilt again. Can't add a dep3 header to a patch unless it's the latest applied patch, which is a problem when you can't apply the patch because you have only the packaging and not the source code.
[01:14] <arraybolt3> So doing the regular fiddliness with pull-lp-source just to satisfy this one tool.
[01:15] <tsimonq2> Sounds like a great time.
[01:20] <arraybolt3> We really need a feature in quilt that lets me say `quilt --dep3 -e /path/to/file.patch` and does it, or I need to figure out how to do that.
[01:20] <arraybolt3> The way I'm doing things now is tedious, hard, and slow.
[01:21] <tsimonq2> Honestly, that seems totally possible.
[01:21] <tsimonq2> BRING OUT THE LIST!
[01:21] <arraybolt3> I guess we don't mess with patches a whole lot usually so this didn't used to be a pain point, but now it is.
[01:21] <tsimonq2> *thunder rolls in the background*
[01:21] <arraybolt3> here you go: https://notes.lubuntu.me/huOk59_iRSaAMZDl_my8bw
[01:21] <tsimonq2> Every time that's rhetorical, yet every time you seem to produce an even better list, actually proving my point... XD
[01:22] <arraybolt3> hehe
[01:25] <tsimonq2> Uh WAT, the armhf queue just went from 2500 to 399 in *one* refresh. Coooooool.
[01:25] <arraybolt3> Wow, nice
[01:26] <tsimonq2> And back up to 2300. I remember this.
[01:26] <arraybolt3> Finally, got a good upload.
[01:26] <arraybolt3> Oh well
[01:26] <tsimonq2> During the refresh stage, it *hard* refreshes, heh.
[01:26] <tsimonq2> Anyway, \o/
[01:26] <arraybolt3> new power manager going into the archive
[01:27] <arraybolt3> man am I thankful for the ability to type fast
[01:27] <arraybolt3> pretty much required for this job :P
[01:29] <tsimonq2> For sure :D
[01:29] <tsimonq2> Let me know if we run into anything else, otherwise I'm going to crank out some more stuff for $dayjob.
[01:29] <arraybolt3> kk, that should be fine
[01:29] <tsimonq2> I would be especially thankful for a revert for my recent cala-settings-ubuntu upload (just .2, not .1) and a fix :P
[01:30] <arraybolt3> heh, kk
[01:30] <tsimonq2> (In fact, it probably has to be fixed *in* Calamares.)
[01:30] <tsimonq2> Anyway, thanks again.
[01:30] <arraybolt3> Ah, I uploaded the fix in Calamares already.
[01:30] <arraybolt3> So revert should be easy.
[01:30] <arraybolt3> if you mean the encryption stuff
[01:31] <tsimonq2> Not talking about your recent fix to Calamares, but I am talking about the amd64 FTBFS for calamares-settings-ubuntu. :P
[01:31] <arraybolt3> ah
[01:33] <Eickmeyer> calamares-settings-ubuntu_24.04.2+reallysimonsfault.1
[01:33] <arraybolt3> We need an #ErichDidIt meme.
[01:33] <tsimonq2> XD
[01:34] <Eickmeyer> At which point I'd point to the ItsAlwaysSimonsFault meme
[01:35] <arraybolt3> We have a you-done-messed-up-aaron and a simons-fault, the loop has to be closed
[01:35] <Eickmeyer> It always goes back to #BlamePopey because that was first.
[01:39] <arraybolt3> Huh, TIL
[01:40] <arraybolt3> Uploaded the patch to backports-staging.
[01:41] <arraybolt3> Uhh... how do I use SSH with dput?
[01:41] <arraybolt3> I'm hitting the flakey FTP upload problem.
[01:41] <tsimonq2> Instead of dput ubuntu, do dput ssh-ubuntu. Instead of ppa, do ssh-ppa. You might have to manually throw your username in /etc/dput.cf.
[01:42] <arraybolt3> worked, thanks
[01:43] <tsimonq2> Of course :)
[01:44] <arraybolt3> All uploads done, all commits pushed, all tags pushed, and all brain cells fried.
[01:44] <tsimonq2> Nicely done :D
[01:44] <arraybolt3> Gonna need some practice before this gets fast, but I'm getting there.
[01:44] <tsimonq2> It always takes a little bit of practice. :)
[01:45] <tsimonq2> Let me know if you get to cala settings tonight, otherwise I'll tackle it $sometime tomorrow.
[01:46] <arraybolt3> kk
[03:29]  * tsimonq2 EOD o/
 working leave menu in noble. (re @lubuntu_bot: (irc) <arraybolt3> houston, we have no leave menu at all on Noble)
[12:23] <guiverc> qterminal won't start on this (noble) box; segfault.. same result on another noble box too  ...   Likely just temporary issue as I note "libegl1, libgl1, libglvnd0 & libglx0" are reported as obsolete; yet all upgrades applied currently available...
 Same. (re @lubuntu_bot: (irc) <guiverc> qterminal won't start on this (noble) box; segfault.. same result on another noble box too  ...   Likely just temporary issue as I note "libegl1, libgl1, libglvnd0 & libglx0" are reported as obsolete; yet all upgrades applied currently available...)
 qterminal hasn't migrated yet, once it does it'll work again on Noble
 I assumed that was it, the same thing happened in 1.3 and after updating it worked perfectly. (re @tsimonq2: qterminal hasn't migrated yet, once it does it'll work again on Noble)
 I queued another test which should hopefully let qterminal through
[17:38] <tsimonq2> https://autopkgtest.ubuntu.com/packages/a/apport/noble/armhf
[17:38] <tsimonq2> Seems like it could very much be a regression on the apport side of things.
[17:38] <tsimonq2> My request is a little far down on the list...
[17:38] <tsimonq2> apport {"requester": "tsimonq2", "submit-time": "2023-11-15 14:23:22", "triggers": ["qterminal/1.4.0-0ubuntu1"]}
 ask Utkarsh.  They said requalification is needed (re @lubuntu_bot: (irc) <tsimonq2> @kc2bez, @teward001: Did we need to seek *re*-qualification for LTS last time around, or were we just grandfathered in?)
 (evidence: you don't read your emails)
 bruh evidence you don't read yours (re @teward001: (evidence: you don't read your emails))
 evidence: you still owe me for another year of email (re @tsimonq2: bruh evidence you don't read yours)
 *sends invoice*
 i have 2,356 unread messages right now
 :O
[18:08]  * tsimonq2 looks over at my inbox with nearly 47,000 unread emails
 @tsimonq2 on November 9, 2023, Utkarsh Gupta emailed ubuntu-release@lists and ubuntu-flavors@list stating "touch base on flavor participation for 24.04".  Stating this as well:
 "Also, given this is an LTS release, so if you’d like to participate as
 an LTS, you will need to go through the LTS qualification process with
 the Technical Board. Please contact technical-board@lists.ubuntu.com
 to kick off this process."
 which overrides anything else because TB requirements are hard
 my email was first, and I talked to vorlon, and we did lots of backchannel coordination on that, so :) (re @teward001: @tsimonq2 on November 9, 2023, Utkarsh Gupta emailed ubuntu-release@lists and ubuntu-flavors@list stating "touch base on flavor participation for 24.04".  Stating this as well:)
 if you disagree with that statement
 I don't disagree at all
 then talk to the TB and show me evidence
 what I'm saying is I'm in the loop
 because 'back channel coordination' that isn't on Council's radar irks me
 either *way* we still owe a reply there
 for *paper trail*
 so
 *pushes @tsimonq2 out the airlock*
 nah this was in a personal capacity not with my Lubuntu hat on :P
 coordination was regarding announcements/Discourse posts
 then we are still boud on this
 all the Lubuntu stuff I made public
 bound on this* for *action to do*
 so yes we still need an email for the TB
 I believe you volunteered for that :P
 so basically we just circled back to the whole fact that i was right in the first place
 my only slight objection would be re-arranging me and kc2bez but that's meh trivial whatever
 and you just wated my time
 no you were wrong in the first place :P
 so I corrected you :P
 (i woke up grumpy today, arguing me on this case is likely to go poorly for you)
 (and everyone)
 but yes we both just bikeshedded for like 5 mins
 /me lets teward continue on
 *goes to go punch something because of aggression*
[18:57] <arraybolt3> *sneaks up and steals teward's coffee*
[18:59]  * lubot [matrix] <kc2bez> sends coffees all around.
[19:05] <arraybolt3> tsimonq2: Didn't do the revert on cala-settings last night, had too much to do here. I'll do it first once I'm up and working.
[19:06] <tsimonq2> arraybolt3: No worries, thanks for taking the lead on that.
[19:06] <arraybolt3> After that I'd like to tackle our wallpaper situation (scaling, numbat placeholder image) and then maybe work some more on the network editor.
[19:06] <tsimonq2> Sweet!
[19:06] <tsimonq2> Good stuff.
[19:07] <tsimonq2> arraybolt3: Did you catch my PSA to ubuntu-devel@l.u.c?
[19:07] <arraybolt3> btw pick a placeholder now or I'm inserting a CC-BY numbat picture from Wikipedia blown up with Upscayl :D
[19:07] <arraybolt3> Got the PSA, yes, had to switch to dput-ssh last night.
[19:08] <arraybolt3> Thankfully my system username and Launchpad username are identical
[19:08] <tsimonq2> Eickmeyer: First there was dput, then there was dput-ng, now there is dput-ssh. XD ^^^
[19:08] <tsimonq2> Just kidding, hehe :)
[19:08] <arraybolt3> so it was a very easy switch
[19:08] <tsimonq2> Nice! Mine too :)
[19:08] <arraybolt3> lol, you know what I meant
[19:08] <Eickmeyer> tsimonq2: systemd-dputd
[19:09] <tsimonq2> Eickmeyer: OHHHHHHHHH NOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO
[19:09] <arraybolt3> *screams into the void*
[19:09]  * Eickmeyer knew that would trigger
[19:09] <tsimonq2> LMFAO
[19:10] <arraybolt3> "Upon boot up, all work-in-progress packages are uploaded to the Archive via the slowest connection available. The system will not boot until every package is successfully uploaded and accepted."
[19:10] <arraybolt3> Using FTP.
[19:11] <arraybolt3> sigh, I was worried no one would get it
[19:11]  * Eickmeyer what have I done
 "Can we upload via telnet?"
[19:13] <Eickmeyer> tl;dr: yes.
 I might actually do that for April Fools. Provide a telnet upload interface. :P
[19:13] <arraybolt3> Oh grief XD
 "Special Announcement: upload to Ubuntu via telnet, the newest kid on the block!"
[19:20] <arraybolt3> Earlier we were talking about reintroducing a retro wallpaper, did we get any further with that idea?
[19:20] <arraybolt3> The first one we ever used seemed good if only it wasn't 4:3.
[19:21] <arraybolt3> Should I perhaps try to remake it in 16:9?
[20:24] <wxl> @kc2bez: oh?
[20:25] <tsimonq2> wxl: +1 from people I've talked to IRL as well :)
[20:25] <tsimonq2> wxl: Very good stuff. Thanks again for your help!
[20:26] <tsimonq2> arraybolt3: I mean, maybe. We do need *something* as a generic placeholder, I only gave the idea of a classic one to troll, tbh. :P
[20:26] <wxl> i'm kind of shocked overall XD
[20:27]  * tsimonq2 bows down to the new Lubuntu Art Team Leader, wxl 
[20:27] <wxl> nonononono
[20:27] <tsimonq2> XD
 wxl: 100÷ agree with tsimonq2. It turned out very good from my viewpoint too.
 ZD
 XD
 Even
[20:28] <wxl> i don't even know what i don't know when it comes to graphic design, so
 Maybe ignorance is vliss
 Bliss
[20:29]  * wxl hands kc2bez a better keyboard
 Bows in thanks
[20:30]  * tsimonq2 hands kc2bez a stronger coffee, making the new keyboard just as bad XD
 XD
[21:06] <tsimonq2> Kay, probably stepping away to do some $dayjob stuff for a bit.
[21:06] <tsimonq2> arraybolt3: Let me know if you run into trouble, if you happen to have the time today. :)
[21:10] <teward> arraybolt3: DM me your address you use on notes again?
[21:12] <tsimonq2> plasma-distro-update-upgrade-notifier-application-thing@buntu'studia'h.com
[21:12] <tsimonq2> Eickmeyer: XD
[21:13]  * tsimonq2 imagines that arraybolt3 has a slight Southern drawl and will probably read that perfectly :P
[22:05] <arraybolt3> teward: Same one I use everywhere.
[22:50] <arraybolt3> Alright, I am FINALLY here.
[22:50] <arraybolt3> (Slight curveball in life slowed me down.)
[22:54] <arraybolt3> tsimonq2: Where on earth is the calamares-settings-ubuntu repo on LP?
[22:54] <arraybolt3> My Launchpad-fu is failing me badly.
[22:57] <arraybolt3> grief, that took forever. It's at https://code.launchpad.net/~ubuntu-qt-code/+git/calamares-settings-ubuntu.
[22:58] <arraybolt3> oh funny, so you pushed to Lubuntu's mirror and not to LP.
[22:58] <arraybolt3> Syncing...
[22:59] <wxl> is there some way to make that easier to find on gitea?
[22:59] <wxl> i seem to remember phab used to show clone links to the mirror source when a mirror was used
 Doesn't the mirror point to lp
 There should be a link on the gitea repo
 Upper leftish area from my memory
[23:00] <wxl> nope
 Harumpf
[23:01] <wxl> like i said i think phab used to point to the mirror
[23:01] <wxl> ooh i'll link it to the website value
 Is that repo actually mirrored?
[23:01] <wxl> good question
[23:02] <wxl> yes but it's a mirror to github actually XD
 Well, that isn't what we were shooting for.
[23:02] <arraybolt3> The mirror isn't a real mirror
 Weird
[23:03] <arraybolt3> It says it's a mirror of the LP repo but it's a LIE :P
[23:03] <arraybolt3> anyways I just synced LP with Gitea, reverted the failed fix and uploaded it to the archive.
 It Should be a mirror of LP though
[23:03] <arraybolt3> yeah
[23:03] <arraybolt3> well for now I'll just tag and push in both places, then I'll see if I can push some buttons.
[23:04] <arraybolt3> If it's too entangled with GitHub though I may have to bail out and let someone more experienced fix it.
[23:04] <wxl> um
 Just push to lp
[23:04] <wxl> github doesn't seem like it's set up as a mirror
[23:04] <arraybolt3> kc2bez: done
[23:04] <wxl> it says it is
[23:05] <arraybolt3> kc2bez: so I should *not* push to Gitea too?
[23:05] <wxl> unless i'm missing something
 We should change the mirroring on gitea to pull from lp
[23:06] <arraybolt3> Gitea is set to *push* to GitHub, and it should *pull* from LP, right?
[23:06] <arraybolt3> then theoretically we push to LP, it pulls, then pushes to GH and we're happy
 Yes
 Seems like the best approach
[23:06] <arraybolt3> hrm, does it let you have both a push *and* a pull mirror?
[23:07] <wxl> only one way to find out
[23:07] <arraybolt3> I see a big "Add Push Mirror" button...
[23:07] <arraybolt3> wxl: and that's to let someone else break it and not you, if you're me :P
[23:07]  * arraybolt3 ducks
[23:07] <arraybolt3> in all seriousness I'm fine if I'm the one at fault if it breaks but I would like to try to keep that from happening
[23:08] <arraybolt3> "❗❗ NOTE: You can only set up pull mirroring for repos that don't exist yet on your instance. Once the repo is created, you can't convert it into a pull mirror anymore. ❗❗"
[23:08] <arraybolt3> welp
[23:08] <arraybolt3> https://docs.gitea.com/next/usage/repo-mirror
[23:08] <arraybolt3> so no, we can't make it a mirror now
[23:08] <arraybolt3> unless we want to nuke the repo and remake it
[23:08] <wxl> seed is set up as a pull only mirror
[23:08] <arraybolt3> probably because it was set up that way from the get go?
[23:09] <wxl> omg who the heck set this all up
[23:09] <wxl> SIMONSFAULT
[23:09] <arraybolt3> teward :P
[23:10] <wxl> default settings is a push to github mirror too
[23:10] <arraybolt3> actually I don't know hwich of the two of them
[23:10] <arraybolt3> but I think teward did some of the initial setup, could be wrong
[23:10] <wxl> i imagine teward set up the infrastructure. i'm sure of it, in fact. but configuring how it's used, i'm sure that's all simonsfault
[23:10] <wxl> i mean it usually is
[23:10] <wxl> XD
[23:11] <arraybolt3> well, we have two options:
[23:11] <arraybolt3> 1. I can push my changes to Gitea too and we deal with this some other time.
[23:11] <arraybolt3> 2. I can nuke the cala-settings-ubuntu repo on Gitea and recreate it as an LP mirror.
[23:11] <arraybolt3> Option 2 should be *reasonably* safe since I have all commits *and* tags pushed to LP.
[23:11] <wxl> i say do 1 and make simon fix 2 :)
[23:12] <arraybolt3> kc2bez: ^ sound like a good idea? (just making sure I have approval from everyone here before moving forward)
[23:12] <arraybolt3> (and yes the ^ is pointing at wxl's idea, not at my "I'll nuke it" idea :P)
 I thought I set it up lol
[23:13] <wxl> ahhhhhh ahahahah
 I am good with 2
 That was the way I thought it worked unless someone else changed it.
 bruh
 cala-settings-ubuntu is the current one
[23:14] <wxl> that could be considered a bit obvious, yes
 Has anyone tried pull-lp-source *or* apt source, I really thought I updated the VCS :P
 And yes this one was definitely 100% me btw
[23:15] <wxl> i knew it!
[23:17] <arraybolt3> tsimonq2: You pushed to one VCS, there were two that needed updated and you pushed to the secondary one :P
[23:17] <arraybolt3> I have the "correct" Git history on my laptop and on LP, and we're discussing what Gitea's fate is now
 I mean, usually it's me. Unless git blame says arraybolt3. In which case I just say "well, Aaron done did 'er this time" :P
 Keep Gitea, @Eickmeyer doesn't GAF anymore about Cala (at least this release... 😈)
[23:18] <arraybolt3> Currently we have three Council members and an emeritus here, I don't know what to do, wxl has one idea, kc2bez has another idea, and you've not chipped it :P
[23:18] <arraybolt3> *in, not it
 I just did, as wxl would always repeat ad nauseum, patience XD
[23:18] <arraybolt3> right :P You typed too fast
[23:18] <arraybolt3> Or I typed too slow
[23:18] <arraybolt3>  /s
 *nauseam
[23:20] <arraybolt3> so anyway. What should I do? Push to Gitea and let someone else fix it, or nuke the Gitea repo and remake it as a pull mirror?
[23:21] <arraybolt3> tsimonq2: well this is fun :) I reverted your failed FTBFS fix that FTBFS everywhere, and the revert now also FTBFS everywhere
[23:21] <arraybolt3> so now what?!
 I'll send you creds over Matrix for push mirroring, you can force push the correct Git history over the Gitea copy if it's currently wrong (and you're sure and you pinky promise you'll fix it if you break it, meaning, keep some original repo copies lying around), then just make sure mirroring for GH and maybe LP is set up
[23:21] <arraybolt3> "Unknown CMake command "set_package_properties"."
[23:22] <arraybolt3> tsimonq2: no force push will be needed fwiw, the repos got out of sync but only in one directoin
[23:22] <arraybolt3> so LP fell behind Gitea, I updated LP with Gitea and then did work and pushed to LP, so now a normal push to Gitea will put them in sync
 I sent the creds over Matrix
 Sorry for the bad advice if I gave it. I had no idea it was that buggered.
 Yeah I honestly don't know on that one...
 I think we're all on the same page now, thanks for your help either way :) (re @kc2bez: Sorry for the bad advice if I gave it. I had no idea it was that buggered.)
 Of course.
[23:25] <arraybolt3> Final confirmation: * Make dead-sure LP is correct * Nuke Gitea repo * Re-create it to pull from LP * Set up push mirroring to GitHub
[23:26] <arraybolt3> If that's 👍 I'll do it.
 Nope
 Gitea is the source, GH and LP are the mirrors
 Then you'd have it right :)
[23:27] <arraybolt3> ah kk
[23:28] <arraybolt3> then I don't have to nuke anything and just set one-way mirroring to LP from Gitea
[23:28] <arraybolt3> tsimonq2: the creds you sent are the LP ones right?
[23:28] <arraybolt3> or are those GH?
 GH
 LP is the same password but that could potentially have its own API key or something
[23:29] <arraybolt3> ah kk
 ll
 mm
[23:30] <arraybolt3> nn?
 and it sends a confirmation email to me (whoops FIXME) so if you happen to want to log into LP, jlmk I'll hook you up
 I'm just continuing with the alphabet ;)
[23:31] <arraybolt3> I just need to know how on earth to set up push mirroring to LP :P that's the only missing link
[23:31] <arraybolt3> it sounds like you probably can do that so I think I'd best stay out of it and let you do that since you're right here and know what needs to be done
 Try an HTTPS push mirror with the existing creds to start
[23:31] <arraybolt3> I pushed my changes to Gitea (no force-push needed)
 meh sure that works too ;)
[23:31] <arraybolt3> ok
 and cool
[23:32] <arraybolt3> well I'll try it and we'll see what happens
 one little Best Practice thing I'll share with you is, you can explicitly set authors for Git commits, and when I'm importing uploads from the archive, I'll just grab that author field right from the changelog
[23:33] <arraybolt3> Push mirror added.
[23:33] <arraybolt3> tsimonq2: Handy!
 Thanks!
 Does it work/did you test it?
[23:33] <arraybolt3> Not sure yet, lemme click Synchronize...
[23:33] <arraybolt3> "check back in a minute" says it
[23:33] <arraybolt3> so alrighty then
[23:33] <arraybolt3> Authorization failed.
[23:34] <arraybolt3> oh manage access tokens, that might work
 Also, since you have creds now, can you help me figure out what is pushing what I assume to be the LP copy of the manual to GitHub? Maybe Phab? Some times of the day the most recent commit is old, other times of the day it's brand new. Super weird functionality: https://github.com/lubuntu-team/manual
[23:34] <arraybolt3> sure, one moment
 thanks :)
 CC @lynorian ^^^
[23:36] <arraybolt3> tsimonq2: To me that sounds like Gitea is pushing I would guess, it has a "sync every 8 hours" or something in there
[23:37] <arraybolt3> https://i.imgur.com/FqobMdj.png
 I think phab (re @tsimonq2: Also, since you have creds now, can you help me figure out what is pushing what I assume to be the LP copy of the manual to GitHub? Maybe Phab? Some times of the day the most recent commit is old, other times of the day it's brand new. Super weird functionality: https://github.com/lubuntu-team/manual)
[23:38] <arraybolt3> tsimonq2: see matrix DM
 Okay lol yup it was Phab
[23:41] <arraybolt3> tsimonq2: Push mirror works!
[23:42] <arraybolt3> So now Lubuntu Gitea is the SSOT for calamares-settings-ubuntu and we can finally forget how to get to that horribly complex and obscure LP URL
[23:43] <arraybolt3> (j/k but seriously we should save that in the README so we don't have an aneurysm looking for it)
[23:43] <arraybolt3> wait...
[23:43] <arraybolt3> lol
[23:43] <arraybolt3> the link is literally in the description of the Gitea repo
[23:43] <arraybolt3> and for some reason I literally didn't see it
[23:44] <arraybolt3> so. Now that I've thoroughly embarrassed myself, now I'll go and figure out how to fix the FTBFS hopefully.
 Lmfao nice, thanks in advance for your FTBFS help!