nD5Xjz has quit [Ping timeout: 245 seconds]
nD5Xjz has joined #nix-darwin
nD5Xjz has quit [Ping timeout: 258 seconds]
nD5Xjz has joined #nix-darwin
nD5Xjz has quit [Ping timeout: 246 seconds]
nD5Xjz has joined #nix-darwin
nikivi has quit [Quit: ZNC is awesome]
nikivi has joined #nix-darwin
nD5Xjz has quit [Ping timeout: 268 seconds]
nikivi has quit [Quit: ZNC is awesome]
nikivi has joined #nix-darwin
nD5Xjz has joined #nix-darwin
nikivi has quit [Quit: ZNC is awesome]
nikivi has joined #nix-darwin
kyren has quit [Remote host closed the connection]
periklis has joined #nix-darwin
<johnw> LnL: that's what happens when I try to build ghc-8.4.4 on unstable right now; have you seen this?
philr has quit [Ping timeout: 246 seconds]
<LnL> it starts building so I presume it's broken
<LnL> the channel only blocks on pkgs.ghc
kyren has joined #nix-darwin
jtojnar has joined #nix-darwin
periklis has quit [Ping timeout: 250 seconds]
<LnL> I forgot how much weird stuff you find with sandboxing, "Use /bin/pwd uniformly, not pwd."
<johnw> they broke ghc-8.2.2 as well
<johnw> so, is there a mechanism by which this red flag gets raised to whomever broke it?
<LnL> not really, best to create an issue
<LnL> depending on how large the diff between builds it you might be able to determine what broke it
<johnw> already an issue for it: #55662
<{^_^}> https://github.com/NixOS/nixpkgs/issues/55662 (by peti, 1 day ago, open): ghc 8.4.4 broken by recent `staging` merge
copumpkin has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
philr has joined #nix-darwin