-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
[stable29] fix(setupcheck): Fix mimetype server version check in backport #47378
Conversation
Signed-off-by: Joas Schilling <coding@schilljs.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you! Error gone.
running "occ setupchecks" shows "✓ Mimetype migrations available: None". Error does not show there anymore neither. Thanks |
How can I get the fix if I just updated before the commit? |
@supett Please... Not everyone here is an IT professional and it would be nice if the complete command was given. So the complete line that you have to enter in the directory. php83 ./occ....... |
|
The call of the occ command is not the problem. But witch of the subcommands will update the fixed file? Upgrade say : everything is uptodate. Only patch the file manually will break the checksum. So what is the right way. Or have Wochenende wait for 29.0.6? |
Hi there! as described above in fix(setupcheck): Fix mimetype server version check in backport Have a nice day... edit: |
Yes, this works for me too, but if you then do an integrity check the file was marked as broken:
|
But that is logical and not a final fix. This will be resolved in the next stable version. |
@WM-Loose You can ignore the warning. Simply wait for the next Nextcloud version. You have no advantage if you fix it now, it's just a false warning with no disadvantage. |
Yes, I do that with all customer installations and wait for the update.
I made the adjustment (fix) for our own installations and that is completely sufficient for me.
Von: Markus Ritzmann ***@***.***>
Gesendet: Freitag, 23. August 2024 08:44
An: nextcloud/server ***@***.***>
Cc: Dirk ***@***.***>; Mention ***@***.***>
Betreff: Re: [nextcloud/server] [stable29] fix(setupcheck): Fix mimetype server version check in backport (PR #47378)
@WM-Loose <https://github.com/WM-Loose> You can ignore the warning. Simply wait for the next Nextcloud version. You have no advantage if you fix it now, it's just a false warning with no disadvantage.
—
Reply to this email directly, view it on GitHub <#47378 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AXYH7P6OIU26MQGIRNJ2RV3ZS3K4TAVCNFSM6AAAAABM3P2MQOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMBWGQYDCMJVGM> .
You are receiving this because you were mentioned. <https://github.com/notifications/beacon/AXYH7P64YBSOQW4IBDU2N6TZS3K4TA5CNFSM6AAAAABM3P2MQOWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTUJPDRYC.gif> Message ID: ***@***.*** ***@***.***> >
|
Thanks! it's work for me. |
Fix by changing line 427 works for me - thanks! Interestingly, I don't get the invalid_hash error by doing so. Could be something to do with running my instance in docker, since I don't remember changing a setting or config file elsewhere! And can I just say, this is a terrible bug for all of the (many) nextcloud users with OCD over that green tick :) |
You have to log in via ssh and run Have a nice day |
Ahhh - that'll be it - thanks! It's been a while since I used the web updater or via CLI, and you don't get that message when updating your instance via docker and docker build file, so I'd forgotten :) |
Thanks man. It works for me as well))) |
Checklist