Skip to content
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 to 10.0.2 fails [Check for expected files] #3045

Closed
pejakm opened this issue Jan 12, 2017 · 5 comments
Closed

Update to 10.0.2 fails [Check for expected files] #3045

pejakm opened this issue Jan 12, 2017 · 5 comments

Comments

@pejakm
Copy link

pejakm commented Jan 12, 2017

I started with paid NextCloud hosting, and from the admin panel I see there's version 10.0.2 available (current version is 10.0.1). However, when I start upgrade, it fails at the first step:

snimak_20170112_143838

Don't know how to proceed here, since I don't have access to filesystem. Should I open a ticket at my hosting service or there is a way to override this?

PHP
Version: 5.6.21
Memory Limit: 512.0 MB
Max Execution Time: 3600
Upload max size: 513.0 MB

Database
Type: mysql
Version: 5.6.30
Size: 8.8 MB
@nickvergessen
Copy link
Member

@MorrisJobke

@MorrisJobke
Copy link
Member

Don't know how to proceed here, since I don't have access to filesystem. Should I open a ticket at my hosting service or there is a way to override this?

There is no way to override this. We do this check because in the past there were files in the nextcloud directory causing the update to break, because they are loaded by the autoloader.

Best would be to let this fix by your host. @LukasReschke Do we want to allow to continue an update on your own risk?

@thejulian
Copy link

thejulian commented Jan 17, 2017

👍 for "continue an update on your own risk" - Button

@LukasReschke
Copy link
Member

LukasReschke commented Jan 17, 2017

Best would be to let this fix by your host. @LukasReschke Do we want to allow to continue an update on your own risk?

There are some other implications of that, we would also need to have a list of shipped folders that are safe to delete etc… (in case a folder gets removed in an update)

Kinda error-prone. But I would not be against a Pull Request…

@MorrisJobke
Copy link
Member

Duplicate of nextcloud/updater#68

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants