2026/04/01

Newest at the top

2026-04-01 14:57:16 +0200tremon(~tremon@83.80.159.219) tremon
2026-04-01 14:51:53 +0200humasect(~humasect@dyn-192-249-132-90.nexicom.net) (Ping timeout: 248 seconds)
2026-04-01 14:51:00 +0200arandombit(~arandombi@user/arandombit) (Remote host closed the connection)
2026-04-01 14:49:52 +0200squid64(~user@fsf/member/squid64) squid64
2026-04-01 14:46:18 +0200arandombit(~arandombi@user/arandombit) arandombit
2026-04-01 14:46:02 +0200wennefer0(~wennefer0@user/wennefer0) (Ping timeout: 265 seconds)
2026-04-01 14:41:21 +0200wennefer0(~wennefer0@user/wennefer0) wennefer0
2026-04-01 14:41:15 +0200humasect(~humasect@dyn-192-249-132-90.nexicom.net) humasect
2026-04-01 14:39:40 +0200Nosrep(~jimothy@user/nosrep) Nosrep
2026-04-01 14:36:04 +0200Pixi(~Pixi@user/pixi) Pixi
2026-04-01 14:31:40 +0200arandombit(~arandombi@user/arandombit) (Ping timeout: 244 seconds)
2026-04-01 14:30:34 +0200 <tomsmeding> merijn: a manually created overlay, or does hackage already serve one?
2026-04-01 14:26:37 +0200 <merijn> tomsmeding: iirc you can specify an overlay to use candidates
2026-04-01 14:21:01 +0200Pixi(~Pixi@user/pixi) (Quit: Leaving)
2026-04-01 14:18:30 +0200rensenwxre(~fwam@user/fwam) fwam
2026-04-01 14:14:37 +0200humasect(~humasect@dyn-192-249-132-90.nexicom.net) (Ping timeout: 265 seconds)
2026-04-01 14:08:11 +0200humasect(~humasect@dyn-192-249-132-90.nexicom.net) humasect
2026-04-01 14:01:58 +0200divlamir(~divlamir@user/divlamir) (Read error: Connection reset by peer)
2026-04-01 13:43:48 +0200j1n37(~j1n37@user/j1n37) (Ping timeout: 255 seconds)
2026-04-01 13:39:02 +0200czan(~czan@user/mange) czan
2026-04-01 12:53:23 +0200fp1(~Thunderbi@2001:708:20:1406::1370) fp
2026-04-01 12:45:58 +0200CiaoSen(~Jura@p549cb690.dip0.t-ipconnect.de) CiaoSen
2026-04-01 12:43:17 +0200xff0x(~xff0x@2405:6580:b080:900:4a9b:f7a0:11a1:60ca)
2026-04-01 12:41:09 +0200humasect(~humasect@dyn-192-249-132-90.nexicom.net) (Ping timeout: 245 seconds)
2026-04-01 12:36:35 +0200humasect(~humasect@dyn-192-249-132-90.nexicom.net) humasect
2026-04-01 12:30:38 +0200Square2(~Square4@user/square) Square
2026-04-01 12:29:00 +0200divlamir(~divlamir@user/divlamir) divlamir
2026-04-01 12:27:28 +0200humasect(~humasect@dyn-192-249-132-90.nexicom.net) (Remote host closed the connection)
2026-04-01 12:27:13 +0200lisbeths(uid135845@id-135845.lymington.irccloud.com) lisbeths
2026-04-01 12:24:11 +0200divlamir(~divlamir@user/divlamir) (Ping timeout: 268 seconds)
2026-04-01 12:23:22 +0200gmg(~user@user/gehmehgeh) gehmehgeh
2026-04-01 12:21:12 +0200gmg(~user@user/gehmehgeh) (Ping timeout: 265 seconds)
2026-04-01 12:18:20 +0200divlamir(~divlamir@user/divlamir) divlamir
2026-04-01 12:13:28 +0200divlamir(~divlamir@user/divlamir) (Read error: Connection reset by peer)
2026-04-01 12:11:49 +0200divlamir_divlamir
2026-04-01 12:11:48 +0200divlamir(~divlamir@user/divlamir) (Ping timeout: 256 seconds)
2026-04-01 12:10:33 +0200ChanServ+v haskellbridge
2026-04-01 12:10:33 +0200haskellbridge(~hackager@96.28.224.214) hackager
2026-04-01 12:10:06 +0200CiaoSen(~Jura@p549cb690.dip0.t-ipconnect.de) (Ping timeout: 244 seconds)
2026-04-01 12:08:24 +0200czan(~czan@user/mange) (Ping timeout: 256 seconds)
2026-04-01 12:07:52 +0200divlamir_(~divlamir@user/divlamir) divlamir
2026-04-01 12:07:14 +0200haskellbridge(~hackager@96.28.224.214) (Read error: Connection reset by peer)
2026-04-01 12:03:56 +0200 <tomsmeding> what can one do with a package candidate on hackage? I know you can look at the hackage page to see if documentation etc. (when self-uploaded) is correct, but is there a way to test _using_ the package?
2026-04-01 11:49:19 +0200humasect(~humasect@dyn-192-249-132-90.nexicom.net) humasect
2026-04-01 11:42:20 +0200xff0x(~xff0x@fsb6a9491c.tkyc517.ap.nuro.jp) (Ping timeout: 256 seconds)
2026-04-01 11:27:17 +0200qqq(~qqq@185.54.20.216) (Remote host closed the connection)
2026-04-01 11:25:34 +0200dutchie(~dutchie@user/dutchie) dutchie
2026-04-01 11:24:29 +0200dutchie(~dutchie@user/dutchie) (Remote host closed the connection)
2026-04-01 11:19:45 +0200Googulator59Googulator
2026-04-01 11:08:34 +0200poscat(~poscat@user/poscat) (Ping timeout: 248 seconds)