2024/10/25

Newest at the top

2024-10-25 23:23:49 +0200Zer000(~02@64.137.132.10) Zer000
2024-10-25 23:23:33 +0200vglfr(~vglfr@2607:fb91:876:ccd6:ac39:c391:b0e4:8435) (Ping timeout: 248 seconds)
2024-10-25 23:20:04 +0200Everything(~Everythin@178-133-29-214.mobile.vf-ua.net)
2024-10-25 23:19:51 +0200Enrico63(~Enrico63@cmbg-18-b2-v4wan-168328-cust3951.vm17.cable.virginm.net) (Quit: Client closed)
2024-10-25 23:19:24 +0200vglfr(~vglfr@2607:fb91:876:ccd6:ac39:c391:b0e4:8435) vglfr
2024-10-25 23:19:12 +0200euleritian(~euleritia@ip4d16fc38.dynamic.kabel-deutschland.de)
2024-10-25 23:18:55 +0200euleritian(~euleritia@176.1.224.47) (Read error: Connection reset by peer)
2024-10-25 23:18:43 +0200vglfr(~vglfr@c-73-250-25-113.hsd1.md.comcast.net) (Ping timeout: 245 seconds)
2024-10-25 23:17:03 +0200merijn(~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 246 seconds)
2024-10-25 23:15:26 +0200 <Enrico63> Thanks!
2024-10-25 23:14:12 +0200euleritian(~euleritia@176.1.224.47)
2024-10-25 23:14:05 +0200 <tomsmeding> the `any.` is essential
2024-10-25 23:13:58 +0200 <tomsmeding> that should work without the local vendored-in happy
2024-10-25 23:13:47 +0200 <tomsmeding> Enrico63: there is a "neater" suggestion over from #hackage: add 'constraints: any.happy == 2.0.2' to cabal.project
2024-10-25 23:13:22 +0200 <tomsmeding> that was already suggested by sm :)
2024-10-25 23:13:18 +0200 <Enrico63> Now I can go to bed :)
2024-10-25 23:13:12 +0200 <tomsmeding> monochrom: no, cabal takes happy from its store, not from $PATH
2024-10-25 23:13:09 +0200 <Enrico63> And everybody who participated, really
2024-10-25 23:12:51 +0200 <Enrico63> Thank you very much tomsmeding and mauke
2024-10-25 23:12:43 +0200merijn(~merijn@128-137-045-062.dynamic.caiway.nl) merijn
2024-10-25 23:12:40 +0200 <monochrom> Wouldn't it be sufficient to just manually perform a `cabal install --constraint='happy < 2.1' happy` as a preparation step?
2024-10-25 23:12:12 +0200 <Enrico63> I see :)
2024-10-25 23:10:31 +0200 <tomsmeding> so this can be worked around either by downgrading happy or by fixing gtk2hs
2024-10-25 23:10:20 +0200 <tomsmeding> Enrico63: gtk2hs is not compatible with happy-2.1 but does not constrain happy on <2.1
2024-10-25 23:09:57 +0200 <Enrico63> tomsmeding, but given you say that the problem is not happy but gtk..., does that mean that I could have `cabal get`ed and added to cabal.project that instead?
2024-10-25 23:09:18 +0200Enrico63(~Enrico63@cmbg-18-b2-v4wan-168328-cust3951.vm17.cable.virginm.net) Enrico63
2024-10-25 23:07:49 +0200 <tomsmeding> with this commit https://github.com/visq/language-c/commit/32763a1a57e427eb3ab51689e8818db333753301
2024-10-25 23:07:47 +0200Enrico63(~Enrico63@cmbg-18-b2-v4wan-168328-cust3951.vm17.cable.virginm.net) (Quit: Client closed)
2024-10-25 23:07:38 +0200 <tomsmeding> yep language-c had the same issue but that's been fixed in language-c-0.9.4
2024-10-25 23:07:17 +0200 <Enrico63> (unlucky you, ahahah)
2024-10-25 23:07:08 +0200 <Enrico63> Wow, we are twins, mauke
2024-10-25 23:07:05 +0200 <mauke> jinx
2024-10-25 23:06:59 +0200 <tomsmeding> lol
2024-10-25 23:06:55 +0200 <Enrico63> https://github.com/gtk2hs/gtk2hs/issues/335
2024-10-25 23:06:54 +0200 <mauke> https://github.com/gtk2hs/gtk2hs/issues/335
2024-10-25 23:06:06 +0200 <tomsmeding> not happy
2024-10-25 23:06:04 +0200 <tomsmeding> but I now believe the proper package to fix is gtk2hs-buildtools
2024-10-25 23:05:54 +0200 <tomsmeding> and yes, the path is indeed: wait for fix, then undo these changes and build again
2024-10-25 23:05:48 +0200 <mauke> Enrico63++
2024-10-25 23:05:41 +0200 <Enrico63> yayyyy
2024-10-25 23:05:34 +0200 <tomsmeding> Enrico63: it did
2024-10-25 23:05:22 +0200 <Enrico63> tomsmeding, please tell me that my suggestion of using cabal.project contributed 1% to your ability to find the solution, so I go to sleep with an aftertaste of accomplishment
2024-10-25 23:05:10 +0200 <Enrico63> Ok, it worked!
2024-10-25 23:04:30 +0200 <Enrico63> (I'm assuming the fix works, but I'm still in the process. Apparently I have to apply this workaround to xmobar (the program), xmobar (my xmobar.hs setup repo), xnobar (a plugin I wrote, check it out :D), and who knows, maybe the config of xmonad broke!
2024-10-25 23:04:01 +0200synchrom1(~john@139.180.95.1) (Quit: WeeChat 4.0.5)
2024-10-25 23:03:00 +0200 <Enrico63> tomsmeding I suppose now I only have to wait for the fix for happy to be available, then delete the local version of it, remove that item from the list of cabal.project, and recompile, right?
2024-10-25 23:02:58 +0200kimiamania(~924ba01d@user/kimiamania) kimiamania
2024-10-25 23:02:35 +0200kimiamania(~924ba01d@user/kimiamania) (Quit: PegeLinux)
2024-10-25 23:02:18 +0200merijn(~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 272 seconds)
2024-10-25 23:01:08 +0200michalz(~michalz@185.246.207.203) (Remote host closed the connection)