-
-
Notifications
You must be signed in to change notification settings - Fork 197
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Invalid symlinks on Windows #248
Comments
So, apparently there are 2 types of symlinks in Windows that are supported:
I have created a pull request. If you decide that actual symlinks will be OK instead of .ink shortcuts - feel free to pull it. |
I am experiencing the exact same problem here as you |
A progres... well i wouldn't say that... but is it dead? Also no i'm a bit bussy now so i don't know when i will sit by this - but in some time, i probably will! |
Oh sure, thank you very much! |
Hi, is there a fix for this by any chance? Maybe a temporary solution? |
I am really sorry to write that, my status, is still busy 😭😭 And official, branded, and tested solution for that is to be done "soon". BUT! Here is a nightly build of a PR #249 that I still need to review and test myself - but he says it works for him 💯 so you can test it too: https://github.com/TheLastGimbus/GooglePhotosTakeoutHelper/actions/runs/8412986115 |
Man, thanks for your hard work. Take the time you need. Thank you! |
v3.4.3, Windows 10
Command:
gpth-windoza.exe --copy --input .\Takeout\ --output .\OutTake2
Executed from root of E:\ drive.
All symlinks point towards
C:\ALL_PHOTOS
instead ofE:\OutTake2\ALL_PHOTOS
Same thing happens when I simply run the gpth-windoza via double clicking the executable and point to directories manually.
v3.4.1 works fine, tho symlinks are not relative.
The text was updated successfully, but these errors were encountered: