[06:35:52] <MirahezeRelay>	 <zipppee, replying to xaloria45> depends on version
[06:36:32] <MirahezeRelay>	 <zipppee> on which note my project for next week is to see if I can bump createwiki to a more recent version without blowing the whole of wikioasis up
[08:25:23] <MirahezeRelay>	 <theastrohim> [1/2] Isn’t this error fixed?
[08:25:23] <MirahezeRelay>	 <theastrohim> [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1427572986705346633/IMG_1507.jpg?ex=68ef5a73&is=68ee08f3&hm=49a9db29bc5823dd04b48b7075fa068c357783c4ade88efaf416cff9b07dca69&
[09:31:20] <MirahezeRelay>	 <originalauthority> I'm assuming since you're accessing SpecialCreateWiki this is not running on Miraheze.
[09:31:41] <MirahezeRelay>	 <originalauthority> In which case, it's probably a config issue on whatever you're running that on.
[09:59:39] <MirahezeRelay>	 <theastrohim, replying to originalauthority> No I can access the SpecialCreateWiki without any errors whatever I put in the database name and submit it returns as the database already exists so is this my Config issue or its issue in the extension
[10:00:46] <MirahezeRelay>	 <theastrohim> I saw similar issue ongoing on Miraheze in Phorge.
[10:12:31] <MirahezeRelay>	 <rhinosf1, replying to theastrohim> What task?
[10:12:39] <MirahezeRelay>	 <rhinosf1, replying to theastrohim> Likely a your config issue
[10:15:24] <MirahezeRelay>	 <theastrohim, replying to rhinosf1> https://issue-tracker.miraheze.org/T14385
[10:16:10] <MirahezeRelay>	 <theastrohim, replying to rhinosf1> I am also having same issue as mentioned here
[11:11:59] <MirahezeRelay>	 <90gq29> [1/3] i noticed miraheze is running 8.2.29 of PHP, which is supposedly ending security support in december of this year (e.g in less than 2 monhts)
[11:11:59] <MirahezeRelay>	 <90gq29> [2/3] most recent ver is 8.4 with 8.5 releasing soon
[11:12:00] <MirahezeRelay>	 <90gq29> [3/3] https://cdn.discordapp.com/attachments/1006789349498699827/1427614912678723745/zSp2B5d.png?ex=68ef817e&is=68ee2ffe&hm=62feeebbec61056e308ad796222d14c5eefa57c73ee9c5b89ff0942b510e9a95&
[11:13:21] <MirahezeRelay>	 <90gq29> are we waiting on 8.5 to update, or?
[11:13:33] <MirahezeRelay>	 <90gq29> cuz like even fandom is on a more recent version
[16:29:57] <MirahezeRelay>	 <rhinosf1, replying to 90gq29> Not relevant anyway to us as Debian security team will support us for a bit longer
[16:39:55] <MirahezeRelay>	 <90gq29, replying to rhinosf1> ye but why not update it
[16:40:05] <MirahezeRelay>	 <90gq29> i assume the new versions are better optimized
[16:41:53] <MirahezeRelay>	 <reception123> It also needs an OS update first and that's a bit trickier
[17:50:36] <MirahezeRelay>	 <awing_ding, replying to reception123> that's why you always install arch on servers /j
[18:34:47] <MirahezeRelay>	 <rhinosf1, replying to 90gq29> Life isn't that simple
[18:34:57] <MirahezeRelay>	 <rhinosf1> Things need testing
[18:35:13] <MirahezeRelay>	 <rhinosf1> You need windows to test them with people and servers free
[18:35:21] <MirahezeRelay>	 <rhinosf1> Other things may affect it
[21:02:43] <MirahezeRelay>	 <90gq29, replying to rhinosf1> ye but thats worth it, no?
[21:03:29] <MirahezeRelay>	 <90gq29> can't just remain on outdated versions of the underlying software forever
[21:04:44] <MirahezeRelay>	 <90gq29> if theres anything i can do ill help yall test wtv
[21:10:49] <MirahezeRelay>	 <thewwrnerdguy, replying to 90gq29> [1/2] true but it's also not worth upgrading to the latest thing as soon as possible. granted, eos is probably about the time that an upgrade should be done
[21:10:49] <MirahezeRelay>	 <thewwrnerdguy, replying to 90gq29> [2/2] Also according to wikipedia eos for 8.2 is December 2026?
[21:11:46] <MirahezeRelay>	 <thewwrnerdguy> [1/2] https://www.php.net/supported-versions
[21:11:46] <MirahezeRelay>	 <thewwrnerdguy> [2/2] Yeah still a year to go
[21:13:07] <MirahezeRelay>	 <90gq29, replying to thewwrnerdguy> mb misread it
[21:13:20] <MirahezeRelay>	 <90gq29> yeah whoops 8.1 is the one thats ending support this year
[21:13:48] <MirahezeRelay>	 <posix_memalign, replying to 90gq29> Just need someone to resolve this task https://issue-tracker.miraheze.org/T14118
[21:14:29] <MirahezeRelay>	 <90gq29, replying to posix_memalign> i assume no one wants to do it? 🧐
[21:14:30] <MirahezeRelay>	 <posix_memalign> It will probably be quite difficult though. Plus there are higher priority tasks like upgrading to SUL3.
[21:15:07] <MirahezeRelay>	 <90gq29, replying to posix_memalign> fair
[21:15:10] <MirahezeRelay>	 <pskyechology> infra be cooking up cooler stuff like servers not exploding
[21:15:25] <MirahezeRelay>	 <posix_memalign, replying to 90gq29> [1/2] https://issue-tracker.miraheze.org/T10914
[21:15:25] <MirahezeRelay>	 <posix_memalign, replying to 90gq29> [2/2] Just need some patience
[21:16:21] <MirahezeRelay>	 <pskyechology> record to beat: january
[21:16:33] <MirahezeRelay>	 <90gq29, replying to pskyechology> that'd be nice as well
[21:17:49] <MirahezeRelay>	 <posix_memalign> Debian stable releases are supported for at least 5 years, so when a new stable version comes out, we have 5 - 2 = 3 years to upgrade. Taking 6 months to do so would be on the faster side lol.
[21:44:56] <MirahezeRelay>	 <paladox, replying to 90gq29> debian maintains packages that are EOL so security stuff will still happen. Since they do LTS releases.
[21:47:20] <BlankEclair>	 the two types of sysadmins: debian users, and arch users