[00:06] <guiverc> adding a .xscreensaver file to a 22.10 system APPEARS (to me thus far) to allow xscreensaver to open;  it can't be blank (ie. `touch` won't help)  but even adding a debian .xscreensaver causes it to open  (ie. any ~valid file)
[00:07] <arraybolt3> That's weird. It didn't used to require that, did it?
[00:09] <guiverc> we've got the xscreensaver issue on the tracker (I assume in release notes too, sorry i forget) ... (why I was trying to go on discourse)  .. nah I don't think it did but I can't be certain
[00:09] <kc2bez[m]> guiverc: Gah! I think I know what is going on
[00:09]  * arraybolt3 was thinking of attempting a git bisect, but it sounds like kc2bez has it covered
[00:12] <guiverc> issue didn't get on release notes; only in the 22.10 tracker
[00:13] <kc2bez[m]> https://github.com/lubuntu-team/lubuntu-default-settings/blob/ubuntu/kinetic/src/usr/lib/X11/app-defaults/XScreenSaver
[00:14] <kc2bez[m]> Sounds like we need to remove that ^
 Lubuntu website question. 22.04 shows as the NEW version on the front page. Should that be updated or is the LTS supposed to be featured?
[00:17] <guiverc> I'm not on kinetic any longer here, can't look what I have locally..  My primary focus is doc/workaround for 22.10 users we can documented on discourse; or can a SRU attempt to correct issue?
[00:17] <arraybolt3[m]> @franksmcb: What website are you visiting?
[00:17] <arraybolt3[m]> Lubuntu.me is the official site.
[00:17] <kc2bez[m]> Good question, we should update it
 Lubuntu.me
[00:17] <arraybolt3[m]> Oh on the front page. Right, that's outdated on our end. The Downloads page will have 22.10 at the top.
 I’m like a calendar, right once a year.
[00:18] <arraybolt3[m]> @franksmcb: Thanks!
[00:20] <guiverc> :)
[00:22] <guiverc> I also note a jammy daily; thanks tsimonq2 
[00:38] <kc2bez[m]> WordPress and I are not friends I guess. I can't seem to edit the main page.
[02:16] <teward> *burps*
[02:16] <teward> the git site is up
[02:16]  * arraybolt3 throws an angry python at teward's server
[02:16] <teward> *noms the python*
[02:16] <teward> *was hungry*
[02:16]  * arraybolt3 gets tangled up in said python and dies
[02:17] <arraybolt3> OK I guess then it's back to migration work. Thank you!
[02:45] <teward> kc2bez[m]: need help with the site?
[02:45] <teward> or is it busted
 "Dan Simmons: need help with..." <- Yeah, the editor wouldn't launch. I got logged into the dashboard but couldn't use Elementor. 
[09:22] <matkoniecz> is breakage of Discourse forum something to report here or on #lubuntu ?
[09:42] <matkoniecz> per https://lists.ubuntu.com/archives/lubuntu-users/2022-October/012682.html it is fully broken in general
[13:34] <tsimonq2> Good morning 
[13:34] <kc2bez[m]> Sup
[13:34] <tsimonq2> Discourse broken it seems?
[13:35] <kc2bez[m]> Yes, needs teward love sprinkled on it.
[13:36] <tsimonq2> Sounds good
[13:38] <kc2bez[m]> Simon Quigley: I'm not sure if you read through the screensaver issues or not. It looks like we need to drop our customization stuff possibly.
[13:39] <tsimonq2> kc2bez[m]: I did read through it but only partially understood: what is the root bug we're chasing?
[13:41] <kc2bez[m]> The application crashes making it impossible to adjust the settings.
[13:41] <tsimonq2> Oh, wow... did the XDG paths change maybe?
[13:43] <kc2bez[m]> I think XscreenSaver updated and there may be an incompatibility with our config. 
[13:44] <kc2bez[m]> https://bugs.launchpad.net/ubuntu/+source/xscreensaver/+bug/1989163
[13:44] -ubot93:#lubuntu-devel- Launchpad bug 1989163 in xscreensaver (Ubuntu) "Unable to run screensaver when selected from menu" [Undecided, Confirmed]
[16:38] <arraybolt3[m]> o/
[16:38] <arraybolt3[m]> Alright, so now it's time to finish the migration work. Sheesh, I hate $PERSONAL_LIFE's insanity sometimes.
[17:23] <arraybolt3[m]> Simon Quigley: Alright, someone tell me what I'm doing wrong here. I'm fighting with Phabricator's Conduit API. I'm trying to pass a JSON blob that looks like this:... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/0ed43500f1976ce32ac3acbc18131bd0d1d97600>)
[17:24] <arraybolt3[m]> If I could make a JSON blob as a string and somehow pass that, I bet it would work.
[17:30] <arraybolt3[m]> But for some reason it wants form-encoded data (whatever that means, I'm sure it means something but I sure don't know), so it won't take a JSON string as a data parameter, and if I try to pass a JSON string as a json parameter, it tells me that sending a JSON-encoded body isn't supported.
[17:30] <arraybolt3[m]> (╯°□°）╯︵ ┻━┻
[17:53] <arraybolt3[m]> I just don't get it. If I do all of the dictionary building in a variable and the json.dumps() the variable to look at the result, it comes out looking like exactly the format the web console is telling me to use, so Idk what it's grumpy about. I find it severely unlikely I've found a flaw in Python Requests, but I'm starting to think it may be quicker if I just use curl to short-circuit the process since there's an example for
[17:53] <arraybolt3[m]> how to do exactly what I'm trying to do using curl directly in the web console.
[17:57] <arraybolt3[m]> aHA! I am victorious! Alright, so, note to self, Phabricator outputs JSON, it does not like taking JSON. Format your dictionary elements like you were putting them in data parameters of curl, and it works.
[18:39] <arraybolt3[m]> s/severely/extremely/
[18:39] <arraybolt3[m]> teward: Have we already snapshotted Gitea? I'm just about done writing the Phabricator exporter, and then will be writing the Gitea importer. I find it highly unlikely that anything will go wrong since I'm not going to overwrite anything that already exists, but better safe than sorry.
[18:43] <teward> it's been taking too long so i'm going to copy it from the lxd infra box to my local system so give me a bit
[18:43] <teward> it's transferring a copy now but isn't the fastest 
[18:43] <arraybolt3> No prob. I won't do any write operations until I have a thumbs-up from you.
[18:57] <kc2bez[m]> Simon Quigley: I think this reddit support request is good now. https://www.reddit.com/r/Lubuntu/comments/y9kbc3/lxqt_panels_custom_command_widget_missing/
 "I think XscreenSaver updated and..." <- I say fix the compatibility issue instead of throwing the baby out with the bathwater :)
 "aHA! I am victorious! Alright..." <- Thanks for sticking through that :)
 "Simon Quigley: I think this..." <- Thank you very much! Well done :)
[19:14] <kc2bez[m]> tsimonq2: That is fair.
[19:15] <tsimonq2> BRING OUT THE LIST!
[19:15] <tsimonq2> roaring in the distance
[19:16] <arraybolt3[m]> tsimonq2: Can I just say I really wish the API docs hadn't spent so much time telling me how to use JSON as input when it turned out that if you're not using their special client, you don't use JSON?!?
[19:16] <arraybolt3[m]> tsimonq2: ```... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/8c3d95c5e63dbdd12bbe28d25e3500e57fea0ca1>)
[19:16] <kc2bez[m]> I am not sure we need/want our customizations though. The dialog has changed. It needs some testing.
[19:16] <arraybolt3[m]> > <@tsimonq2:linuxdelta.com> BRING OUT THE LIST!... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/5d6dc0c54a22f45197a5ed68811d201798c503f8>)
[19:16] <kc2bez[m]> Sorry, that was a reply
[19:16] <tsimonq2> arraybolt3[m]: Let's be fair here... Phab has been deprecated for a bit now and will show more signs of bitrot the more we use it :)
[19:17] <arraybolt3[m]> tsimonq2: Fair enough. Glad we're about to be done with it.
[19:17] <arraybolt3[m]>  * ```... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/6bc727254da8e5ca314200df3f73ecab3b0d09a3>)
[19:17] <tsimonq2> > <@arraybolt3:matrix.org> ```... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/2f0c23dcaae92a7b85c706713fcf7ee6e4c82324>)
[19:17] <arraybolt3[m]> (Changed the list a few times, re-review it)
[19:17] <tsimonq2> kc2bez[m]: Good to look at, right about now in the cycle :) let's do it 
[19:18] <tsimonq2> Channel topic done?
[19:18]  * arraybolt3[m] points at channel topic, it no longer says Kinetic, it will need changed one more time once LL is named
[19:18] <arraybolt3[m]> So I guess not really done...
[19:18] <tsimonq2> Thanks for the clarification :)
[19:19] <arraybolt3[m]>  * ```... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/28cea51c7490110bd2db482f4dc2cb8e8b490335>)
[19:19] <arraybolt3[m]> Alright, another list update.
[19:19]  * arraybolt3[m] slaps this onto CodiMD so we can all see and edit
[19:19] <kc2bez[m]> arraybolt3[m]: Thomas has op powers now
[19:19] <arraybolt3[m]> Nice 👍️
[19:22] <arraybolt3[m]> Alright what does everyone think of this? https://notes.lubuntu.me/huOk59_iRSaAMZDl_my8bw
[19:23] <arraybolt3[m]> That way we can add, move, reprioritize, whatever. I prioritized it according to what I think is right, but obviously it might not be all correct yet.
[19:23] <tsimonq2> Will look when I'm back at my computer. I've been running errands
[19:32] <krytarik> Btw, you'll be delighted to hear that Gitea is fully supported by ubot93 wrt issue, pull request, and commit snarfing - as opposed to Phab previously.
[19:32] <arraybolt3[m]> krytarik: \o/
[19:35] <arraybolt3[m]> Oh also somewhere around here I have a running bug list of things that need taken care of at some point, I think it's on my Chromebook which I don't have near me right now, but I should also upload that and present it for destruction.
[19:45] <tsimonq2> arraybolt3: re: bug 1989203 - I subscribed ~ubuntu-sponsors in case I don
[19:45] -ubot93:#lubuntu-devel- Bug 1989203 in manuskript (Ubuntu Kinetic) "Manuskript crashes on start" [High, Confirmed] https://launchpad.net/bugs/1989203
[19:46] <tsimonq2> * I don't get to it
[19:46] <arraybolt3[m]> Simon Quigley: Thanks, I was just thinking of asking about that.
[19:46] <tsimonq2> you get a 6th sense for those kind of things eventually ;)
[19:50] <tsimonq2> Another thing to mention...
[19:50] <tsimonq2> Does anyone have a laptop with an Ethernet port? Try connecting to WiFi and plugging in the ethernet cord
[19:50]  * arraybolt3[m] has multiple laptops like that
[19:50] <arraybolt3[m]> One of them is even free for testing at the moment.
[19:50] <tsimonq2> The ethernet connection doesn't even come up for me. `ip addr` to test
[19:51] <arraybolt3[m]> Jammy? Kinetic?
[19:51] <tsimonq2> Kinetic
[19:52] <arraybolt3[m]> K, guess that will be the next test once I'm finished fighting the Artificial Perpetually-grumpy Intelligence... er. API.
[19:53] <kc2bez[m]> > <@tsimonq2:linuxdelta.com> Another thing to mention...
[19:53] <kc2bez[m]> > 
[19:53] <kc2bez[m]> > Does anyone have a laptop with an Ethernet port? Try connecting to WiFi and plugging in the ethernet cord
[19:53] <kc2bez[m]> I can test that tonight.
[19:53] <tsimonq2> kc2bez[m]: Sounds good
[19:55] <tsimonq2> The manual workaround I have so far is to, in this order:
[19:55] <arraybolt3[m]> To me that sounds like either a severe Network Manager bug or a hardware problem.
[19:55] <tsimonq2>  1. Disable WiFi via nm-tray
[19:55] <tsimonq2>  2. Run `sudo dhclient -r NEW_NAME_FOR_eth0` to *release* the DHCP client process on that interface
[19:55] <tsimonq2>  3. Run `sudo dhclient NEW_NAME_FOR_eth0` to restart the DHCP client process
[19:56] <arraybolt3[m]> Also how old is your laptop? Should I be doing this on my ancient Elitebook8570p, or should I boot my KFocus with a live ISO?
[19:56] <arraybolt3[m]> Both have an Ethernet port.
[19:57] <tsimonq2> I've seen other reports in the mist, if it is a hardware problem I'd be curious to see "of what nature", if it's a kernel problem, we're screwed, and if it's nm territory, we need to see if we're the only flavor with this problem
[19:57] <tsimonq2> It's a Thinkpad T480s
[19:57] <kc2bez[m]> There was a recent (today?) kernel update addressing WiFi issues.
[19:58] <kc2bez[m]> For 5.19
[19:58] <tsimonq2> ...oh?
[19:58] <tsimonq2> $ uname -r
[19:58] <tsimonq2> 5.19.0-23-generic
[19:58] <kc2bez[m]> https://9to5linux.com/ubuntu-22-10-gets-first-kernel-security-update-to-address-recent-wi-fi-stack-vulnerabilities
[19:59] <arraybolt3[m]> tsimonq2: Heh, my systems hit on either side of that one's age. One is a 3rd Gen Core i5, the other 11th Gen, yours is 7th Gen... I guess I'll test both and see what happens.
[19:59] <arraybolt3[m]> *7th or 8th gen
[20:00] <tsimonq2> I shouldn't patch the kernel myself... I shouldn't patch the kernel myself... every time I say that it becomes less convincing :P
[20:00] <arraybolt3[m]> tsimonq2: Then livepatch the kernel yourself?
[20:01] <arraybolt3[m]> I don't know all the details of how using Linux's livepatching features works, but that might actually work.
[20:01] <tsimonq2> Well, one simple way to see if it's a local or a real issue would be to see if anyone else can reproduce it
[20:01] <arraybolt3[m]> If you want to make a patch for just your own machine.
[20:01] <arraybolt3[m]> Simon Quigley: Another thing you might try is falling back to the normal kernel - it just dawns on me you use the mainline one.
[20:02] <tsimonq2> tsimonq2: ( https://www.scientificamerican.com/article/the-universe-is-not-locally-real-and-the-physics-nobel-prize-winners-proved-it/ )
[20:02] <tsimonq2> arraybolt3[m]: I switched back after hearing about the LED screen stuff
[20:02] <tsimonq2> Just for the time being, heh
[20:02] <arraybolt3[m]> Ah.
[20:02] <arraybolt3[m]> I think that was actually in 5.19, and was fixed? Don't remember for sure.
[20:03] <arraybolt3[m]> Might've been 5.18
[20:04] <tsimonq2> I dunno, I saw the headline and panic-switched back :P
[20:05] <tsimonq2> I do still use a LUKS + btrfs setup though
[20:05] <arraybolt3[m]> It was 5.19.12, I believe? it was fixed in 5.19.13.
[20:05] <arraybolt3[m]> https://arstechnica.com/gadgets/2022/10/linux-5-19-2-kernel-can-flicker-and-damage-screens-on-some-intel-gpu-laptops/
[20:07] <tsimonq2> ¯\_(ツ)_/¯ I've been seriously considering switching back
[20:07] <tsimonq2> Anyway, here's the perspective I take on this...
[20:08] <tsimonq2> If it's only my issue, I want to take the time to see why the issue is caused, to perhaps reveal an underlying problem
 "I do still use a LUKS + btrfs..." <- Rebel.
[20:20] <tsimonq2> If someone else can reproduce it, and it's a real bug, we can definitely consider patching it for everyone
 "Rebel." <- ikr heh
[20:24] <tsimonq2> Well, maybe I should just grab the mainline kernel, hm :P
[20:24] <arraybolt3[m]> If it starts working right with the mainline kernel, then you get to bisect it!
[20:25] <tsimonq2> https://thumbs.gfycat.com/AbleMelodicHapuka-size_restricted.gif
[20:35] <tsimonq2> Followup on that issue...... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/5c7168bdea2578171085762ee7ad64022ce2a20c>)
[20:35] <tsimonq2> s/aquire/acquire/
[20:36] <arraybolt3[m]> nm regression, bet you.
[20:36] <tsimonq2> Also now my snaps won't load lol
[20:36] <tsimonq2>  XPCOMGlueLoad error for file /snap/firefox/1959/usr/lib/firefox/libmozgtk.so:
[20:36] <tsimonq2> /snap/firefox/1959/gnome-platform/usr/lib/x86_64-linux-gnu/libgdk-3.so.0: undefined symbol: XIFreeDeviceInfo
[20:36] <tsimonq2> Couldn't load XPCOM.
[20:36]  * arraybolt3[m] quotes the bit about mainline kernels being unsupported, guess now we know it's true!
[20:37] <tsimonq2> hahahahaha
[20:37] <tsimonq2> let me see if I can get it to work, and report back on my steps if I do
[20:37] <arraybolt3[m]> Sounds good. Might also be interesting to see how Debian LXQt behaves (I think it uses ConnMan rather than NetworkManager?).
[20:38] <tsimonq2> Yeah, it does
[20:39] <tsimonq2> also if other n-m flavors exhibit this bug, we know it's n-m
[20:39] <arraybolt3[m]> Especially if the same version of NM on non-Ubuntu distros does this (perhaps give Arch a shot?).
[20:39] <tsimonq2> Anyway... I'll boot back into the supported kernel so I can get work done, until this bug is fixed :P
[21:12]  * arraybolt3[m] is going to vanish for a bit if all goes well - rebooting after a system upgrade and also installing KDE updated from -proposed
[21:12] <arraybolt3[m]> (Yes, on my production system. I like playing with fire sometimes I guess.)
[21:56] <arraybolt3[m]> Alright so that was weird. I now know how to make Gitea repos from the API, and push to them using Git manually. Only thing I don't think I have the brains to automate right now is the username and password entry for each git push, so I'm just going to finish up here, and then plug in my username and password several times while it migrates everything over.
[21:57] <arraybolt3[m]> (And yeah an SSH key would probably have automated even the authentication but I don't have the brains for that right now :P)
[22:00] <arraybolt3[m]> Simon Quigley, teward, Dan Simmons: Alright, I am about to pull the "Migrate" lever, are we ready?
[22:01] <arraybolt3[m]> Or do I hand the script over to someone else at this point and they do it?
[22:06] <arraybolt3[m]> This is the script:
[22:06]  * arraybolt3[m] sent a code block: https://libera.ems.host/_matrix/media/v3/download/libera.chat/8c6da1f6afb31328014f7b3946c2c98b5370cade
[22:06] <arraybolt3[m]> And yes, I am a bit embarrassed that it took me this long to come up with something that looks this simple, but at least it's ready.
[22:06] <arraybolt3[m]> (I believe.)
[22:09] <arraybolt3[m]> Heh, I forgot to double-check some of the names, one moment...
 "is going to vanish for a bit..." <- stable-proposed isn't devel-proposed, I think you're safe :)
