FS#56302 - [nextcloud] Upgrade incompatible with postgres 10
Attached to Project:
Community Packages
Opened by Maarten de Vries (de-vri-es) - Saturday, 11 November 2017, 20:58 GMT
Last edited by Sergej Pupykin (sergej) - Monday, 12 February 2018, 20:32 GMT
Opened by Maarten de Vries (de-vri-es) - Saturday, 11 November 2017, 20:58 GMT
Last edited by Sergej Pupykin (sergej) - Monday, 12 February 2018, 20:32 GMT
|
Details
Nextcloud's upgrade procedure is not compatible with
postgres 10, which is now used in Arch. An attempt to
upgrade will result in an error, leaving the nextcloud
instance unusable.
More information is available on github. A fix is mentioned in the comments but has not been commited yet: https://github.com/doctrine/dbal/issues/2868 Manually applying the fix mentioned in the issue is a workaround. Tested with nextcloud-12.0.3-3 and postgresql-10.1-1 To reproduce: $ sudo -u nextcloud /usr/share/webapps/nextcloud/occ upgrade <output snipped> Doctrine\DBAL\Exception\InvalidFieldNameException: An exception occurred while executing 'SELECT min_value, increment_by FROM "oc_activity_activity_id_seq"': SQLSTATE[42703]: Undefined column: 7 ERROR: column "min_value" does not exist LINE 1: SELECT min_value, increment_by FROM "oc_activity_activity_id... ^ Update failed |
This task depends upon
https://github.com/doctrine/dbal/issues/2868#issuecomment-332119007
Edit: whoops, nevermind... looks like you linked the issue already!
Is there some feedback here about Nextcloud stability when using Postgres 10 (after applying the proposed patch to do the upgrade)?
If it is working and stable with Postgres 10, is it possible to include the patch in the Archlinux package?
The FreeBSD port/package added it some time ago, using exactly this patch:
https://svnweb.freebsd.org/ports/head/www/nextcloud/files/patch-3rdparty_doctrine_dbal_lib_Doctrine_DBAL_Schema_PostgreSqlSchemaManager.php?view=markup
However, the file integrity check is (quite obsiously) affected by patching a file and will display a warning:
https://github.com/nextcloud/server/issues/7549
The FreeBSD discussion is here: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224393
I not able to figure what is the worst, between integrity warning to all users or package more or less broken for a few (like me) using Postgres.
In my situation, I am using some automatic deployment and multiple staging/testing VMs, so patching the Doctrine file is feasible but require more than just issuing a command on my laptop.
Unless Nexcloud 13 is scheduled to be released *soon* we really should backport this fix now, rather than have a package with broken backends.
I think you can close it if nobody is reporting an issue with Nextcloud 13 + Postgres 10.