February 2024 releases: 28.0.3 27.1.7 and 26.0.12 final

Latest releases are out, grab them while you can! :tada:








Thank you. 26.0.12 up & running.

Does “grab them while you can!” implies you have recruited a Midl of Lidl marketeer - “when its gone its gone” :wink:

When I try to update from version 27.1.6 to 27.1.7 via updater.phar, I unfortunately get the following error:

[✘] Create backup failed
Could not copy "/var/www/nextcloud/apps/files_trashbin/lib/Sabre/AbstractTrash.php" to "/var/www/nextcloud-data/updater-oc41epd17f6k/backups/nextcloud-". Source /var/www/nextcloud/apps/files_trashbin/lib/Sabre/AbstractTrash.php is not readable. Destination /var/www/nextcloud-data/updater-oc41epd17f6k/backups/nextcloud- is not writable

Thank you to the team for the release!


What’s the general timeline between a release announcement and docker image availability?


Maybe a lack of space?

Check in your DATA folder, inside update.log file. There must be a
reason logged there.

1 Like

Thanks guys for all these patches, the only thing missing from this wonderful tool is to fix that damn desktop client, 4 hours to sync a folder of 300.000 files…make it work like the mobile version, at least you don’t have to wait.

Now… saving to S3 is still a headache for my clients, it’s almost impossible to rename a folder inside a shared folder.

1 Like

Sorry, I found the error. www-data had no authorization for the file in question. For some reason root:root was entered. After a chown the update went through.

Would installing this update break Calendar App 4.4.5? Bug 5563 remains open, and I’m not willing to lose half of my calendar appointments by upgrading. It is unclear if Nextcloud 28.03 is compatible with this older version of the Calendar App.

Thank you.

No, the lowest available version for NC28 would be 4.5.0:

I’d keep the NC 27 branch (still supported until June this year) and wait for https://github.com/nextcloud/calendar/issues/5563 to be fixed.

Thank you, @tflidd

is there any information or experience about the availability of the docker versions of the current release versions?

To be fair to Nextcloud, this is a problem with most cloud applications. I often sit there watching OneDrive populate the file structure of a massive SharePoint document library. However, 4 hours does seem a very long time. Not many of my clients have 300,000 SharePoint document libraries but one does have over 100,000. I’ll do a test now.

I was mulling over this at the weekend as I sat watching OneDrive do an initial sync of the file structure. One gets the feeling that they all do it one file at a time. I wonder if any of them do it via a bulk mechanism, i.e. download the entire list locally in one block and work through it. However, experience has shown that the local file system is (relatively) slow at creating thousands of small files. For maximum efficiency, it would probably need an OS function to bulk create placeholders effectively. Replace multiple individual calls to CreateFile with one call to create all the placeholders in one directory in one go. Replacing multiple directory updates with fewer writes. I wouldn’t be surprised if the OneDrive developers were asking for the same of the Windows team. A rather low-level change to the OS disk system though. Does Linux offer anything like this?

Now… saving to S3 is still a headache for my clients, it’s almost impossible to rename a folder inside a shared folder.

I reported the same here as well but mysteriously today it’s not happening. The fault I was getting is creating a new folder. It failed and put it back to “New folder”.

Might raise a separate post on this. On a very rough speed test, OneDrive is ~3.6 times faster at the initial placeholder synchronisation of a folder.

OneDrive took 13 minutes to initially create the placeholders (no data downloaded) for 71,461 files. That’s creating placeholders at a rate of 11 seconds per 1,000.

Nextcloud took 9 minutes to initially create the placeholders (no data downloaded) for 13,536 files. That’s creating placeholders at a rate of 40 seconds per 1,000.

Both tests were creating the placeholders on the same RAID-0 SATA-3 HDD drive.

The speed of the internet connection should be irrelevant as so little data is been transferred when doing initial synchronisation. Same with the performance of the host? That said, Nextcloud is hosted on Azure as I suspect is OneDrive. Haven’t a clue whether Azure throttles the internet connection. But if this is a factor, then Nextcloud client/server could do the initial sync in a better way, i.e. bulk setup.

1 Like

There seems to be an issue in the automated build process, see here: https://github.com/nextcloud/docker/actions/runs/8134160455

Maintainers of the nextcloud/docker repository would have to investigate this further.

Edit: I have opened an issue regarding this: [GH-Actions] Image build failed for 28.0.3/27.1.7/26.0.12 · Issue #2171 · nextcloud/docker · GitHub


seems to be solved - the docker images are available since 18 hours.

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