[07:31:22] <MirahezeRelay>	 <rhinosf1> @paladox DO NOT UPDATE TO DEBIAN 12.3 - https://octodon.social/@alienghic/111554146479489358
[07:31:56] <MirahezeRelay>	 <rhinosf1> Debian 12.4 is fine
[07:32:14] <MirahezeRelay>	 <rhinosf1> But make sure the kernel package says kernel-image-6.1.0-15
[07:36:12] <MirahezeRelay>	 <paladox> we're running > Linux mw131 6.1.0-14-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.64-1 (2023-11-30) x86_64
[07:37:07] <MirahezeRelay>	 <paladox> there's a kernel update
[07:37:12] <MirahezeRelay>	 <rhinosf1> @paladox please tell me we aren't using ext4 or you haven't rebooted
[07:37:14] <MirahezeRelay>	 <paladox> 6.1.66-1 500
[07:37:25] <MirahezeRelay>	 <paladox> ext4 is the default file system on debian
[07:37:33] <MirahezeRelay>	 <paladox> so we are using ext4
[07:37:40] <MirahezeRelay>	 <rhinosf1> @paladox get us the hell off 6.1.64-1 asap please
[07:37:46] <MirahezeRelay>	 <rhinosf1> If that's the running kernel
[07:38:07] <MirahezeRelay>	 <rhinosf1> If you've rebooted since that got installed, risk of corruption
[07:38:21] <MirahezeRelay>	 <paladox> we updated to bookworm from bullseye on mw*
[07:38:35] <MirahezeRelay>	 <rhinosf1> @paladox ok, upgrade past that kernel
[07:38:36] <MirahezeRelay>	 <rhinosf1> Now
[07:56:46] <MirahezeRelay>	 <paladox> done
[07:58:02] <MirahezeRelay>	 <rhinosf1> @paladox and reboots?
[07:58:07] <MirahezeRelay>	 <paladox> yes
[07:58:11] <MirahezeRelay>	 <rhinosf1> Amazing 🙂
[07:58:19] <MirahezeRelay>	 <paladox> i do not upgrade a kernel without rebooting
[07:58:25] <MirahezeRelay>	 <rhinosf1> @paladox good
[07:58:38] <MirahezeRelay>	 <paladox> simply because i'll forget later on leading to corruption
[07:58:44] <MirahezeRelay>	 <rhinosf1> To confirm, 6.1.66-1 500 is the kernel we now have everywhere
[07:58:48] <MirahezeRelay>	 <rhinosf1> @paladox
[07:59:10] <MirahezeRelay>	 <paladox> on mw* yes, other hosts use slightly older then .64
[07:59:17] <MirahezeRelay>	 <rhinosf1> @paladox 🙂
[07:59:23] <MirahezeRelay>	 <rhinosf1> Disaster averted
[13:13:14] <MirahezeRelay>	 <jph2> any update to resolving issues with CreateWiki? It is still not assigning rights to requestors.
[18:23:57] <MirahezeRelay>	 <pixldev> Jesus
[19:20:13] <MirahezeRelay>	 <orduin, replying to jph2> What's the latest wiki with these symptoms? I'll try and investigate in about an hour or so
[19:36:50] <MirahezeRelay>	 <pixldev, replying to orduin> Going off support threads looks like https://discord.com/channels/407504499280707585/1183269256318697583
[19:36:59] <MirahezeRelay>	 <pixldev> 2 hours ago
[19:37:55] <MirahezeRelay>	 <pixldev> Wait that’s last message not post
[19:47:56] <MirahezeRelay>	 <orduin> We've got something we're investigating
[21:27:00] <MirahezeRelay>	 <jph2> Maybe you've fixed it. mercedesbenz.miraheze.org was created this morning and the requestor was not given bureau rights. the main page had been edited, so i couldn't tell if the boilerplate was posted. I see now the boilerplate is there and the requestor has their rights.
[21:32:15] <MirahezeRelay>	 <jph2> The one before that, created yesterday, however, is missing boilerplate and requestor is missing rights but is a user. So yestereday's wiki creations probably all need rights assigned.
[21:32:54] <MirahezeRelay>	 <jph2> I did just create a wiki and it took a minute to populate the main page boiler plate but it did assign rights, so appears fixed going forward.
[21:41:30] <MirahezeRelay>	 <jph2> yep. seems to be good now.