-
Notifications
You must be signed in to change notification settings - Fork 3
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 mount .tar, .tar.bz2, .tar.gz #43
Comments
So ... I suppose then that it is something with wrong or better unexpected mime-types. I would suggest to start with uncompressed tar archives, although both -- First: do you have that archive information in the details tab at all? If so, what is the mime type and archive format, and which archive backend is in use? Please note that If there is no archive tab in the details view, then the issue is that the mime type is not accepted by files_archive. Then it would probably good to augment the settings sections by the supported mime types and archive backends to ease debugging (would probably a good idea anyway). |
Well, this |
No, Here I attach it. (unfortunately github doesn't allow tar files, so it's zipped, inside there's the test.tar file) |
Perhaps the |
Indeed! I've tried with a test.php.tar, and the message was "Entry hp does not exist".
I don't think so:
|
I am trying to find the piece of code stating 'Entry xt does not exist' but am not able to find it. The exception should also be logged to the Nextcloud log, can you please look it up? I am not sure were this exception is thrown . Thanks. |
Please see my previous message, the Here it is in the logs:
|
Oh well. It is However, this means the error messages is generated by the phar extension. Ok. The way I would go would be to edit that TarByPhar.php and throw out log messages in order to check where things break. E.g. in line 181 it would be interesting to know whether the there mentioned parametere |
Is the data directory also a symlink which maybe confuses the phar extension? |
Yes. That is the problem. Or the cause of the manifestation of whatever problem we really have. I have just now replaced my data directory by a symlink like this:
Then everything else still works, but the phar-extension does not seem to like this change. The error message is slightly different:
|
You could try to replace your symlink by a bind mount, just to check if this changes anything. The phar-extension problems could perhaps be cured by using |
The nextcloud-app-files-archive/lib/Toolkit/Service/ArchiveService.php Lines 231 to 234 in 44baceb
by
|
I was already doing that! And it works now!!!! Thanks a lot! I hope there's no side effect. Now, I can't mount |
Oops. Still? Neither can I on my laptop test setup, but it works @home in another instance. The actual backend driver in use is then indeed TarByPear, no longer TarByPhar. Please leave the issue open for the moment; the topic is correct although different things may cause the problems. |
Ok, @home I can mount .tar.xz, .tar.bz2, but .tar.gz is not recognized. @work with my notebook neither of the archives works, and .tar.gz is not recognized. This means I have one system where I can reproduce the problem locally, so it should not be too difficult to solve. However, not now. I'll come back to it later. |
Nextcloud (at least my instance) likes to classify This does not address the problem that on some systems |
Well, according to https://www.rfc-editor.org/rfc/rfc9110.html#name-gzip-coding "x-gzip" and "gzip" are equivalent. |
Yes "of course", but that does not help if Nextcloud returns one flavour and your app expects the other. However, I think that the latest pre-release fixes the archive-not-detected problems ( Oops. I missed that realpath() change in the latest pre-release. |
Ok, about |
The alchemy/zippy bug got its work around in 761b4bf until wapmorgan/UnifiedArchive#44 has been merged "upstream". Can you please re-check whether perhaps now it works for you also? Why UA chooses AlchemyZippy on my laptop for |
Hi, |
Mmh. Ok then: are there any problems remaining? (restricting ourselves to the problems you mentioned in this issue ;) ) |
Of the file formats I've tried: |
No, the xz stuff just also works. But please let me double check this later. |
Ok. At home I have lzma installed, not on the laptop. If we look at the support matrix locally (no on the web, I must filed a bug report wapmorgan/UnifiedArchive#45) we have the following output:
Actually going back to you initial issue #42 it would perhaps be good to either document the use of
Installing the lzma php extension seems to be the only option at the moment. |
... and yes, there must be a test and a suitable error message for this case ... |
6d4d4c1 is an attempt to have a less unfriendly error handling. The error text is displayed as toast and also contains some installation instructions. Perhaps one could also provide the summary generated by the system:drivers and system:formats command on the admin settings page. |
Ok, installing How all this "mounting" works. Is it really extracted on demand or it's extracted on a temp dir until it's unmounted? |
I couldn't run |
composer install or require could have helped for that. Anyhow, the current state of the affair is that I have hopefully improved the error message: and in the admin settings there is the support matrix and driver overview (by executing the console commands without console, Symfony supports this via its BufferedOutput class, https://symfony.com/doc/current/console/command_in_controller.html: |
Hi, openning new issue here and closing #42 .
Basically I am unable to mount any .tar (compressed or not) file but it works using directly the command line.
I've tried this that works ok:
When trying mounting in nextcloud, it results in a 500 http code.
zip files work ok and can be mounted.
.tar.xz files don't work for me, even using UnifiedArchive directly.
The text was updated successfully, but these errors were encountered: