Newest at the top
| 2025-05-01 22:43:16 +0200 | peterbecich | (~Thunderbi@syn-047-229-123-186.res.spectrum.com) peterbecich |
| 2025-05-01 22:42:49 +0200 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 265 seconds) |
| 2025-05-01 22:40:01 +0200 | <geekosaur> | *is an |
| 2025-05-01 22:39:45 +0200 | <tomsmeding> | yay |
| 2025-05-01 22:39:35 +0200 | <tomsmeding> | sim590: in the Cabal user guide, the .cabal file is 'cabal reference' section 1, and the cabal.project file is section 2 ;) |
| 2025-05-01 22:39:32 +0200 | <geekosaur> | anyway the project file parser is known to be half-assed; the change to check for known stanzas are an interim fix, there's a new parser in development that might make 3.16 |
| 2025-05-01 22:39:03 +0200 | <sim590> | Thanks very much to everyone helping debugging this. I hope to get to know these files better in the future. I know the `.cabal` file better, but it seems like when I get on the documentation website, I always assume the options are for `.cabal` files, but I guess now I have to look better to know if they are for other files. |
| 2025-05-01 22:38:09 +0200 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-05-01 22:37:35 +0200 | <tomsmeding> | (but thanks to whomever fixed it for 3.14 :) ) |
| 2025-05-01 22:37:27 +0200 | <geekosaur> | (the downside being that now there's an extra place that needs to be updated if new stanzas are added) |
| 2025-05-01 22:37:09 +0200 | <tomsmeding> | who decided ignoring unknown stanzas was a good idea :p |
| 2025-05-01 22:36:40 +0200 | <geekosaur> | yes, which it ignores in older cabal. 3.14 does better |
| 2025-05-01 22:36:38 +0200 | <tomsmeding> | I'd expect an error on encountering an unknown stanza |
| 2025-05-01 22:36:21 +0200 | <tomsmeding> | but an unknown stanza, surely? |
| 2025-05-01 22:36:12 +0200 | <geekosaur> | it's treated as a stanza which is unused |
| 2025-05-01 22:36:00 +0200 | <sim590> | tomsmeding: I see. |
| 2025-05-01 22:35:51 +0200 | <geekosaur> | btw that error is detected better in 3.14 |
| 2025-05-01 22:35:38 +0200 | <tomsmeding> | what cabal parses your `packages .` line to instead in that case, no clue |
| 2025-05-01 22:35:25 +0200 | <tomsmeding> | sim590: if there's no cabal.project (and a cabal.project.local is not a cabal.project), then the `packages:` line is not required |
| 2025-05-01 22:35:03 +0200 | <tomsmeding> | in general, in cabal.project* files, clauses which directly take arguments have a `:`, and headings which contain further keys with values have no `:` |
| 2025-05-01 22:34:58 +0200 | <sim590> | Aight. It's funny that just renaming it to `cabal.project.local` works though ? |
| 2025-05-01 22:34:42 +0200 | <EvanR> | step up your game |
| 2025-05-01 22:34:41 +0200 | <sim590> | Damn |
| 2025-05-01 22:34:33 +0200 | <geekosaur> | as usual |
| 2025-05-01 22:34:20 +0200 | <tomsmeding> | too slow |
| 2025-05-01 22:34:16 +0200 | <geekosaur> | no colon on the packages line? |
| 2025-05-01 22:34:09 +0200 | <tomsmeding> | sim590: missing the `:` after `packages` |
| 2025-05-01 22:33:54 +0200 | <sim590> | https://paste.debian.net/1372746/ |
| 2025-05-01 22:33:41 +0200 | <tomsmeding> | post the contents of your cabal.project file? |
| 2025-05-01 22:33:34 +0200 | <tomsmeding> | okay good |
| 2025-05-01 22:33:30 +0200 | <sim590> | The version of the cabal binary is 3.12.1.0 |
| 2025-05-01 22:33:29 +0200 | <tomsmeding> | ah |
| 2025-05-01 22:33:21 +0200 | <sim590> | tomsmeding: sorry. I thought you meant the version of the file. |
| 2025-05-01 22:32:57 +0200 | <tomsmeding> | 3.12.1.0 is recommended, 3.14.2.0 is latest |
| 2025-05-01 22:32:46 +0200 | <tomsmeding> | sim590: that is ancient, please upgrade now |
| 2025-05-01 22:32:36 +0200 | <EvanR> | shouldn't have named your file `cabal.project |
| 2025-05-01 22:32:35 +0200 | <sim590> | 3.0 |
| 2025-05-01 22:32:28 +0200 | <tomsmeding> | what is your cabal version? |
| 2025-05-01 22:32:25 +0200 | <sim590> | Always |
| 2025-05-01 22:32:21 +0200 | <sim590> | Soo I build with `v2-build`. |
| 2025-05-01 22:32:08 +0200 | <sim590> | And if I just change the name to `cabal.project.local`, then it works.. |
| 2025-05-01 22:31:54 +0200 | <tomsmeding> | wat |
| 2025-05-01 22:31:52 +0200 | <sim590> | Yeah |
| 2025-05-01 22:31:46 +0200 | <tomsmeding> | and `cabal build` gives `There is no <pkgname>.cabal package file or cabal.project file.`? |
| 2025-05-01 22:31:22 +0200 | <tomsmeding> | oh |
| 2025-05-01 22:31:18 +0200 | <sim590> | `ls .` yields `cabal.project CHANGELOG.md dht.data dht.data_port.txt dhtrunner-commit.msg dist-newstyle docker LICENSE opendht-hs.cabal README.md src todo.txt`. |
| 2025-05-01 22:31:01 +0200 | <tomsmeding> | cabal.project, not project.cabal |
| 2025-05-01 22:30:27 +0200 | <sim590> | While `I'm not though.. The `opendht-hs.cabal` and the `project.cabal` files are both in the current directory. |
| 2025-05-01 22:30:17 +0200 | <tomsmeding> | the `.` is a path to a directory, relative to the cabal.project file, where cabal expects to find a .cabal file |
| 2025-05-01 22:30:16 +0200 | dhil | (~dhil@openvpn-125-1069.inf.ed.ac.uk) (Ping timeout: 276 seconds) |