Hi everyone,
I encountered a bug when trying to install a dependency in my project using Sysand:
error: failed to install project urn:kpar:sysmod:
installation error: io error: The system cannot move the file to a different disk drive. (os error 17)
I’m working on Windows and my project is residing on the D-drive. I suppose Sysand downloads the dependency and temporarily places it on the C-drive, and then when trying to move it to the other drive it fails?
Greetings,
Jasper
Thanks for reporting this! That is correct, we rely extensively on the system temporary directory for downloading and verifying projects before installation. We will look into this and figure out why the move fails.
@jbussemaker I believe this issue is now fixed. Please try out the 0.0.4 release (here) to see if it solves your problem.
For reference, a ticket was created here.
Thank you! It works perfectly fine now 
I noticed another issue: in the SysandLock.toml file the project is declared using its absolute path:
[[project.source]]
editable = 'C:\<path>\<to>\<project>'
I think this shouldn’t be the case, and might even break stuff when sharing the project through for example git.
Thanks, that definitely needs to be fixed. We’re currently working on a significant rework of the lock file design and implementation. We will fix it together with all the other upcoming changes. For now, I created a bug report here: Lockfile uses absolute path for editable entries. · Issue #85 · sensmetry/sysand · GitHub
@jbussemaker The bug related to editable paths should be fixed in the latest version: Release v0.0.5 · sensmetry/sysand · GitHub