[22:10] <teward> just do it when you're ready its why i made a backup of gitea
[22:11] <arraybolt3[m]>  * ```... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/3219863d8798ef581a16d2efd44b01f5479721d9>)
[22:11] <arraybolt3[m]> Alright, had one name wrong, fixed it.
 "Alright so that was weird. I now..." <- git clone https://GH_USER:KEY_NOT_YOUR_PASSWORD!!!/etc.
 "And yes, I am a bit embarrassed..." <- I mean I guess some of those Phabricator JSON monsters were tough cookies to crumble so it's not that simple but...
[22:12] <arraybolt3[m]> tsimonq2: Oh nice.
[22:13] <arraybolt3[m]> Key being an API key or a personal access token?
 "And yes, I am a bit embarrassed..." <- I mean, here's the thing... I didn't give you a lot of info to start this project and you built it in less than a week. Don't be sorry for anything :)
[22:13] <tsimonq2> arraybolt3[m]: Latter
[22:14] <tsimonq2> > <@arraybolt3:matrix.org> ```... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/f6987b1efb91790d3f8cd59bb7d92add18c181ba>)
[22:14] <arraybolt3[m]> Odd, Gitea doesn't even have personal access tokens...
[22:14] <arraybolt3[m]> That I can tell.
[22:14] <arraybolt3[m]> tsimonq2: #!/usr/bin/env python3, right?
[22:14] <tsimonq2> arraybolt3[m]: That syntax is how you'd feed it info
[22:14] <arraybolt3[m]> That's what I see used a lot.
[22:15] <tsimonq2> GiTea may not support those types of tokens... but you may be able to use your password or an API key?
[22:15] <arraybolt3[m]> My password works, I just noticed you said "not my password" so that made me a bit gunshy.
 "Also now my snaps won't load lol" <- *cough* Flatpak 😂
