Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 24 Apr 2020 00:29:17 +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@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D245863

            Bug ID: 245863
           Summary: www/gitea: fix viewing of branches with a slash in the
                    name
           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: kevans@freebsd.org
                CC: stb@lassitu.de
                CC: stb@lassitu.de
             Flags: maintainer-feedback?(stb@lassitu.de)

Created attachment 213736
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D213736&action=
=3Dedit
svn(1) diff against the ports tree

An issue[0] was filed upstream in January that branches with a slash in the=
ir
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 Free=
BSD
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) conv=
ince
gitea maintainers to accept the patch as well once it's upstreamed.

The attached patch brings it into the ports tree as well, so that FreeBSD u=
sers
can more immediately get the fix. It should still apply to the version 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

--=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-245863-7788>