Uh oh!
There was an error while loading. Please reload this page.
[stable29] fix(setupcheck): Fix mimetype server version check in backport - #47378
Conversation
Signed-off-by: Joas Schilling <coding@schilljs.com>
supett
commented
Aug 21, 2024
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? |
WM-Loose
commented
Aug 22, 2024
@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....... |
supett
commented
Aug 22, 2024
|
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: |
AleksCee
commented
Aug 22, 2024
Yes, this works for me too, but if you then do an integrity check the file was marked as broken:
|
WM-Loose
commented
Aug 22, 2024
But that is logical and not a final fix. This will be resolved in the next stable version. |
mritzmann
commented
Aug 23, 2024
@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. |
WM-Loose
commented
Aug 23, 2024
via email
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: ***@***.*** ***@***.***> > |
filerem
commented
Aug 23, 2024
Thanks! it's work for me. |
sultanoswing
commented
Aug 25, 2024
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 |
sultanoswing
commented
Aug 25, 2024
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 :) |
neerro
commented
Aug 28, 2024
Thanks man. It works for me as well))) |
Checklist