[22:15] <tsimonq2> arraybolt3[m]: Not good practice. Works though :)
[22:16] <tsimonq2> kc2bez[m]: *someone* on the team has to actually use snaps, I won't pawn that off on anyone else :P
[22:17]  * arraybolt3[m] likes snaps but doesn't use them since Chrome works better...
[22:17] <tsimonq2> ¯\_(ツ)_/¯
[22:17] <tsimonq2> https://gitpython.readthedocs.io/en/stable/
[22:17] <tsimonq2> Also arraybolt3 @arraybolt3:matrix.org...
 "git clone https://GH_USER:..." <- Eh, I'd have to tear up too much code to do that, considering the number of repos involved.
[22:18] <arraybolt3[m]> tsimonq2: Oh that looks nifty.
[22:18] <arraybolt3[m]> Alright, activating migration in three... two... crud wait I have to make sure these go under the right organization.
[22:19] <kc2bez[m]> tsimonq2: I kid. I have some snaps that I use. 
[22:21] <arraybolt3[m]> Umm... ok so it turns out I can *create* a repository as the Lubuntu organization, I just can't delete it thereafter. So now I have "arrayboltAPITest" stuck in Lubuntu...
[22:21] <arraybolt3[m]> Hopefully someone can delete that.
[22:21] <kc2bez[m]> I think my all time favorite snap is LXD
[22:21] <kc2bez[m]> I should be able to delete stuff 
[22:22] <tsimonq2> kc2bez[m]: Yes, definitely kidding, sure ;)
[22:24] <arraybolt3[m]> Alright, carefully starting migration... (just gonna make sure I don't make a ton of garbage repos and then fail to fill them with anything)
[22:25] <arraybolt3[m]> Oh lovely I missed a couple of slashes, glad I proceeded carefully!
[22:28]  * kc2bez[m] uploaded an image: (52KiB) < https://libera.ems.host/_matrix/media/v3/download/matrix.org/lKjJpsdFSdapeURyYgMsmHvi/Screenshot%20from%202022-10-26%2018-27-49.png >
[22:28] <kc2bez[m]> Cue Kenny Loggins
[22:29] <arraybolt3[m]> Yeah I don't see that section when I look there.
[22:29] <kc2bez[m]> I think it needs Admin privs. Want me to delete it?
[22:29] <arraybolt3[m]> Dan Simmons: Yeah, and also lubuntu-meta while you're at it since my code boffoed and made that one and then errored out.
[22:30] <kc2bez[m]> ok
[22:30] <arraybolt3[m]> (Failed to increment a counter :P)
[22:32] <kc2bez[m]> Poof They are gone.
[22:32] <arraybolt3[m]> Thanks!
[22:32] <arraybolt3[m]> Alright, here goes!
[22:33] <arraybolt3[m]> Shoot, now Git is giving me errors I've never seen before...
[22:33] <kc2bez[m]> Hmm, whatcha got?
[22:33] <arraybolt3[m]> Probably a failed chdir somewhere that I tested first and then botched once it was all the way in the code.
[22:34] <kc2bez[m]> Oh, that would do it.
[22:34] <arraybolt3[m]> 🤦‍♂️ Sure enough. Alright, let's just make the repos this step and then populate them a second step.
[22:36] <arraybolt3[m]> Sap, that won't work.
[22:38] <arraybolt3[m]> Alright, it's working this time.
[22:39] <arraybolt3[m]> what in the world... now Gitea just timed out during a git upload.... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/798dda230015ed42bf69c023fd8f15e0d4a52943>)
[22:40] <arraybolt3[m]> Sigh. I have all five repos locally and all five made remotely, let's just finish this with some git pushes and call it a day.
[22:43] <arraybolt3[m]> Dan Simmons: OK so it looks like Gitea doesn't want to take lxqt-l10n-packaging. It fails with a Payload Too Large error as described above.
[22:43] <arraybolt3[m]> I thought it was a timeout, but I don't think so after all.
[22:44] <kc2bez[m]> We don't need that anymore 
[22:44] <arraybolt3[m]> Oh good.
[22:45] <arraybolt3[m]> Wow. So all that work to migrate a whole whopping four repos, three of which ended up having to be done halfway manually.
[22:45] <arraybolt3[m]> :P Well hey, at least we're done.
[22:46] <kc2bez[m]> That is awesome! 
[22:46] <arraybolt3[m]> Anyway, there's now an lxqtmeta-packaging repo that could use deleted, other than that I think we have conquered the Git repo migration.
[22:46] <arraybolt3[m]> And I learned a lot, so that's good!
[22:47] <arraybolt3[m]> Thank you guys for your patience with me, and hey, we're done!
[22:47] <tsimonq2> arraybolt3[m]: **thank you** for this :)
[22:47] <tsimonq2> 🎉
[22:49] <arraybolt3[m]> Final notes for myself after this. One, just because you tested it in the Python REPL and it worked, doesn't mean it will work once you plug it into the source code. Something may be different and mangle everything. Two, if your only good way of testing involves running something in production, find some other way to do it. Three, if you really can't find some other way to do it, save yourself the headache and run the whole thing
[22:49] <arraybolt3[m]> in a debugger for at least the first loop.
[22:50] <arraybolt3[m]> Had I followed all three of those (or even just two of the three!), the whole migration would have been automatic except for that one bit with lxqtmeta-packaging.
[22:51] <arraybolt3[m]>  * ```... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/aebae1c583f122af5cb8b1601f1747a33446d300>)
[22:51] <arraybolt3[m]> And also I went back and edited that script I posted first with all of the fixes.
[22:52] <arraybolt3[m]> Thankfully between teward's snapshot and Dan's willingness to help with deleting garbage repos, nothing was lost except for time. So woot!
[22:52] <arraybolt3[m]> Thank you guys!
[22:53] <tsimonq2> I'm glad you learned something, thank you to Dan and Thomas for assisting :)
 "Anyway, there's now an lxqtmeta..." <- Er... lxqt-l10n-packaging needs deleted. Wow, typo.
[23:39] <kc2bez[m]> Ok, just got back. I can do some cleanup.