| 1 Apr 2024 |
 John Ericson | this failure | 18:52:52 |
 artemist | In reply to @Ericson2314:matrix.org
https://github.com/NixOS/nixpkgs/pull/298849 Alyssa Ross rhelmot I separated out the freebsd13 -> freebsd in a commit, can we PR that alone, hopefully to master? That sounds like a good first change, we can work on sandboxing more later. | 20:47:36 |
| artemist | In reply to @Ericson2314:matrix.org
rhelmot: in both the older versions of your PRs, and the latest rebase, I am getting
In file included from /nix/store/k5qq133jmgn1zck6npiw5q0j16m24wsr-libmd-1.1.0/include/sha.h:32,
from xinstall.c:66:
/nix/store/k5qq133jmgn1zck6npiw5q0j16m24wsr-libmd-1.1.0/include/sha.h:36:9: error: unknown type name 'SHA_CTX'
36 | typedef SHA1_CTX SHA_CTX;
| ^~~~~~~~
In file included from /nix/store/k5qq133jmgn1zck6npiw5q0j16m24wsr-libmd-1.1.0/include/sha256.h:32,
from xinstall.c:67:
/build/xinstall-bootstrap-filtered-src/lib/libnetbsd/sha2.h:38:10: fatal error: sha384.h: No such file or directory
38 | #include <sha384.h>
| ^~~~~~~~~~
compilation terminated.
*** Error code 1
Stop.
make: stopped in /build/xinstall-bootstrap-filtered-src/usr.bin/xinstall
error: builder for '/nix/store/9y57p11i78ibl1d032l1szjyhqjch15r-xinstall-bootstrap-14.0.drv' failed with exit code 1;
last 10 log lines:
> In file included from /nix/store/k5qq133jmgn1zck6npiw5q0j16m24wsr-libmd-1.1.0/include/sha256.h:32,
> from xinstall.c:67:
> /build/xinstall-bootstrap-filtered-src/lib/libnetbsd/sha2.h:38:10: fatal error: sha384.h: No such file or directory
> 38 | #include <sha384.h>
> | ^~~~~~~~~~
> compilation terminated.
> *** Error code 1
>
> Stop.
> make: stopped in /build/xinstall-bootstrap-filtered-src/usr.bin/xinstall
For full logs, run 'nix-store -l /nix/store/9y57p11i78ibl1d032l1szjyhqjch15r-xinstall-bootstrap-14.0.drv'.
I haven't seen this before, I'll test it | 20:47:51 |
| John Ericson | artemist: ah right you are working on all the nix bsd things too? | 20:58:51 |
| John Ericson | In reply to @artemist:mildlyfunctional.gay
That sounds like a good first change, we can work on sandboxing more later. In any event, if one of you could PR that first commit with the full rationale (I vaguely remember there being an issue about FreeBSD having a stable enough ABI or whatever after all, but I forgot) | 21:01:26 |
| John Ericson | In reply to @artemist:mildlyfunctional.gay
That sounds like a good first change, we can work on sandboxing more later. * In any event, if one of you could PR that first commit with the full rationale (I vaguely remember there being an issue about FreeBSD having a stable enough ABI or whatever after all, but I forget) that would be good | 21:01:34 |
| John Ericson | I don't have the information to write the rationale myself | 21:01:44 |
| John Ericson | * https://github.com/NixOS/nixpkgs/pull/298849 Alyssa Ross rhelmot I separated out the freebsd13 -> freebsd in a commit, can we PR that alone, hopefully to master rather than staging? | 21:01:54 |
| 2 Apr 2024 |
|  @lotte:chir.rs changed their profile picture. | 06:53:08 |
| @lotte:chir.rs changed their profile picture. | 07:32:47 |
|  Mic92 joined the room. | 13:23:27 |
|  stablejoy joined the room. | 13:31:14 |
| 3 Apr 2024 |
|  Alex K joined the room. | 20:47:56 |
| 4 Apr 2024 |
|  silvanshade joined the room. | 19:41:35 |
| 5 Apr 2024 |
 Anderson Torres | In reply to @Ericson2314:matrix.org
In any event, if one of you could PR that first commit with the full rationale (I vaguely remember there being an issue about FreeBSD having a stable enough ABI or whatever after all, but I forget) that would be good POLA?
https://docs.freebsd.org/en/books/handbook/glossary/ | 23:45:15 |
| Anderson Torres | > Principle Of Least Astonishment
> As FreeBSD evolves, changes visible to the user should be kept as unsurprising as possible. For example, arbitrarily rearranging system startup variables in /etc/defaults/rc.conf violates POLA. Developers consider POLA when contemplating user-visible system changes.
| 23:45:37 |
| Anderson Torres | * > Principle Of Least Astonishment
> As FreeBSD evolves, changes visible to the user should be kept as unsurprising as possible. For example, arbitrarily rearranging system startup variables in /etc/defaults/rc.conf violates POLA. Developers consider POLA when contemplating user-visible system changes.
| 23:46:00 |
| 8 Apr 2024 |
| John Ericson | hmm maybe | 02:40:43 |
| John Ericson | not sure | 02:40:44 |
 rhelmot | I think a more compelling proof is some of the stuff that they have kept around for compatibility | 02:41:54 |
| rhelmot | There are versions of syscalls which are compatible with FreeBSD 9 at least | 02:42:13 |
| rhelmot | Like the name is xxxxxx_compat9 or something | 02:42:34 |
| rhelmot | https://github.com/freebsd/freebsd-src/blob/main/sys/kern/syscalls.master | 02:53:49 |
| rhelmot | Oh oops this one is much more obviously compelling https://github.com/freebsd/freebsd-src/blob/main/sys/kern/syscalls.c | 02:59:54 |
| rhelmot | Based on the descriptions of the former I think you can turn off compat but it’s an opt out situation | 03:01:00 |
|  Levi joined the room. | 03:21:06 |
| Levi changed their display name from levigross to Levi. | 03:38:37 |
|  @cnx:loang.net joined the room. | 07:18:04 |
| @cnx:loang.net left the room. | 07:27:08 |
 dramforever | i got myself a yeelong 8089d laptop with a loongson 2f (mips) cpu in it | 16:33:53 |
