Newest at the top
| 2024-12-24 17:58:42 +0100 | notzmv | (~umar@user/notzmv) notzmv |
| 2024-12-24 17:53:36 +0100 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 244 seconds) |
| 2024-12-24 17:52:43 +0100 | euphores | (~SASL_euph@user/euphores) (Quit: Leaving.) |
| 2024-12-24 17:49:20 +0100 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) merijn |
| 2024-12-24 17:45:16 +0100 | machinedgod | (~machinedg@d108-173-18-100.abhsia.telus.net) (Ping timeout: 252 seconds) |
| 2024-12-24 17:38:45 +0100 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 246 seconds) |
| 2024-12-24 17:37:48 +0100 | prasad | (~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 +0100 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) merijn |
| 2024-12-24 17:31:54 +0100 | ubert | (~Thunderbi@p200300ecdf117cf7bdcd23ba5c3b89f8.dip0.t-ipconnect.de) ubert |
| 2024-12-24 17:30:52 +0100 | notzmv | (~umar@user/notzmv) (Ping timeout: 265 seconds) |
| 2024-12-24 17:26:01 +0100 | CrunchyFlakes | (~CrunchyFl@31.19.233.78) |
| 2024-12-24 17:23:37 +0100 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 265 seconds) |
| 2024-12-24 17:23:34 +0100 | CrunchyFlakes | (~CrunchyFl@31.19.233.78) (Read error: Connection reset by peer) |
| 2024-12-24 17:22:46 +0100 | pavonia | (~user@user/siracusa) siracusa |
| 2024-12-24 17:19:59 +0100 | machinedgod | (~machinedg@d108-173-18-100.abhsia.telus.net) machinedgod |
| 2024-12-24 17:19:05 +0100 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) merijn |
| 2024-12-24 17:11:09 +0100 | JuanDaugherty | (~juan@user/JuanDaugherty) JuanDaugherty |
| 2024-12-24 17:08:21 +0100 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 248 seconds) |
| 2024-12-24 17:03:42 +0100 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) merijn |
| 2024-12-24 16:58:36 +0100 | sayurc | (~sayurc@169.150.203.34) sayurc |
| 2024-12-24 16:52:50 +0100 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 260 seconds) |
| 2024-12-24 16:48:20 +0100 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) merijn |
| 2024-12-24 16:45:58 +0100 | ljdarj | (~Thunderbi@user/ljdarj) ljdarj |
| 2024-12-24 16:40:07 +0100 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 265 seconds) |
| 2024-12-24 16:35:46 +0100 | xff0x | (~xff0x@p3704193-ipxg12201sapodori.hokkaido.ocn.ne.jp) (Ping timeout: 265 seconds) |
| 2024-12-24 16:35:07 +0100 | Sgeo | (~Sgeo@user/sgeo) Sgeo |
| 2024-12-24 16:33:15 +0100 | merijn | (~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 |
| 2024-12-24 16:25:45 +0100 | Natch | (~natch@c-92-34-7-158.bbcust.telenor.se) (Ping timeout: 252 seconds) |
| 2024-12-24 16:25:14 +0100 | <int-e> | Oh I hate the fact that DDG found docs for version 3.4. |
| 2024-12-24 16:24:39 +0100 | <int-e> | I guess 3.14 should conservatively refuse to work with any package that doesn't specify cabal-version: 3.14 or later? ("refuse" - it can still build Setup executable with an older Cabal version) |
| 2024-12-24 16:22:15 +0100 | <int-e> | https://cabal.readthedocs.io/en/3.4/cabal-package.html#pkg-field-cabal-version ...okay I'm confused. There used to be a lower bound syntax here but that's discontinued. |
| 2024-12-24 16:22:06 +0100 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 246 seconds) |
| 2024-12-24 16:21:29 +0100 | <int-e> | hrm |
| 2024-12-24 16:20:47 +0100 | <hseg> | indeed, https://hackage.haskell.org/package/chs-cabal-0.1.1.2/revisions/ seems to have deliberately introduced that upper bound? |
| 2024-12-24 16:19:28 +0100 | <hseg> | https://hackage.haskell.org/package/chs-cabal-0.1.1.2/src/chs-cabal.cabal sets cabal-version to 1.18, so I don't _think_ that's the right place to blame? |
| 2024-12-24 16:17:52 +0100 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) merijn |
| 2024-12-24 16:16:51 +0100 | <int-e> | there's a 0.1.1.4 that works with Cabal-3.14? |
| 2024-12-24 16:16:05 +0100 | <int-e> | well, for 0.1.1.2 at least |
| 2024-12-24 16:15:25 +0100 | <int-e> | I think what chs-cabal needs is an upper bound on its cabal-version field |
| 2024-12-24 16:09:11 +0100 | ljdarj | (~Thunderbi@user/ljdarj) (Ping timeout: 265 seconds) |
| 2024-12-24 16:07:19 +0100 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 264 seconds) |
| 2024-12-24 16:06:00 +0100 | bitdex | (~bitdex@gateway/tor-sasl/bitdex) bitdex |