-
Notifications
You must be signed in to change notification settings - Fork 1
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
Filenames longer then 99 chars seem not to be implemented properly ... #4
Comments
@DeepDiver1975 can't confirm:
104 characters long, no errors |
uncomment this one and see it failing - https://github.com/owncloud/TarStreamer/blob/master/tests/Streamer.php#L70 |
@DeepDiver1975 wrong repo ;)
|
t.php:
|
Okay - please open a PR which tests the proper behavior - THX |
argh
|
the question is whether tar for macs is capable to read long filenames in a POSIX way, via 'L'-headers |
I just tried the file name "Team Week Presentation July 2015-12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970.odp.zip" and "Team Week Presentation July 2015-12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970.odp", downloaded as file, archive (with 2 files), archive (with 1 file), had no problem with any of them. Mac with OS X El Capitan, Safari browser |
@cmonteroluque yes. There are two ways of handling long names. We use header of 'x' type for that. |
We need to find out of 'x' type is supported on MacOS - results are to be expected here owncloud/core#19318 (comment) As a result we either add 'x' support to Archive_Tar or 'L' headers to the tarstreamer |
It is done yesterday. Tests with Archive_Tar are passing locally. Not pushed yet, I'm cleaning the code. |
L-headers support #6 |
No description provided.
The text was updated successfully, but these errors were encountered: