Date: Mon, 07 Jan 2019 21:18:29 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 234709] www/gitea: Add sqlite_unlock_notify tag Message-ID: <bug-234709-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D234709 Bug ID: 234709 Summary: www/gitea: Add sqlite_unlock_notify tag Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: ports-bugs@FreeBSD.org Reporter: adamw@FreeBSD.org CC: stb@lassitu.de CC: stb@lassitu.de Flags: maintainer-feedback?(stb@lassitu.de) This is a request to enable the sqlite_unlock_notify tag when 1.7.0 is released. When multiple concurrent git operations are made against a repo backed by g= itea with a SQLite database, transient errors occur, such as: Gitea: Internal error=20 UpdatePublicKey: Failed to update public key: database is locked or Gitea: You do not have allowed for this action User [user] does not have allowed access to repository [repo] 's code fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. A new tag (sqlite_unlock_notify) was added recently to fix this, and it sho= uld arrive with 1.7.0. databases/sqlite builds with UNLOCK_NOTIFY enabled by default, so it should be safe to tie this new tag to the SQLITE option of gitea. -SQLITE_VARS=3D GO_TAGS+=3Dsqlite +SQLITE_VARS=3D GO_TAGS+=3D"sqlite sqlite_unlock_notify" --=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-234709-7788>