It didnât install in NC 22.
OK. I am on NC21. Sorry.
All my NC instances do not show the 21.0.4 update, a week after release. There must be something strange going on as a minor release is normally not rolled out delayed âŚ
stuck on 21.0.3 here also.
i for once didnât do the âswitch to beta and backâ trick as i usually do and have been waiting patiently for 22.
the wait continues.
Just updated 2 almost identical docker instances from 21.0.3 to 21.0.4, both are up and running again, but for some reason one instance reports an integrity error?
[INVALID_HASH] => Array
(
[templates/settings/personal/development.notice.php] => Array
(
[expected] => 9350eed8a575764a192301beb19ef77dbbb8c105e661b378c4714c1d6678ca3a3fd2f95fcddd1df2fcef64c32aabedfa3d64e826389ee33da3c8a66619b9448e
[current] => cf83e1357eefb8bdf1542850d66d8007d620e4050b5715dc83f4a921d36ce9ce47d0d13c5d85f2b0ff8318d2877eec2f63b931bd47417a81a538327af927da3e
)
)
I mean, howâs that even possible given that both use the same docker image? The only development.notice.php file I can find is 0 bytes with both instances.
Also no 21.0.4 update availabe, neither in web gui (also beta channel) nor command line.
For a company with the aim of high professionality I expect updates beeing available for all at the same time!
i think we do not need more messages here.
it is clear that the rollout not started.
i think they found problems (maybe with circles?) and not started it (which is good).
let´s see what the next days will bring.
the only think what is not nice is the kind of communication to the community.
one or two sentences of a official person about the current state would not hurted anyone.
(instead tickets get closed with kind of ignorance https://github.com/nextcloud/server/issues/28367 or not get any replies did production branch deployed without errors? ¡ Issue #634 ¡ nextcloud/updater_server ¡ GitHub, or this thread here)
@jospoortvliet May I ask you to have a look and provide a small information update to the community?
We are wondering if the upgrade to 21.0.4 is hold back intentionally (due to some issues maybe) or if this minor update is also provided in waves.
Some users, including me, would expect that a minior update is available immediately after the release announcements. Are we wrong with our assumption?
A short info/ clarification would be nice.
Thanks a lot.
I have 21.0.4 RC1. I needed to fix this issue
https://github.com/nextcloud/server/issues/27781
I think this fix solved it:
adding these lines
apc.enable_cli=1
apc.shm_size=512M
to this file
/etc/php/7.3/mods-available/apcu_bc.ini
This seems to solve a different issue related to the cron job. It does not effect the upgrade. Still stuck to 21.0.3.
issue got fixed, you should all get 21.0.4 now!
(did production branch deployed without errors? ¡ Issue #634 ¡ nextcloud/updater_server ¡ GitHub)
Indeed! Thank you
21.0.4 rollout seems to work but now 22.1.0 is not available anymore on the beta (!) channel (and on the stable channel).
We do a 22.1.1 next week. An issue with Circles and Talk caused us to delay the updater deployment.
Anyone else lost their logo and favicon after updating to 21.0.4?
ScssPhp\ScssPhp\Exception\CompilerException: Undefined variable $theming-cachebuster: apps/theming/css/theming.scss on line 96, at column 2 Call Stack: #0 import apps/theming/css/theming.scss (unknown file) on line 1
No, I have the theming app enabled with that it works.
Me too, but its settings are no longer honoured
Same Problem here with two instances of NC.
Itâs a known bug.
Just deactivate the guests- app
Thanks Soko, that worked