-
Notifications
You must be signed in to change notification settings - Fork 45
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
Update not possible: Out-of-path file extraction #52
Comments
yap exactly. |
Same problem here: Message":"Could not extract app recognize: Out-of-path file extraction {/volume1/@tmp/oc_tmp_aYHmf1-folder/recognize/node_modules/@tensorflow/tfjs-node-gpu/deps/lib/libtensorflow.so.2 --> libtensorflow.so.2.5.0} |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
When will you push it to the nextcloud store? |
New version is available now. Let me know if there are additional issues |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
It seems I cannot circumvent this bug, so I've reopened it here and over here: nextcloud/server#26708 |
This comment has been minimized.
This comment has been minimized.
A manual update of the app seems to work. |
what other manual way is there besides what i tried? i also tried the webinterface, same issue |
Move the |
Trying DecaTec's solution showed a 'Saving of node binary failed' message. I had to put the old recognize folder back and manually turn the maintenance mode off in config.php
|
@vanderheyde Make sure you chown to the right user. It should be the user of your http server (the one you use for running occ). |
I did. Also attempted to update via commandline with same result:
|
attempted both 1.6 release and 1.5.8 release, same results |
I guess, then you'll have to wait until this issue is fixed :/ |
fyi, this appears to be fixed in v22 |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
To be clear: This is a bug in nextcloud < 22 that I cannot circumvent without bloating up the bundle causing the appstore to reject the bundle. (I have tried.) |
recognize new version available: 1.5.1
recognize couldn't be updated
recognize new version available: 1.5.2
recognize couldn't be updated
Nextcloud 21.0.4
The text was updated successfully, but these errors were encountered: