| 4 Apr 2024 |
 sorear | I specifically want to avoid a policy which requires no public errata, because that will just push us towards vendors that treat all errata as trade secrets | 18:33:04 |
 Pratham Patel (you can mention me) | me not know that, I’ll look into that tomorrow | 18:34:07 |
 Alex | In reply to @hive:the-apothecary.club
catch2-3.5.2-riscv64-linux I've already encountered this build failure. Here's a fix (probably suboptimal, but it works). | 19:18:21 |
 Dr. Worm | thanks :fold | 19:19:44 |
| Dr. Worm | * thanks 🙏 | 19:19:49 |
| Alex | (The fix is based on skeuchel's PR. You could probably use that PR directly if you use a custom Nixpkgs repository; I don't.) | 19:20:37 |
| Dr. Worm | i don't either | 19:20:50 |
|  silvanshade joined the room. | 19:42:09 |
| 5 Apr 2024 |
|  liberodark joined the room. | 07:46:35 |
| liberodark | Hi | 11:27:42 |
| liberodark | If you need to work on RISC-V servers, don't hesitate to ask me, I will provide some for free. | 11:28:51 |
| liberodark | being also a small user of nixos it is important to me that everyone can work in good conditions. To improve this architecture. | 11:30:25 |
| Pratham Patel (you can mention me) | Nice work, thank you
- a NixOS user | 11:31:00 |
| Alex | In reply to @liberodark:matrix.org
If you need to work on RISC-V servers, don't hesitate to ask me, I will provide some for free. Are you able to share the specs of those servers? Esp. CPU model | 11:31:17 |
| liberodark | I don't want to advertise here so I won't put the link to my RISC-V project here, I don't want to spam but don't hesitate to ping me. | 11:31:28 |
| liberodark | In reply to @alex:tunstall.xyz
Are you able to share the specs of those servers? Esp. CPU model Yes | 11:31:34 |
| liberodark | Im go to share C920 C910 & JH7110 | 11:31:56 |
| liberodark | * Im go to share SoC : C920 C910 & JH7110 | 11:34:06 |
| liberodark | Currently it is Debian which is offered on my infrastructure.
But I can make the C910 and JH7110 completely available to you in case you want to have nixos on it, which I would understand. | 11:35:25 |
| liberodark | If of course it can be useful to you. | 11:36:28 |
| liberodark | Best Regards | 11:36:31 |
|  @lsbgkdlpqhswnccwnabaflt:matrix.org joined the room. | 17:34:09 |
| Dr. Worm | Alex have you encountered an issue with openldap-2.6.7-riscv64-linux | 23:36:17 |
| 6 Apr 2024 |
| Alex | In reply to @hive:the-apothecary.club
Alex have you encountered an issue with openldap-2.6.7-riscv64-linux I don't appear to have built it recently.
(At the moment I'm focused on building GHC, so it's unlikely I've built anything outside of the closure of GHC or a full NixOS system.) | 00:41:34 |
| Dr. Worm | alright | 00:41:53 |
| Dr. Worm | as far as i know this is something you would need for a full nixos system but i could be wrong | 00:42:34 |
| Alex | In reply to @hive:the-apothecary.club
as far as i know this is something you would need for a full nixos system but i could be wrong Nope.
[nixos@nixos:~]$ nix-store -qR /run/current-system | grep -we openldap
[nixos@nixos:~]$
| 00:43:54 |
| Dr. Worm | rats | 00:44:54 |
| Alex | (And this system is on a recent nixos-unstable commit) | 00:44:56 |
| Dr. Worm | is there a way to see what it's being required by ? | 00:46:14 |
