ln: failed to create symbolic link 'latest' -> '': No such file or directory

[baskuit]

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  8318  100  8318    0     0   143k      0 --:--:-- --:--:-- --:--:--  145k
[night.zig] Starting fresh installation...

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 37843  100 37843    0     0   134k      0 --:--:-- --:--:-- --:--:--  135k
[night.zig] Deploying latest nightly...

[night.zig] Fetching nightly tar ball...

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0Warning: Failed to open the file 
Warning: /tmp/tmp.cgcGbJW3N5/zig-linux-x86_64-0.12.0-dev.1859+27d4bf753.tar.xz:
Warning:  No such file or directory
  0 44.9M    0 15912    0     0   117k      0  0:06:30 --:--:--  0:06:30  118k
curl: (23) Failure writing output to destination
[night.zig] Fetch completed.

/tmp/tmp.cgcGbJW3N5/zig-linux-x86_64-0.12.0-dev.1859+27d4bf753.tar.xz
tar: /tmp/tmp.cgcGbJW3N5/zig-linux-x86_64-0.12.0-dev.1859+27d4bf753.tar.xz: Cannot open: No such file or directory
tar: Error is not recoverable: exiting now
[night.zig] Extracting nightly tar ball...

tar: /tmp/tmp.cgcGbJW3N5/zig-linux-x86_64-0.12.0-dev.1859+27d4bf753.tar.xz: Cannot open: No such file or directory
tar: Error is not recoverable: exiting now
[night.zig] Extraction completed.


[night.zig] Configuring latest nightly...

ln: failed to create symbolic link 'latest' -> '': No such file or directory

I'm on Kubuntu 23.04. sudo does not help.

[jsomedon]

Your log shows that the ln command failed because nightly tar ball was not fetched. I just tried on my machine and it is successfully fetching tar ball. So my guess is that it was some network error that you had back then.

Hope that helps.