00:13:13 Unstable branch on cbro.berotato.org updated to: 0.33-a0-640-g717b6cd007 (34) 00:54:39 Monster database of master branch on crawl.develz.org updated to: 0.33-a0-640-g717b6cd007 04:35:14 Experimental (bcrawl) branch on underhound.eu updated to: 0.23-a0-5249-g4a8afe7061 05:07:24 Unstable branch on crawl.akrasiac.org updated to: 0.33-a0-640-g717b6cd (34) 06:47:46 03Flugkiller02 {Implojin} 07* 0.33-a0-641-gf20420b48f: fix: Make spells that never miss unaffected by blindness 10(20 hours ago, 1 file, 2+ 1-) 13https://github.com/crawl/crawl/commit/f20420b48f08 06:49:57 03Implojin02 07* 0.33-a0-642-g974e7ae34f: Add Flugkiller to the CREDITS 10(44 seconds ago, 1 file, 1+ 0-) 13https://github.com/crawl/crawl/commit/974e7ae34f48 06:58:37 04Build failed for 08master @ f20420b4 06https://github.com/crawl/crawl/actions/runs/12610975713 06:59:05 <03i​mplojin> hmmmm 06:59:08 <03i​mplojin> oh 07:00:13 <03i​mplojin> our runners are using ubuntu images and getting hit by those reported glu compile issues? 07:01:49 04Build failed for 08master @ 974e7ae3 06https://github.com/crawl/crawl/actions/runs/12610990391 07:04:37 <03i​mplojin> well, i guess fixing this should solve a few open issues at least 09:17:19 <03i​mplojin> so, yeah, what's happening here is that github's ubuntu-latest runner upgraded to ubuntu 24.04 today: https://github.com/actions/runner-images/issues/10636 and this broke a bunch of our CI. Adding a libglu1-mesa-dev dep fixes some of it, but not all of it. Probably going to temporarily set our runners to use 22.04 to let CI work while we figure out the rest 09:20:12 that's what we did more or less last time they did this (several months ago, quickly rolled back because pretty much everyone's CI broke) 09:21:16 we're still using 22.04 because it's a build tool we need to support older versions of a compiler that won't run on 24.04 (need libncurses.so.5 which isn't available any more) 09:38:09 03Implojin02 07* 0.33-a0-643-g1404ca9d21: Temporarily set CI to ubuntu 22.04 10(28 minutes ago, 1 file, 11+ 11-) 13https://github.com/crawl/crawl/commit/1404ca9d2121 09:41:17 Oh, it's a gradual rollout. I kept seeing different projects hitting the upgrade problem at different times, myself encountering it like two weeks ago, but wasn't able to connect all the dots. 10:23:13 gwm5600 (L13 MiBe) Crash caused by signal #6: Aborted (Zot:5) 13:47:18 <04d​racoomega> Quaintly ancient comment here: // Sort the dropped items so we don't see weird behaviour when // dropping a worn robe before a cloak (old behaviour: remove // cloak, remove robe, wear cloak, drop robe, remove cloak, drop // cloak). 13:47:57 <04d​racoomega> (I don't think ths is a reason to enforce a particular slot order behind the scenes anymore >.>) 14:03:24 03gammafunk02 07* 0.33-a0-644-g64fd3f8b57: Update the list of required Tiles packages (Cgettys) 10(18 minutes ago, 1 file, 2+ 1-) 13https://github.com/crawl/crawl/commit/64fd3f8b57e9 15:42:08 Colgate (L11 DEHW) Crash caused by signal #6: Aborted (Lair:2) 15:45:35 <04d​racoomega> A crocodile bursts forth beneath you and grabs the yak in its jaws! The yak falls through a shaft! The shaft crumbles and collapses. Haha, welp 16:05:51 "Look out, centaur! Suddenly a trapdoor in the ceiling opens and a crocodile with a yak in its jaws falls on your head. Fortunately, you are wearing a hard helmet." 16:41:21 Unstable branch on underhound.eu updated to: 0.33-a0-644-g64fd3f8b57 (34) 22:42:21 bolt::harmless_to_player() for cloud spells does not check for Qazlal cloud immunity. Is this for some reason I didn't consider, or can this be modified? I want to give it a try. 22:45:02 wait, it's already there: if (you.cloud_immune() && is_big_cloud())... 22:46:10 Anyways, the targeter doesn't function as I expected in Meph Cloud + Qazlal, I'll look at it. 23:35:54 Unstable branch on crawl.develz.org updated to: 0.33-a0-644-g64fd3f8b57 (34) 23:59:28 Windows builds of master branch on crawl.develz.org updated to: 0.33-a0-644-g64fd3f8b57