Also I have to wait for the final ghc alpha to drop (sometime this week iirc) to test it, Not only because of bytestring, but because I think a buggy release of unix was in the last one.

On Sat, Sep 16, 2023 at 2:18 PM Brandon Allbery <allbery.b@gmail.com> wrote:
This has been going on for long before bytestring-0.12. I can try building with ghc alpha but last I checked we still had other problems with it in xmonad-contrib (https://github.com/xmonad/xmonad-contrib/issues/826).

On Sat, Sep 16, 2023 at 2:12 PM Tomas Janousek <tomi@nomi.cz> wrote:

Hi,

On Sat, Sep 16, 2023 at 11:36:21AM -0400, Brandon Allbery wrote:

Anyone know what this is about? I get it weekly, presumably because I
forked the xmonad-contrib repo.
[…]
Packdeps: Some jobs were not successful

Yeah, I keep getting it as well: https://github.com/xmonad/xmonad-contrib/actions/runs/6204986546/job/16847665048

I think it's trying to tell us that our bounds exclude bytestring 0.12 which is now available in Hackage. What we need to do is make sure xmonad builds and works with this version, and update the bounds.

I'm not keeping up with the Haskell ecosystem these days so I don't know how to actually do that. Last time I checked, bytestring was a "boot" package shipped with GHC, so perhaps we'd need to test with GHC HEAD? Or can you ask cabal to just pull it and build it?

--

Tomáš "liskin" ("Pivník") Janoušek, https://lisk.in/



--
brandon s allbery kf8nh


--
brandon s allbery kf8nh
allbery.b@gmail.com