Date: Thu, 04 Jan 2018 11:30:34 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 224393] Update to www/nextcloud 12.0.4 caused INVALID_HASH PostgreSqlSchemaManager.php Message-ID: <bug-224393-13-hhZBEeGaXT@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-224393-13@https.bugs.freebsd.org/bugzilla/> References: <bug-224393-13@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D224393 --- Comment #4 from Marko Cupa=C4=87 <marko.cupac@mimar.rs> --- (In reply to loic.blot from comment #3) "Code Signing" page at docs.nextcloud.com states that "By supporting Code Signing we add another layer of security by ensuring that nobody other than authorized persons can push updates for applications, and ensuring proper upgrades.": https://docs.nextcloud.com/server/12/admin_manual/issues/code_signing.html#= why-did-nextcloud-add-code-signing If vanilla Nextcloud doesn't work for some FreeBSD users using postgres, I guess the right thing to do would be to ask Nextcloud developers to include patch upstream, or come out with their own solution. Not that I have any experience with software packaging and maintenance. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-224393-13-hhZBEeGaXT>