Esy: Exception when trying to rename file

[rdavison]

esy version: Latest master: https://github.com/esy/esy/tree/093a20b6441d25f44c4427e66ed136adb0569d0c

Operating System: Ubuntu 18.04

Issue: Internal error

Package.json

Actual behavior:

ubuntu@ip-10-0-0-67:~/project$ ../esy/bin/esy
info esy 0.6.0 (using esy.json)
info fetching: done
error command failed: 'unzip' '-q' '-d' '/tmp/esy-786e00' '/home/ubuntu/project/_esy/default/dist/6775c2cfb7a0ccff940fdb48169749f1'
      stderr:

      stdout:

error command failed: 'unzip' '-q' '-d' '/tmp/esy-a18c18' '/home/ubuntu/project/_esy/default/dist/a758edfe7999021ab82e30b43f3805a3'
      stderr:

      stdout:

error: error running command
  unpacking @opam/camlzip@opam:1.07
  installing @opam/camlzip@opam:1.07
esy: exiting due to errors above

ubuntu@ip-10-0-0-67:~/project$ sudo apt install unzip

ubuntu@ip-10-0-0-67:~/project$ ../esy/bin/esy
info esy 0.6.0 (using esy.json)
.... fetching @opam/yaml@opam:2.0.0esy: internal error, uncaught exception:
     Unix.Unix_error(Unix.ENOTEMPTY, "rename", "/home/ubuntu/project/_esy/default/tmp/esy-83e8c8")
     Raised at file "esy-lib/RunAsync.re", line 13, characters 2-51
     Re-raised at file "esy-lib/RunAsync.re", line 13, characters 2-51
     Re-raised at file "src/core/lwt.ml", line 2998, characters 20-29
     Called from file "src/unix/lwt_main.ml", line 26, characters 8-18
     Called from file "esy-lib/Cli.re", line 263, characters 9-28
     Called from file "cmdliner_term.ml", line 25, characters 19-24
     Called from file "cmdliner.ml", line 25, characters 27-34
     Called from file "cmdliner.ml", line 116, characters 32-39

Expected behavior:

No exception

Additional steps to reproduce:

[leematos]

I ran into a problem like this and I think it was due to a partial run that failed leaving behind the _esy directory. I blew that away ( rm -rf _esy) and then re-ran the esy install that was giving me problems and it worked

[andreypopp]

should be fixed in 494e5bd8682b967445d0ce94e27ba8a41d9a7fb1 nightly is building

[andreypopp]

Should be fixed with 0.6.4

[purplezimmermann]

I can confirm that it's definitely fixed in 0.6.4 :) Thanks @andreypopp