2024/05/01

Newest at the top

2024-05-01 13:45:55 +0200madeleine-sydney(~madeleine@c-76-155-235-153.hsd1.co.comcast.net) (Quit: Konversation terminated!)
2024-05-01 13:44:01 +0200Square(~Square@user/square)
2024-05-01 13:41:20 +0200acidjnk(~acidjnk@p200300d6e714dc53acbe2cc37902b0bc.dip0.t-ipconnect.de)
2024-05-01 13:36:01 +0200mei(~mei@user/mei)
2024-05-01 13:35:25 +0200mei(~mei@user/mei) (Remote host closed the connection)
2024-05-01 13:34:20 +0200Maxdamantus(~Maxdamant@user/maxdamantus)
2024-05-01 13:26:25 +0200raehik(~raehik@rdng-25-b2-v4wan-169990-cust1344.vm39.cable.virginm.net)
2024-05-01 13:23:57 +0200destituion(~destituio@2a02:2121:340:2456:fffe:d0f:7737:dd1)
2024-05-01 13:23:45 +0200L29Ah(~L29Ah@wikipedia/L29Ah)
2024-05-01 13:21:20 +0200L29Ah(~L29Ah@wikipedia/L29Ah) (Remote host closed the connection)
2024-05-01 13:18:39 +0200Maxdaman1us(~Maxdamant@user/maxdamantus) (Ping timeout: 256 seconds)
2024-05-01 13:17:43 +0200destituion(~destituio@2a02:2121:340:2456:fffe:d0f:7737:dd1) (Ping timeout: 255 seconds)
2024-05-01 13:13:07 +0200guest7621(~username@120.17.103.254) (Read error: Connection reset by peer)
2024-05-01 13:13:07 +0200gues51644(~username@120.17.103.254) (Read error: Connection reset by peer)
2024-05-01 12:53:04 +0200Lord_of_Life_Lord_of_Life
2024-05-01 12:52:07 +0200Lord_of_Life(~Lord@user/lord-of-life/x-2819915) (Ping timeout: 260 seconds)
2024-05-01 12:51:41 +0200Lord_of_Life_(~Lord@user/lord-of-life/x-2819915)
2024-05-01 12:49:41 +0200xff0x(~xff0x@softbank219059019218.bbtec.net)
2024-05-01 12:48:34 +0200gues51644(~username@120.17.103.254)
2024-05-01 12:47:25 +0200guest7621(~username@120.17.103.254)
2024-05-01 12:21:47 +0200mwnaylor(~user@2601:5cf:837e:2bb0::f472) (Ping timeout: 260 seconds)
2024-05-01 12:09:08 +0200 <hseg> lyxia: thanks! In hindsight, it makes sense that such an off-the-beaten-path configuration would need manual intervention
2024-05-01 12:08:24 +0200hseg(~gesh@77.137.75.224)
2024-05-01 12:04:04 +0200L29Ah(~L29Ah@wikipedia/L29Ah)
2024-05-01 12:02:23 +0200hseg(~gesh@77.137.75.224) (Ping timeout: 264 seconds)
2024-05-01 11:57:58 +0200L29Ah(~L29Ah@wikipedia/L29Ah) ()
2024-05-01 11:53:33 +0200 <lyxia> hseg: https://docs.haskellstack.org/en/stable/yaml_configuration/#compiler
2024-05-01 11:45:48 +0200aws(~alews@user/aws)
2024-05-01 11:45:48 +0200aws(~alews@141.94.77.100) (Changing host)
2024-05-01 11:45:32 +0200aosync_aws
2024-05-01 11:43:15 +0200oo_miguel1oo_miguel
2024-05-01 11:43:15 +0200oo_miguel(~Thunderbi@78-11-181-16.static.ip.netia.com.pl) (Ping timeout: 245 seconds)
2024-05-01 11:41:52 +0200oo_miguel1(~Thunderbi@78-11-181-16.static.ip.netia.com.pl)
2024-05-01 11:32:25 +0200xff0x(~xff0x@softbank219059019218.bbtec.net) (Ping timeout: 245 seconds)
2024-05-01 11:31:10 +0200barak(~barak@2a0d:6fc2:68c1:7200:3cf2:a87d:a02b:3e21)
2024-05-01 11:29:30 +0200gues90080(~username@ppp121-45-202-250.cbr-trn-nor-bras38.tpg.internode.on.net) (Ping timeout: 245 seconds)
2024-05-01 11:26:54 +0200FinnElija(~finn_elij@user/finn-elija/x-0085643)
2024-05-01 11:26:10 +0200FinnElija(~finn_elij@user/finn-elija/x-0085643) (Remote host closed the connection)
2024-05-01 11:25:35 +0200jinsun(~jinsun@user/jinsun)
2024-05-01 10:53:27 +0200acidjnk(~acidjnk@p200300d6e714dc53acbe2cc37902b0bc.dip0.t-ipconnect.de) (Ping timeout: 256 seconds)
2024-05-01 10:43:44 +0200xff0x(~xff0x@softbank219059019218.bbtec.net)
2024-05-01 10:42:43 +0200xff0x(~xff0x@softbank219059019218.bbtec.net) (Ping timeout: 268 seconds)
2024-05-01 10:37:33 +0200oo_miguel(~Thunderbi@78-11-181-16.static.ip.netia.com.pl)
2024-05-01 10:37:09 +0200sawilagar(~sawilagar@user/sawilagar)
2024-05-01 10:36:24 +0200 <hseg> (alternatively, where can I track progress on cutting an lts using ghc 9.6.5? It has a bugfix that's critical on my system)
2024-05-01 10:34:53 +0200 <hseg> I know I can set the lts part by stack config set resolver lts-22.19, but does stack not have a way to write the compiler version to use?
2024-05-01 10:34:15 +0200 <hseg> Hi. I'm packaging some haskell programs, and am planning to build them with stack. Other than manually editing stack.yaml, is there a way to set the snapshot to lts-22.19+ghc-9.6.5 ?
2024-05-01 10:32:05 +0200hseg(~gesh@77.137.75.224)
2024-05-01 10:26:15 +0200danza(~francesco@151.43.219.217) (Ping timeout: 255 seconds)
2024-05-01 10:21:35 +0200talismanick(~user@2601:644:937c:ed10::ae5) (Ping timeout: 245 seconds)