2020-09-26T02:42:46 *** okurz_ is now known as okurz 2020-09-26T05:13:17 Forum thread pages are refusing to completely load, which breaks quoting-reply. 2020-09-26T05:13:49 connecting to beans.opensuse.org remains in statusbar 2020-09-26T05:20:51 got it figured out 2020-09-26T05:27:16 I thought I had, but submitting is producing similar failure due to beans.*. 2020-09-26T05:28:46 second try worked, but it's still not getting through to beans.*. 2020-09-26T12:26:24 beans.o.o is back - it was an interesting[tm] error 2020-09-26T12:39:39 the details are too long for IRC, I sent a mail to heroes@ instead 2020-09-26T14:12:45 bmwiedemann1: we will be replacing mailing list backend whenever I have the time to migrate it, so I don't think it's worth the effort currently 2020-09-26T17:08:45 lcp: I have an idea how we could fix the messed up charset in the forums database without too much effort 2020-09-26T17:09:06 so far, we thought about fixing it with sql statements in the database, which is a can of worms 2020-09-26T17:09:19 however, fixing it on the sqldump level should be easier: 2020-09-26T17:09:47 "just" split the INSERTs with latin1 charset into a separate file and then convert that file to utf8 2020-09-26T17:10:28 that split will be manual work (cut&paste), but since it probably only affects a few tables, it shouldn't be too difficult 2020-09-26T18:48:03 cboltz: that's true, I would have to check if the stuff in tables is put there in any sort of order (since the affected bits are before date x) 2020-09-26T18:55:10 usually sqldumps are in insert order, so in theory converting the "first half" of each affected / important table should work 2020-09-26T18:59:03 hopefully, now I would just need to check the date tbh