New Nextcloud maintenance releases out with improved updater and over 40 fixes

system · September 29, 2016, 5:08pm

Originally published at: New Nextcloud maintenance releases out with improved updater and over 40 fixes - Nextcloud

screenshot_20160929_190237
Today we’ve released the first update to Nextcloud 10 and a 3rd update to Nextcloud 9. These releases bring a large number of improvements, most notably an improved updater. We strongly recommend upgrading. Read on for a taste of what is new.

Improvements

The new updates add some minor functionality to Nextcloud 9, allowing user quota retrieval via the provisioning API and supporting the files drop capability for clients. Clients will also be able to retrieve theming information so they can adjust colors or icons as well and the theming tool will modify the browser page titles to match the setting by the Admin. The Nextcloud installation process will warn users that Nextcloud 9 does not support PHP 7.1 and will refuse to continue the installation.

Nextcloud 10 received most of the same enhancements as 9, adding the ability for admins to specify the configuration directory in an environment variable and applying the password policy upon user creation.

Besides the introduction of these enhancements over 40 bugs were squashed in both 9 and 10.

A complete changelog can be found on our website.

Improved Updater

With 10.0.1 and 9.0.54 we include a more reliable updater which has been in testing for several weeks. We had disabled the update notifications in current versions due to issues with the updater. We decided to spend time on additional testing and improvements to make sure no admin would be left with a broken instance. The new updater replaces the files of the existing installation with those of the new release, doing extensive checks in between to ensure the platform, permissions and other requirements are all as they need to be. Once the upgrade of the files is done, the normal update process can be started from either the command line or the browser. To upgrade to 10.0.1 and 9.0.54 you still need to do this manually via our tarballs. For future updates (from 9.0.54/10.0.1 to a release afterwards) instances can more easily be updated via the new web based updater which shows up in the admin settings once there is an update available. In the upcoming releases we also plan to bring this feature back to the command line tool.

If you’re eager to test the new updater with an old version of Nextcloud you can find the steps in the forums, but they should only be used by experienced users. Only updating the URL in config.php to the new server (via updater.server.url) is strongly discouraged because then the old updater will break your setup.

Get the new update now!

[caption id=“attachment_1013” align=“aligncenter” width=“1024”] Another update done![/caption]

haemme · September 29, 2016, 5:25pm

Hi,

glad to hear this - thank you!

However, if I run

sudo -u www-data php occ upgrade
I get
Nextcloud is already latest version

Do I have to change the update channel?

Kind regards
Thomas

falu · September 29, 2016, 5:45pm

ummm, i don’t think that my 9.1.0.16 is the latest…

George_Farris · September 29, 2016, 6:16pm

I get exactly the same thing. Is the updater broken for 10.0.0 to 10.0.1 update?

LukasReschke · September 29, 2016, 6:21pm

occ upgrade is NOT executing any code upgrades or so. You need to manually put the code in place and then execute it. It simply runs the upgrade routine once the code is in place. (as it always did)

JoMatr · September 29, 2016, 6:54pm

After upgrade from 10 to 10.0.1 the app store is not working. When activate the Mail app, contacts or calendar app, it comes the error message: cURL error 35: Unknown SSL protocol error in connection to github-cloud.s3.amazonaws.com:443 Server: Debian Jessie Linux 4.6.4-1~bpo8+1
Any Ideas?

Problem solved. My firewall configuration was incorrect. Sorry for the post. Next Cloud 10.0.1 running perfectly. Manual update went smoothly.

Thanks for the great work!!!

JasonBayton · September 29, 2016, 8:40pm

Just finished what I hope will be the last manual upgrade for Nextcloud, everything works as expected. Thanks for another awesome update!

Julien_B · September 30, 2016, 6:31am

Hi,

After performing a manual upgrade from 10.0.0 to 10.0.1 (https://docs.nextcloud.com/server/10/admin_manual/maintenance/manual_upgrade.html) I get this integrity check warning:

Technical information

The following list covers which files have failed the integrity check. Please read
the previous linked documentation to learn more about the errors and how to fix
them.

Results

password_policy

EXTRA_FILE

img/app.svg

files_accesscontrol

EXTRA_FILE

lib/CacheWrapper.php

user_saml

EXTRA_FILE

appinfo/update.php

img/app.svg

theming

EXTRA_FILE

img/app.svg

lib/Capabilities.php

Raw output

Array
(
[password_policy] => Array
(
[EXTRA_FILE] => Array
(
[img/app.svg] => Array
(
[expected] =>
[current] => eda9b8cca85e4a60a02d9bed0286a526df4a02f23437720a057f98da7fe2d191b74d8e25861a4ac148b69b9ff142c5aa25dbb7c7248c42846f07aded01bf0efe
)

[files_accesscontrol] => Array
    (
        [EXTRA_FILE] => Array
            (
                [lib/CacheWrapper.php] => Array
                    (
                        [expected] => 
                        [current] => e5e6069b9d4e7d4b27c3549b188ce8474d7feeb135ceb1a985ca966a3d5f67be10a053566eded204be208799bad2d89318038a669f4992a56bfd298235119cbd
                    )

[user_saml] => Array
    (
        [EXTRA_FILE] => Array
            (
                [appinfo/update.php] => Array
                    (
                        [expected] => 
                        [current] => 3ec3b90994f0fdc7512717959fe6989388e8cbc1d2924e090fef2647a44369c7b5f8c28c71c8fb651c6c573b72b1f8ed9640a091bd30e263b91038357d380605
                    )

                [img/app.svg] => Array
                    (
                        [expected] => 
                        [current] => 8de71976146a347ee037d47f14d5d9ad95e91547054e10508afc1fc89495528032531809cc07936b8c66e62858702657c648f340c9b468181074ba6482a0c77a
                    )

[theming] => Array
    (
        [EXTRA_FILE] => Array
            (
                [img/app.svg] => Array
                    (
                        [expected] => 
                        [current] => ef917321e149d000fd44eade9aa8dcbb5dcaf01d8c023869b555b7a26d9f6b30860b1cb23290bd3fdc105bc504026dce381f7eb177cff2f38d3be4968c682331
                    )

                [lib/Capabilities.php] => Array
                    (
                        [expected] => 
                        [current] => 82d33b5f34309e3591e79495c3ed1782f6c81cbf5973d3a41ab303c08ac09478f912b529294db3f76af89e31eb5ab10b78375a14d2271dc16d1125b6f85149bb
                    )

)

Should I delete these files ?

BernhardPosselt · September 30, 2016, 7:24am

@Julien_B yes you should delete them

AlfredSK · September 30, 2016, 8:27am

Manual update to 10.0.1 was successful. Everything* works. Very nice release. Thank you!

* The News app was completely missing after the update. Even enabling experimental apps didn’t help. I had to manually download the app (v.9.0.4) from the new appstore and extract it to the …/apps/ folder.

LukasReschke · September 30, 2016, 8:30am

These files actually look legit. Where did you download the 10.0.1 from? What did you execute exactly when updating?

JuergenGrete · September 30, 2016, 9:28am

Hi,
do I run in trouble, when I’m updating from 9.0.53 directly?
Or should I upgrade step by step?
Sorry if I doesn’t see the obvious…
Regards
Jürgen

Soko · September 30, 2016, 9:34am

Step by step, because of the database-manipulations should be the better and more secure way…

JasonBayton · September 30, 2016, 9:49am

@AlfredSK when you follow the upgrade procedure, don’t forget to copy over your apps too

I’ve done it a couple of times where I leave both apps and themes out and wonder what on earth has happened

Smaig · September 30, 2016, 11:35am

Manual update from fresh install with 10.0.0 to 10.0.1 worked like a charm, except maybe this in my logs:

Info no app in context Invalidating tokens older than 2016-09-29T10:45:03+00:00 2016-09-30T12:45:03+02:00 –
Info no app in context Invalidating tokens older than 2016-09-29T10:30:02+00:00 2016-09-30T12:30:02+02:00 –
Info no app in context Invalidating tokens older than 2016-09-29T10:45:03+00:00 2016-09-30T12:45:03+02:00 –
Info no app in context Invalidating tokens older than 2016-09-29T10:30:02+00:00 2016-09-30T12:30:02+02:00 –

seems to correspond to my cron execution time which is configured just with this line (edited as www-data):

*/15 * * * * php -f /var/www/nextcloud/cron.php > /dev/null 2>&1

Also, i’ve noticed that we don’t get any feedback when trying to create a new user without matching password policy.

AlfredSK · September 30, 2016, 1:43pm

@JasonBayton Hmm. I’ve never experienced the need to copy the apps manually. It was always sufficient to reenable them from the admin’s app panel.
Also, I just found out that the News app has completely vanished from apps.owncloud.org (the default app source of Nextcloud). No wonder it didn’t work. :-/
Btw. is it possible to enable the experimental Nextcloud appstore as a second, alternative source of apps now?

BernhardPosselt · September 30, 2016, 2:01pm

Yep the News app was pulled from the store because I was contacted from ownCloud people and Nextcloud apps are not allowed on the store

BernhardPosselt · September 30, 2016, 4:24pm

BTW, I’m currently trying to make the new app store work on Nextcloud 10 which depends on a few fixes for the server https://github.com/nextcloud/server/pull/1598#pullrequestreview-2347850 and this PR which implements the OCS (old) App Store API https://github.com/nextcloud/appstore/pull/326

shad · September 30, 2016, 5:20pm

The Updater of 10.0 still finds no update. I´m getting bored right now. Update to 10.0 was the same issue and someone said there will be no problems in future versions.

Extremeley pissed off right now. Is that the big thing in comparison to owncloud? I really don´t think so! Same sh*t different name.

BernhardPosselt · September 30, 2016, 5:27pm

@shad read the announcement properly: " To upgrade to 10.0.1 and 9.0.54 you still need to do this manually via our tarballs."