RC1s of 28.0.9 and 29.0.5

Maintenance releases of 28.0.9 and 29.0.5 are coming next Thursday and RCs for those are now available on our download server.

As always, help with testing is very much welcome!

We updated our servers, did our tests, and the release candidates seem pretty decent. Still, give it a whirl and report back here so weā€™re even more sure that itā€™s good to go! If you notice anything out of order, please report back on the appropriate Github repository! :bowing_woman:

Downloads

Changelogs

29.0.5 RC1

28.0.9 RC1

After the upgrade from 29.0.4 to 29.0.5 RC1 I see in the NC Admin Overview

ā€œOne or more mimetype migrations are available. Occasionally new mimetypes are added to better handle certain file types. Migrating the mimetypes take a long time on larger instances so this is not done automatically during upgrades. Use the command occ maintenance:repair --include-expensive to perform the migrations.ā€

After run :

sudo -u www-data php occ maintenance:repair --include-expensive

The problem has not been resolved and the message still appears.

1 Like

Just upgraded to 29.0.5 and get the same message. repair step does not resolve the issue :frowning: .

Same issue here

Same issue here on 2 different servers after upgrading to 29.0.5 (final) , I ā€œran occ maintenance:repair --include-expensiveā€ twice to no avail ā€¦

1 Like

Hi, same problem for me ā€¦

1 Like

Hello same here for meā€¦ seems a bug for a lot of poepleā€¦

I think this is not the correct post (RC1) to explain thisā€¦ prhaps here Warning after upgrading to 28.0.9 or 29.0.5

Hello, I have too same problem after update to 29.0.5 from 29.0.4

Same problem hereā€¦

Also getting the warning ā€œOne or more mimetype migrations are availableā€¦ā€ and the given occ command runs without error but does not clear the warning.

This has already been fixed.

See my post here on how to manually apply the patch.

1 Like

Mimetype warning issue: [Bug]: Warning: One or more mimetype migrations are available Ā· Issue #47359 Ā· nextcloud/server Ā· GitHub
No need to add comments saying ā€œme tooā€ :see_no_evil:, weā€™re aware of it and itā€™s been fixed within 24h too :wink:

Thank you all for the help!

2 Likes

Thanks for that. :slight_smile:

And now, if there was an official hotfix release that would allow us to patch our instances without getting a ā€˜much more frighteningā€™ red integrity check warning instead of a ā€˜yellowā€™ mimetipe warning, everything would be perfect :wink:

This topic was automatically closed after 31 days. New replies are no longer allowed.