| 15 Mar 2026 |
eveeifyeve | * See https://github.com/opentracing/specification/issues/163 for more info | 13:50:38 |
sterni (he/him) | well i mean if you still have an opentracing compatible server and client it will continue to work the same as it used to | 13:55:51 |
eveeifyeve | Lightstep has been deprecated/archived so that can be removed. I have also opened up an issue upstream: https://github.com/kim/opentracing/issues/55 | 13:56:28 |
sterni (he/him) | i agree it doesn't make sense to keep maintaining this stuff, but it's also not like anything bad is going to happen if it's still around | 13:56:45 |
eveeifyeve | But again in nixpkgs, we should not keep stuff that seems like it will go unmaintained in nixpkgs. | 14:06:02 |
eveeifyeve | One reason to remove the opentracing stuff is unmaintained, https://github.com/NixOS/rfcs/blob/master/rfcs/0180-broken-package-removal.md#unmaintained-packages | 14:37:36 |
sterni (he/him) | that definition doesn't even have anything to do with upstream maintenance | 15:54:51 |
aiya | Redacted or Malformed Event | 18:55:02 |
aiya | Redacted or Malformed Event | 18:55:13 |
| 16 Mar 2026 |
maralorn | sterni: If we switch to nightly that means going to ghc 9.12, right? | 10:35:06 |
maralorn | Is that safe in regards to the whole miscompilation thingy? | 10:35:22 |
maralorn | e.g. do we maybe want to wait for 9.12.4? | 10:35:36 |
sterni (he/him) | We patched that in 9.12.3, but we could also wait for 9.12.4 | 10:35:48 |
sterni (he/him) | Maybe it is sensible to wait for the next HLS release (which is coming soon right?) and the update | 10:36:47 |
maralorn | I don’t know. I am not aware of immediate plans. | 10:41:29 |
maralorn | It seems likely that they would want to make a release after 9.12.4 to provide binaries. | 10:41:48 |
maralorn | But I also wouldn’t be other than from it being discussed on the hls matrix channel. | 10:44:38 |
sterni (he/him) | I just saw new versions of lsp and lsp-types so I assumed that was the reason | 10:44:58 |
sterni (he/him) | in any case, most stuff I had on my mind we can do with LTS is done, what remains are things like pandoc 3.9 which are probably best addressed by jumping to nightly | 10:46:42 |
sterni (he/him) | Also if anyone is interested in trying out 9.12.4-rc1 https://github.com/NixOS/nixpkgs/pull/500108 | 11:10:27 |
sterni (he/him) | alexfmpe: this was on darwin, right? https://github.com/NixOS/nixpkgs/pull/497811#issuecomment-4019565283 | 17:34:15 |
alexfmpe | aaah yeah | 22:10:03 |
alexfmpe | I forgot that threw off regen script | 22:10:13 |
eveeifyeve | I experienced this as well in this pr: https://github.com/NixOS/nixpkgs/pull/499983#issuecomment-4062916058 | 22:39:11 |
eveeifyeve | * I forgot to mention this, It's not just that pr is linked it's across globally: https://github.com/NixOS/nixpkgs/pull/499983#issuecomment-4062916058 | 22:40:10 |
eveeifyeve | * I forgot to mention this, It's not just that pr is linked it's across globally, because I was happened to reproduce it.
Ref: https://github.com/NixOS/nixpkgs/pull/499983#issuecomment-4062916058 | 22:40:32 |
alexfmpe | heh you barely missed 500k | 22:44:25 |
| 18 Mar 2026 |
Alex | It seems that we have a regression in pkgsCross.riscv64.buildPackages.ghc:
error: In file included from /nix/store/77digc4i0ny4i31cwns7zpirak96np5r-libffi-riscv64-unknown-linux-gnu-3.5.2-dev/include/ffi.h:84,
from FFI.hsc:33:
/nix/store/77digc4i0ny4i31cwns7zpirak96np5r-libffi-riscv64-unknown-linux-gnu-3.5.2-dev/include/ffitarget.h:36:2: error: #error "libffi was configured for a RIS
C-V target but this does not appear to be a RISC-V compiler."
36 | #error "libffi was configured for a RISC-V target but this does not appear to be a RISC-V compiler."
| ^~~~~
(On latest nixpkgs-unstable)
sterni Is this known about?
We might need to bisect for the cause.
pkgsCross.riscv64.haskell.compiler.ghc94 still builds, but cross-compiling other Haskell packages has been a bit of a blind spot for me. | 02:27:59 |
Alex | * It seems that we have a regression in pkgsCross.riscv64.buildPackages.ghc:
error: In file included from /nix/store/77digc4i0ny4i31cwns7zpirak96np5r-libffi-riscv64-unknown-linux-gnu-3.5.2-dev/include/ffi.h:84,
from FFI.hsc:33:
/nix/store/77digc4i0ny4i31cwns7zpirak96np5r-libffi-riscv64-unknown-linux-gnu-3.5.2-dev/include/ffitarget.h:36:2: error: #error "libffi was configured for a RIS
C-V target but this does not appear to be a RISC-V compiler."
36 | #error "libffi was configured for a RISC-V target but this does not appear to be a RISC-V compiler."
| ^~~~~
(On latest nixpkgs-unstable)
sterni Is this known about?
We might need to bisect for the cause, assuming this ever worked.
pkgsCross.riscv64.haskell.compiler.ghc94 still builds, but cross-compiling other Haskell packages has been a bit of a blind spot for me. | 02:30:11 |
Alex | Reproducer: https://gist.github.com/colemickens/78af9a28c01b888726322ca6628b27f5 | 02:30:29 |