| 25 Aug 2025 |
 fzakaria | the file parsing I have kept the same for now and this tackles mostly SCP | 04:40:26 |
 emily | I don't think Nix treats file://a/b as relative or file:/a/b as absolute currently | 04:41:28 |
| emily | file://relative/repo is the path /repo on the authority relative, and file:/a/b is I think RFC-compliant but does not work | 04:43:29 |
| emily | at least a doc/tests issue, since the URL described as relative isn't | 04:44:04 |
| fzakaria | I wrote two tests for now.
If we file a bug I can augment the parser | 04:44:52 |
| fzakaria | // Relative path (becomes file:)
{"relative/repo", "file://relative/repo"},
// Already file: scheme
{"file:/var/repos/x", "file:/var/repos/x"},
| 04:44:54 |
 Sergei Zimmerman (xokdvium) | In reply to @fzakaria:one.ems.host
the file parsing I have kept the same for now and this tackles mostly SCP Either way that looks like a bug. file urls must contain absolute paths https://datatracker.ietf.org/doc/html/rfc8089#section-2 | 06:24:20 |
 magic_rb | https://github.com/NixOS/nix/pull/13437 dumb question, cause from the description its not obvious. But this makes follows recursive right | 13:13:03 |
| fzakaria | so should it fail ? | 14:24:39 |
| fzakaria | or just force relative paths to become absolute ?
Can we handle this in a separate PR after and discuss? | 14:24:52 |
