Date: Mon, 11 May 2020 16:53:09 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 245863] www/gitea: Fix viewing of branches with a slash in the name Message-ID: <bug-245863-7788-bmeYv7MCRL@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-245863-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-245863-7788@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=3D245863 --- Comment #13 from commit-hook@freebsd.org --- A commit references this bug: Author: kevans Date: Mon May 11 16:52:29 UTC 2020 New revision: 534921 URL: https://svnweb.freebsd.org/changeset/ports/534921 Log: www/gitea: Fix viewing of branches with a slash in the name An issue[0] was filed upstream in January that branches with a slash in their name (e.g. stable/11) result in a 500 error when attempting to view them. I tracked down the issue to the fact that read(2) on a directory fd in FreeBSD will actually succeed, while it will not on Linux/other OS. I have filed a PR[1] with go-git to remedy the problem there, and then we (hopefully) convince gitea maintainers to accept the patch as well once i= t's upstreamed. The attached patch brings it into the ports tree as well, so that FreeBSD users can more immediately get the fix. It should still apply to the vers= ion in 2020Q2, more or less, with version numbers changed to protect the innocent. [0] https://github.com/go-gitea/gitea/issues/9938 [1] https://github.com/go-git/go-git/pull/39 PR: 245863 Approved by: <stb lassitu de> (maintainer) Aoorived by: koobs (mentor, ports) MFH: 2020Q2 (minor bugfix patch) Changes: head/www/gitea/Makefile =20 head/www/gitea/files/patch-vendor_github.com_go-git_go-git_v5_storage_files= ystem_dotgit_dotgit.go --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-245863-7788-bmeYv7MCRL>