| 20 Jul 2025 |
 raitobezarius (DECT: 7248) | on the host? | 15:02:02 |
| raitobezarius (DECT: 7248) | i mean | 15:02:12 |
| raitobezarius (DECT: 7248) | do you have ipv4 connectivity on the host? | 15:02:16 |
| raitobezarius (DECT: 7248) | for reference, this is the host builder | 15:02:32 |
| raitobezarius (DECT: 7248) | [root@build01:~]# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host noprefixroute
valid_lft forever preferred_lft forever
2: host0@if11: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 3e:b0:ee:45:01:14 brd ff:ff:ff:ff:ff:ff link-netnsid 0
inet6 2001:bc8:38ee:100:8000::20/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::3cb0:eeff:fe45:114/64 scope link proto kernel_ll
valid_lft forever preferred_lft forever
| 15:02:34 |
| raitobezarius (DECT: 7248) | [root@build01:~]# ip -6 r
64:ff9b::/96 via 2001:bc8:38ee:100::100 dev host0 proto static metric 1024 pref medium
(ipv4 comes from there) | 15:02:54 |
 aloisw | Ah that might do it, I do have ipv4 on the host. | 15:03:06 |
| aloisw | Right, removing all IPv4 addresses (except 127.0.0.1/8 on lo) makes IPv4 connectivity go away in the sandbox too. | 15:05:29 |
| raitobezarius (DECT: 7248) | which makes sense to some extent | 15:06:25 |
| raitobezarius (DECT: 7248) | but creates that very funny situation | 15:06:29 |
| raitobezarius (DECT: 7248) | where IPv4-only localhost services are now unreachable | 15:06:39 |
| raitobezarius (DECT: 7248) | a workaround is to always add 169.254.1.1 to lo | 15:06:53 |
| raitobezarius (DECT: 7248) | alternatively pasta could heuristically recognize NAT64 prefixes and do the right thing | 15:07:40 |
| raitobezarius (DECT: 7248) | not so sure this is a good idea | 15:07:45 |
| aloisw | In reply to @raitobezarius:matrix.org
a workaround is to always add 169.254.1.1 to lo The arguments passed to pasta are not different, so this seems like a pasta issue? | 15:08:37 |
| raitobezarius (DECT: 7248) | yep | 15:11:50 |
| 21 Jul 2025 |
 jade_ | yippeee, time to reverse engineer how output-addressed store paths with references work. I could do IA but it's not truthful since Lix doesn't get to see the input as it's externally generated... | 19:00:41 |
| jade_ | * yippeee, time to reverse engineer how output-addressed store paths with references serialize in nix-store --export. I could do IA but it's not truthful since Lix doesn't get to see the input as it's externally generated... | 19:00:49 |
| jade_ | (I am building nix store paths directly with buck2(!) and jamming them directly into the store. they're to be used with builtins.fetchClosure ideally. hopefully we didn't delete enough CA code that we can't run that stuff anymore) | 19:01:46 |
| jade_ | actually it looks like the fixed-output derivations cannot have references thing is entirely at the builder layer? seemingly CA paths just are allowed to have references? | 19:12:35 |
| jade_ | * actually it looks like the fixed-output derivations cannot have references thing is entirely at the builder layer? seemingly output-addressed paths just are allowed to have references? | 19:12:44 |
| jade_ | .... oh. if you want to import random bullshit IA paths, you can't do it with nix-store --import. I wonder how I get around that. | 19:29:58 |
| jade_ | * .... oh. if you want to import random bullshit IA paths, you can't do it with nix-store --import. I wonder how I get around that because I have no reason to not be CA. | 19:30:19 |
| jade_ | ........... why did they do modulo hashing?! | 19:33:42 |
| jade_ | what is the purpose of that? | 19:33:48 |
| jade_ | "jade go read Eelco's thesis"
yeah okay it's in there | 19:34:14 |
| jade_ | page 144 | 19:34:22 |
| jade_ | oh! modulo hashes are identical if you prohibit self refs. lets go! | 19:34:45 |
| jade_ | * oh! modulo hashes are possibly identical if you prohibit self refs. lets go! | 19:35:09 |
| jade_ | oh no. okay so I have to implement a thing that either links to the nix implementation or implements the protocol, because nix-store --import doesn't support importing CA hashed paths. Either way I am quite displeased. | 19:39:45 |
