2024/12/24

Newest at the top

2024-12-24 18:46:45 +0100ljdarj(~Thunderbi@user/ljdarj) (Ping timeout: 265 seconds)
2024-12-24 18:42:54 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 260 seconds)
2024-12-24 18:38:07 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) merijn
2024-12-24 18:29:58 +0100robobub(uid248673@id-248673.uxbridge.irccloud.com) (Quit: Connection closed for inactivity)
2024-12-24 18:27:34 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 272 seconds)
2024-12-24 18:22:45 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) merijn
2024-12-24 18:20:54 +0100sayurc(~sayurc@169.150.203.34) sayurc
2024-12-24 18:19:21 +0100sayurc(~sayurc@169.150.203.34) (Quit: Konversation terminated!)
2024-12-24 18:12:13 +0100euphores(~SASL_euph@user/euphores) euphores
2024-12-24 18:11:28 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 265 seconds)
2024-12-24 18:10:47 +0100zerozzz
2024-12-24 18:09:41 +0100econo_(uid147250@id-147250.tinside.irccloud.com)
2024-12-24 18:04:42 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) merijn
2024-12-24 18:03:52 +0100ridcully(~ridcully@p57b52ec2.dip0.t-ipconnect.de) ridcully
2024-12-24 18:03:34 +0100ridcully(~ridcully@p57b52ec2.dip0.t-ipconnect.de) (Quit: WeeChat 4.4.2)
2024-12-24 17:58:42 +0100notzmv(~umar@user/notzmv) notzmv
2024-12-24 17:53:36 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 244 seconds)
2024-12-24 17:52:43 +0100euphores(~SASL_euph@user/euphores) (Quit: Leaving.)
2024-12-24 17:49:20 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) merijn
2024-12-24 17:45:16 +0100machinedgod(~machinedg@d108-173-18-100.abhsia.telus.net) (Ping timeout: 252 seconds)
2024-12-24 17:38:45 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 246 seconds)
2024-12-24 17:37:48 +0100prasad(~Thunderbi@c-73-75-25-251.hsd1.in.comcast.net)
2024-12-24 17:37:34 +0100 <geekosaur> if you think you have a bug, yes. At worst someone will tell you how it's supposed to work
2024-12-24 17:34:28 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) merijn
2024-12-24 17:31:54 +0100ubert(~Thunderbi@p200300ecdf117cf7bdcd23ba5c3b89f8.dip0.t-ipconnect.de) ubert
2024-12-24 17:30:52 +0100notzmv(~umar@user/notzmv) (Ping timeout: 265 seconds)
2024-12-24 17:26:01 +0100CrunchyFlakes(~CrunchyFl@31.19.233.78)
2024-12-24 17:23:37 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 265 seconds)
2024-12-24 17:23:34 +0100CrunchyFlakes(~CrunchyFl@31.19.233.78) (Read error: Connection reset by peer)
2024-12-24 17:22:46 +0100pavonia(~user@user/siracusa) siracusa
2024-12-24 17:19:59 +0100machinedgod(~machinedg@d108-173-18-100.abhsia.telus.net) machinedgod
2024-12-24 17:19:05 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) merijn
2024-12-24 17:11:09 +0100JuanDaugherty(~juan@user/JuanDaugherty) JuanDaugherty
2024-12-24 17:08:21 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 248 seconds)
2024-12-24 17:03:42 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) merijn
2024-12-24 16:58:36 +0100sayurc(~sayurc@169.150.203.34) sayurc
2024-12-24 16:52:50 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 260 seconds)
2024-12-24 16:48:20 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) merijn
2024-12-24 16:45:58 +0100ljdarj(~Thunderbi@user/ljdarj) ljdarj
2024-12-24 16:40:07 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 265 seconds)
2024-12-24 16:35:46 +0100xff0x(~xff0x@p3704193-ipxg12201sapodori.hokkaido.ocn.ne.jp) (Ping timeout: 265 seconds)
2024-12-24 16:35:07 +0100Sgeo(~Sgeo@user/sgeo) Sgeo
2024-12-24 16:33:15 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) merijn
2024-12-24 16:30:32 +0100 <hseg> should I perhaps post this to the cabal-install github?
2024-12-24 16:29:48 +0100 <int-e> I can live with a breaking change that only affects a few packages (using those Path modules is not too common)
2024-12-24 16:29:01 +0100 <int-e> Anyway, the real issue I have is that there's no way I can see to *express* that Cabal-3.14 is unfit for building that package.
2024-12-24 16:28:30 +0100 <int-e> So if a generated file isn't backwards compatible... that's very murky.
2024-12-24 16:28:03 +0100 <int-e> Yes but my understanding is that the build tool semantics are not supposed to change either.
2024-12-24 16:26:43 +0100 <hseg> not of the build tool
2024-12-24 16:26:39 +0100 <hseg> note that cabal-version is the version of the .cabal format