-
Notifications
You must be signed in to change notification settings - Fork 771
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
"Can't restore time" when extracting on Windows 8.1 #772
Comments
|
Can also do this if extracting to tmpfs on FreeBSD 11. At first I did it in tmpfs, got rid of that and still got the error. |
|
so I just hit this again, and am quite surprised to find my own post. again not finding it either ;-) |
|
Well, there are three different cases when this message is set by archive_write_disk_windows. If the |
|
It doesn't seem to be Windows-specific based on this comment. |
|
This happens when I tried to 'tar xzf' on exFAT. Works fine on NTFS |
|
Linking this ticket to another which has the goal of making this message non-fatal, since it is regarded in some parts of the code as a "warning" |
|
@sklaw is right. |
|
I can confirm it gives the error on exFAT but works fine on NTFS. I just wanted to add a note: Using Windows 10 PowerShell I'm perfectly able to change the Last Modified time on an exFAT fs, while |
|
This issue is still relevant on Windows 10, and for me has had the downstream effect of preventing me from being able to build OpenCV on an exFAT drive. Is there any idea why this would happen specifically with exFAT? |
|
I ran into this issue in a GitHub workflow that's based on macOS 12, so this does not appear to be limited to Windows. Curiously, the workflow is non-deterministic: it occurs only sporadically. Update: My problem is discussed in this issue: actions/runner-images#2619 Passing the flag |
|
On Windows, you need to compile on an NTFS disk instead of a FAT32 or exFAT disk, then cmake can perform the extract. I guess there's an issue to extract on a FAT32 or exFAT disk. |
Something with this zip file, md5: 53c1c32f8f4730538a6d3e9eb5d8589e:
This has also been seen with some Boost tarballs, so it isn't zip-specific (I'll try and find the tarball we had issues with).
Cc: @robertmaynard
The text was updated successfully, but these errors were encountered: