Nextcloud 23 support

[sunjam]

For internal testing and notes. Do not expect support!!!!!! Please do report testing issues here.
Nextcloud 23 beta 1 available 10/18/2021
"Release date is 1 December 2021" according to this post.
See this wiki post on which apps are not yet compatible with 23.

• ^ includes apps missing support for 22 and 21

nextcloud/server#29258 - Deprecation of php 7.3

• Deprecate PHP7.3 for Nextcloud 23 server#29285 just introduces a warning to be displayed.
• Drop PHP7.3 server#29286 in version 24
  • Support PHP8.1 server#29287 in development for future release

[ovpc]

Tried updating to NC23.0.0 using nc-update-nc via ncp-config ncp v 1.44.5

and apps thet get disabled are

Timetracker seems to work okay after re-enabled it, as do preview gen and ncp app

[Oberlurch3000]

Since updating to NC23.0.0 I can't enter maintenance mode any more due to an unhandeled exeption.
My ncp-config is to v .44.5. Also Nextcloud Check shows me an error. But I've no issues using the web application so far.

EDIT: Problem solved! Somehow in ncp-config the maintenance mode was on enabeled also it wasn't after the update. Just setting it to "NO" and back to "YES" gave me the expected behaviour. Also nextcloud check works fine now. So it wasn't a NC23 specific issue.

[jerabaul29]

Is there some hope / roadmap / thoughts about providing the v23 by default? Would be super useful thanks to the possibility to perform automatic peer to peer backup as indicated on the Nextcloud release page. If I understand well, that would make it possible / easy to have 2 nextcloud boxes at 2 different locations peer backing-up each other, which would be really awesome and would make the solution truly semi professional (for now, the fact that there is no real remote peer to peer backup as far as I know is a big minus with regards to guarantees around no loss of data).

[nachoparker]

That's a cool feature, but just so you know, NCP has supported this for years using btrfs-sync or rsync

[aphex008]

Hey! Count my vote in for this issue :) Looking forward for 23 support.

[nachoparker]

NC23 available for testers in the devel branch. If I don't get bug reports, will publish shortly

[ovpc]

Tested Update to NC 23.0.4 on a Proxmox VM ncp 1.47.1 NC22.2.2 using ncp-config
Full terminal output here
In NC Get

Integrity check fail:
`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

• core
  • INVALID_HASH
    • core/js/mimetypelist.js

Raw output

Array
(
[core] => Array
(
[INVALID_HASH] => Array
(
[core/js/mimetypelist.js] => Array
(
[expected] => 94195a260a005dac543c3f6aa504f1b28e0078297fe94a4f52f012c16c109f0323eecc9f767d6949f860dfe454625fcaf1dc56f87bb8350975d8f006bbbdf14a
[current] => 1b07fb272efa65a10011ed52a6e51260343c5de2a256e1ae49f180173e2b6684ccf90d1af3c19fa97c31d42914866db46e3216883ec0d6a82cec0ad5529e78b1
)

            )

    )

)
`

[theCalcaholic]

@ovpc That issue can have two reasons:

• Either the file (core/js/mimetypelist.js) could not be overwritten for some reason (filesystem issue, it being in use by something) - however, in this case, the update should have failed
• or it has been corrupted during download of NC 23.

We should maybe check the archive checksum during updates... 🤔

Since this is probably not related to NC23 in particular, I'll close the issue again. To fix your specific problem, you can

1. Download the correct version of nextcloud to your instance. You want the .tar.bz2 file.
2. Get the correct link from here
3. Download it using wget <url>
4. Extract the archive with tar -xf <downloaded-file>
5. Put nextcloud into maintenance mode with ncc maintenance:mode --on (or use ncp-config)
6. find the corrupted file (core/js/mimetypelist.js) in the archive and copy it over to your nextcloud installation folder with sudo cp ./nextcloud/core/js/mimetypelist.js /var/www/nextcloud/core/js/mimetypelist.js
7. Fix the permissions on the file chown www-data: /var/www/nextcloud/core/js/mimetypelist.js
8. Disable maintenance mode ncc maintenance:mode --off (or use ncp-config)

Then the checksums should match again